Hello,
Got a Xperia Z2. It's rooted, installed TWRP Manager (ROOT), tried to install recovery manager. seemed to work but coulden't boot into recovery mode. I remember i had blocked bootloader and went through that and probably unlocked it. As no issues and every step went fine.
Tried now to start my phone, I only see background image and those waves. then it stucks for a second and reboot on it's own. And does that again and again.
Everything worked with phone until i unblocked the bootloader. also made sure i typed the right numbers and letters, and I did. Also no error at all when unlocked the bootloader.
but now I can't get my phone running. I still can boot into "fastboot mode", (volume up and power button and the led is blue).
So now I wonder if there is any way to get my phone running again, either with stock rom or something else. I really don't care how much I need to do, as long it might get the phone running again.
If you got any solution, or think you might have, try to explain as good as possible, as I'm not too familiar with these issues.
Thanks in advance.
TForsman said:
Hello,
Got a Xperia Z2. It's rooted, installed TWRP Manager (ROOT), tried to install recovery manager. seemed to work but coulden't boot into recovery mode. I remember i had blocked bootloader and went through that and probably unlocked it. As no issues and every step went fine.
Tried now to start my phone, I only see background image and those waves. then it stucks for a second and reboot on it's own. And does that again and again.
Everything worked with phone until i unblocked the bootloader. also made sure i typed the right numbers and letters, and I did. Also no error at all when unlocked the bootloader.
but now I can't get my phone running. I still can boot into "fastboot mode", (volume up and power button and the led is blue).
So now I wonder if there is any way to get my phone running again, either with stock rom or something else. I really don't care how much I need to do, as long it might get the phone running again.
If you got any solution, or think you might have, try to explain as good as possible, as I'm not too familiar with these issues.
Thanks in advance.
Click to expand...
Click to collapse
i think, now you can flash stock ftf thru flashtool.
and get it rooted again by xperia rootkit, and install xzdual recovery.
Jhon998 said:
i think, now you can flash stock ftf thru flashtool.
and get it rooted again by xperia rootkit, and install xzdual recovery.
Click to expand...
Click to collapse
Thanks, worked fine to use flashtool to get it to work again. Installed recovery and rooted it. Also custom rom. Thanks again
Related
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
Don't really need some special help here, just want the device to function again no matter what way. (Don't care if it's factory reset completely it has nothing on it I was just using it for a bit of experimenting).
So anyway, I have an HTC One x that I tried to install Cyanogenmod mod on but when trying to flash it (I was a bit impatient and just did what I thought would work), it didn't work and I'm stuck on the HTC Boot screen. I can still restart the phone and get to the recovery menus or whatever they're called. But even when doing a factory reset it still just won't get past the boot screen.
I'm just someone who has a good love for android and got given this phone for free so I thought I might experiment with rooting and all that, (I don't want to do this to my main driver, the Z1, for the life of me).
Any help here would be great.
Thanks
MHarris333 said:
Don't really need some special help here, just want the device to function again no matter what way. (Don't care if it's factory reset completely it has nothing on it I was just using it for a bit of experimenting).
So anyway, I have an HTC One x that I tried to install Cyanogenmod mod on but when trying to flash it (I was a bit impatient and just did what I thought would work), it didn't work and I'm stuck on the HTC Boot screen. I can still restart the phone and get to the recovery menus or whatever they're called. But even when doing a factory reset it still just won't get past the boot screen.
I'm just someone who has a good love for android and got given this phone for free so I thought I might experiment with rooting and all that, (I don't want to do this to my main driver, the Z1, for the life of me).
Any help here would be great.
Thanks
Click to expand...
Click to collapse
If you had just used htcdev.com to unlock the bootloader and are still S-On, you need to pull/extract the boot.img from the CyanogenMod zip and install via fastboot.
es0tericcha0s said:
If you had just used htcdev.com to unlock the bootloader and are still S-On, you need to pull/extract the boot.img from the CyanogenMod zip and install via fastboot.
Click to expand...
Click to collapse
She's running all good now, thanks for that
MHarris333 said:
She's running all good now, thanks for that
Click to expand...
Click to collapse
You're welcome. Pretty common issue when people are getting used to how it works for HTCs.
Pro Tip: If you want to simplify the process, you can use this: https://play.google.com/store/apps/details?id=com.cgollner.flashify and install the boot.img with the phone while booted, then boot to recovery and finish the rom install. Recommend doing a nandroid recovery first, just in case the boot,img/rom combo does not work properly, otherwise if you flash it first THEN do a backup, the new boot.img will be matched with the old rom and might cause issues upon restoring if they are not compatible.
Alternative: S-Off. Depending on which hboot you are on, you should be able to do S-Off. It can be a bit of a pain to set up, but once you do, then you can install roms just like normal as the boot.img will be able to be flashed from recovery along with the rom like in most phones.
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
jfsat said:
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
Click to expand...
Click to collapse
First off once you have unlocked the boot loader you nolonger have to do the downgrade/root/recovery dance if you get stuck. Just flasf the latest FTF then a rootable kernel (jackie099 normally has one out in a day or two of an updated firmware) then you can just flash recoveries/supersu/etc as needed.
Not sure why the installs are failing. If you have flashed a custom ROM (carbon/PAC/CM/...) and it doesn't boot at any point the first step is to flash the boot.img file that is inside the zip of the ROM. Do this in flashtool and put the phone into fastboot mode (vol. up when connecting to the PC).
Help
so i just got the lg g5, used. unlocked the bootloader, flashed twrp/rooted it, and tried to install linage os, which worked pretty good but the battery draw was insane.
i then proceeded to install fulmics rom. now i'm stuck on a bootloop which starts the recoverymode everytime.
does anyone know what to do? i'm not smart enough to get behind the kdz/tot flashing whatever it is called. i didn't came to any conclusion, tried flashing the boot.img and bootloader.img, a new kernel and other roms, also the flashable original firmware through sdcard, fixed permissions, repaired the directories but it still didn't change a thing. i always land into the recovery mode.
i really hope there is someone out there who can tell me what is going on maybe
so i got it working again.
what i did? i forced myself into recovery via holding power button and then doin the click which asked me the yes, yes again.. and all of sudden it works like nothing happened lol. had to reinstall the rom though
Anymore info on this and what you did exactly to come out of the "recovery bootloop" as I also have the same issue and suspect others may also run into this
What I did to get recovery loop:
ReRoot and flashed latest TWRP
Flashed Nougat Firmware via TWRP
Flashed Fulmics1
Reboot and then recovery loops
-
FYI for anyone else having this issue
Looking at other threads and noticed mention of this command a few times
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
the path on my G5 (H850) was instead /dev/block/platform/SOC/624000.ufshc and once run corrupted the device
Guess I'll reflash KDZ and try again.
This worked for me
Cuerex said:
so i got it working again.
what i did? i forced myself into recovery via holding power button and then doin the click which asked me the yes, yes again.. and all of sudden it works like nothing happened lol. had to reinstall the rom though
Click to expand...
Click to collapse
I just wanted to draw attention to this thread, because I searched for a bit and there seems to be dangerous advice (dd zero) out there and flashing. This trick worked for me right away. Thanks.
Running H850, might also work for other people stuck in TWRP bootloop with other models.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.