So I decided to flash MIUI Eu again for better cameras, but then the recovery just boot loops. Out of desperation, I decided to install global MIUI using Mi Flash. Then it took too long to flash and I accidentally pressed the flash all and lock. Now it seemingly bricks.
Is there any way to fix this issue? If not, i guess I could just bring it into warranty.
Oh wair the đevice just boots
I will update things
Related
Trying to help out my friend. He rooted his Galaxy S 4G and was trying out different roms and now it's stuck in recovery. He brought it to me--I can pretty much fix anything Android--I've helped a lot of people on XDA, but this one has completely stumped me.
I've Odin'd several different Official Stock restore packages, recovery packages, etc. Everything has the same effect, no matter the rom or the recovery, the phone will always (re)boot back into recovery. Selecting reboot system reboots it back into recovery. No matter what. I must have flashed Stock via Odin about 10 times today. Same results every time.
Right now it's stuck in the 3e recovery screen. But I can flash a Voodoo recovery, but it still gives the same effect.
Does anyone have any ideas? Is there a bootloader sequence anyone knows about, that he may have changed? Any help is appreciated.
Thanks everyone!
Follow the guide in the second link of my signature to fix.
Awesome! That worked! Followed the guide. I had already flashed stock, but I didn't know you could flash the bootloaders using a .jar package. It worked. I guess he jacked with his bootloaders.
actually, bootloaders would corrupt boot period. You'd be stuck in a "FIRMWARE UPGRADE FLASH FAILED" screen, or phone won't boot period. So, I think I know what the problem was.
When hopping from roms to other roms, specially on Kxx Based Touchwiz roms, your cache tends to get corrupted. Had you reflashed cache.rfs and a stock zImage using heimdall, it'd fix the issue, and data wouldn't vanish.
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Dissentire77 said:
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Click to expand...
Click to collapse
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
WhatTheAndroid? said:
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
Click to expand...
Click to collapse
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Dissentire77 said:
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Click to expand...
Click to collapse
Sounds like a thanks button click is on order for WhatTheAndroids post to you
ViperXL 2.4.0 w/ElementalX 3.1 kernel
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
Hey guys,
I was previously on xtresolite 2.4 lollipop rom and saw that he had a new rom out based on Marshmellow 6.01.
The instructions for the installation the new rom said to flash the new bootloader, modem and recovery before installing the new rom.
I flashed the bootloader with Odin using the BL button as instructed and how it's stuck on the Samsung Screen. I can still boot into download mode, but that's about it. It won't let me boot into recovery. Doing a bit of research it says to boot into download warning screen and cancel. Then quickly do the recovery buttons (volup, home, power), but it still won't go in.
So now I'm stuck! i'm trying to download the new stock Marshmellow firmware to see if I can install that, but aside from that I'm not sure what else I can do.
Any suggestions? Since I'm still able to use Odin, can I try to re-install the correct bootloader or is that too late? I'm not even sure which bootloader to install now. :crying::crying::crying:
Any help is much appreciated!
Thanks,
kc
as long as you can boot into the download mode, everything's alright. try flashing the latest stock rom for your model. then a new recovery, and then the new xtrestolite rom.
if something fails. do it again.... flash the latest stock rom, and so on.
Just make sure you have the correct model software for your phone and there won't be any issues. Did you backup your imei way back when you rooted on lollipop? If you did then everything will be fine if you didn't, Restore stock ROM and root, then backup your imei, hopefully you won't have any issues with your modem
Try pressing on power + vol down untill the phone shuts down then quickly press home+power+vol up before the phone starts . you will be in recovery try a factory reset then wait for the first boot. Voila !
hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!
tnimk said:
hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!
Click to expand...
Click to collapse
Stock rom overrides everything so your root is long gone & you now have the latest bootloader & modem already - don't stress & no need to do anything else! If you want custom recovery simply flash with latest TWRP using Odin in download mode (in tar format using AP button). Don't root with TWRP if asked to - instead download latest recovery flash-able SuperSU (ZIP) onto your device & then flash it using TWRP. This will be the safest option for you (with root if you want).
AFAIK one always uses the "AP" button if you wanna flash <anything> with Odin - not the BL button (I've never used this). The rest are for pro's only (of which I'm not one). I'm simply a regular rom flasher & read/study/compare several guides before attempting anything I've never done before with my device. If the overall feeling is not a good one, rule of thumb is I don't proceed until I feel confident enough about what I'm attempting to do.
Good luck.
On my sm-G920I
I flashed the xtresolite ROM without first flashing the bootloader and modem and it worked fine for me, if you back up everything with an otg cable onto a USB then flash the ROM everything should work fine but you will have to wait around 5 minutes for it to boot. If your still waiting after 10-20 minutes then you did something wrong and you can just wipe your entire phone then recover everything from your backup on your USB ????????
Alright, so it has been a while since I last tried custom roms only to go back to official EUI, so bear with me as this is probably a basic dumb question.
So I had TWRP and the official EUI. I saw that there was an OTA update and normally used the update app on the phone. It downloaded the rom, and booted into twrp which started flashing the rom. So far so good. I let it do its thing as it took some minutes... once it was ready it showed a dialog asking if I wanted the flashing process to rewrite the boot partition or let TWRP own it. I wasn't really sure which one to pick, but as I "swipes to unlock", the phone restarted anyway without letting me pick any of the two.
Now It only boots into recovery mode (TWRP). This is probably easy to fix in TWRP, but I am not sure how. Can anyone help?
Thank you.