Hello everybody,
Im totally new and have a big problem.
I rooted and unlocked my phone (HTC one m9), to install a costum Recovery (Team win)
I followed all instructions and copied viper rom on the phone.
After installation, I got into the bootloop.
I can see white HTC Bootscreen with the red instruction ..."This build is for..."
I know, that my phone is not able to boot new image because S-Off is not enabled.
Now my question.
Whats the best way to get a solution for this problem.?
I can boot into download mode or get into my costum recovery.
ADB and platform tools are installed on computer.
Need help. please!!!
Factory reset seems to be it. Thankfully something pops up, instead of dead. There should be a option( you may have to look for it on xda) to get into the stock recovery, through a combination of button presses. On my phone, volume up, and power button gets me into twrp, volume down and power button takes me to the stock recovery. You may have different cadence for your particular phone, so finding that out is a must to return to stock, which you can start over again. I couldn't even root my phone, with out installing twrp first, so I had to get the unlock code, to unlock it first. Some phones may have a different way to root, without unlocking the bootloader first, but start over, it still turns on. Whatever you have had will be lost, if you didn't backup somewhere before you started to install twrp, because it won't boot into the os, that info's gone, and you have to go back to stock, to get rid of the garbage that would still be there from the failed attempt. Trying to install twrp, without doing that may corrupt your partitions, then it may get bricked beyond repair.
What are the necessary steps i have to follow?
Relock Bootloader?
Flash firmware.zip?
how do i flash stock rom?
Im not able to star my phone.
only workspace is recovery and ADB via PC...
Help please!
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
Searched and couldn't find any solution.
I can't seem to boot into recovery whether it be through ROM Manager or manually holding the power and Vol down buttons. I ran the bootloader unlock tool from Asus and updated Super User already. )Before ROM Manager would freeze at the end of trying to flash recovery until I realized I needed to update Super User). I'm trying to download and install a ROM but every time I get to the boot into recovery phase the tablet just reboots normally. Is there a way to check and make sure the boot loader unlocker worked right? Should I just try TWRP and see how that goes? Does anyone know what the problem could be?
Nevermind this topic, going to pick up a TF700 right now so I'll just be tossing this prime. Start from scratch tonight.
Hi
I am having some issues with my Xperia Z2 D6502. I am new to rooting, so please bear with me.
I rooted my device following these instructions. All things went smoothly. However next day I started having problems to boot into recovery mode. I have explained my problem here. I tried reinstalling Z2-lockeddualrecovery2.7.154-BETA.installer which I got from the above instructions. It installed successfully but still I couldnt boot into recovery mode. The phone even stopped detecting my SD card, I had to reinsert it each time I would reboot to make it work.
So I followed all the instructions from the scratch again except for the last one which involved flashing pre rooted 5.1.1 stock ROM(flashable_D6502_23.4.A.0.546.zip). I wanted to keep rooted kitkat 4.4.2(I initially,i ..e., before rooting, had 5.1.1 but according to the instructions I had to downgrade it to kitkat) which I obtained as a result of downgrading my Xperia Z2 from 5.1.1.
Now I am facing wifi problems with kitkat. I can connect to the network but internet works extremely slow while it works absolutely fine on other devices. I dont have access to the router as its a common router in my dorm. I tried several solutions which I found on internet involving changing DNS to 8.8.8.8 and changing IP settings to static. None of them had any effect. Is there anything else I could do to resolve this issue?
The main reason I want to keep kikat is that I want to install Xposed on my device for imei changer and android id changer, and I read somewhere that for installing Xposed on kitkat you dont need to flash any zips and just install it like any other app. I didnt flash it on lollipop because of the warnings about getting stuck in bootloop in sony devices and I wasnt sure of how to flash it as the instructions were not very detailed and I am new to it. So do we flash it the same way I flashed 5.1.1 rom, i.e., booting into recovery mode and then selecting install and then selecting the zip I want to install?
I got this link to working modules on sony devices but I cant find imei changer in the list. So even if I installed Xposed, with your help of course, will I be unable to use imei and android id changer?
I read in several places that I should backup my device so that I can restore to the previous state in case I soft brick it or enter a bootloop. What kind of backup is this and how do I take it?(I googled and found Backup TA to take backup but I am not sure if that is the type of backup I am looking for and the instructions in the page are not detailed enough for me as I cant risk my device.)
I have one request, please provide me with detailed steps as I am doing all of it for the first time and am extremely nervous of screwing up my device as it is my only phone and quite expensive too.
Well, my device is rooted, on 5.1.1, and Xposed Works very well, without bootloops, and all Modules that I tried worked very well, by your description I can't figure out what is causing your problems...
stayawake said:
Well, my device is rooted, on 5.1.1, and Xposed Works very well, without bootloops, and all Modules that I tried worked very well, by your description I can't figure out what is causing your problems...
Click to expand...
Click to collapse
I havent tried Xposed on my device yet. Have you tried imei changer and android id changer? If not can you confirm if it works?
Can you please provide me with detailed step on how to install Xposed?
If my device goes into bootloop, will I be able to flash it using stock ROM?
And can you please provide answers regarding taking backup?
berbatov93 said:
I havent tried Xposed on my device yet. Have you tried imei changer and android id changer? If not can you confirm if it works?
Click to expand...
Click to collapse
I didn't tried these two modules.
berbatov93 said:
Can you please provide me with detailed step on how to install Xposed?
Click to expand...
Click to collapse
following the official topic of the module, you will have all the steps to install it, and the version that most fits with your system version
berbatov93 said:
If my device goes into bootloop, will I be able to flash it using stock ROM?
Click to expand...
Click to collapse
If you got a boot loop, you can:
1: Force power off the device by holding volume+ and power button simultaneously, then, you will able to flash via flashtool a new ROM
2: if you have a custom recovery, you can follow the same method to power off, then, power on and access the recovery, where you will be able to flash a zip containing a new system, etc.
berbatov93 said:
And can you please provide answers regarding taking backup?
Click to expand...
Click to collapse
Well, again, using a custom recovery you can make a Backup, the interface is very intuitive and easy to understand.
stayawake said:
I didn't tried these two modules.
Click to expand...
Click to collapse
Can you please try them?
If you got a boot loop, you can:
1: Force power off the device by holding volume+ and power button simultaneously, then, you will able to flash via flashtool a new ROM
2: if you have a custom recovery, you can follow the same method to power off, then, power on and access the recovery, where you will be able to flash a zip containing a new system, etc.
Well, again, using a custom recovery you can make a Backup, the interface is very intuitive and easy to understand.
Click to expand...
Click to collapse
Do we make custom recovery using the backup option we get when we boot into recovery menu?
And how to enter recovery menu without booting into the system? I access it using NDR utils app.
And do I need to flash any recovery zip from the recovery menu if I want to keep it?
berbatov93 said:
Can you please try them?
Do we make custom recovery using the backup option we get when we boot into recovery menu?
And how to enter recovery menu without booting into the system? I access it using NDR utils app.
And do I need to flash any recovery zip from the recovery menu if I want to keep it?
Click to expand...
Click to collapse
If you have Dual recovery, you are already running a custom recovery.
to enter the recovery menu whitout boot the system, you should:
Power On the device, and at the FIRST SONY screen, when the LED flashes, press volume up to enter TWRP
stayawake said:
If you have Dual recovery, you are already running a custom recovery.
to enter the recovery menu whitout boot the system, you should:
Power On the device, and at the FIRST SONY screen, when the LED flashes, press volume up to enter TWRP
Click to expand...
Click to collapse
Volume down for TWRP, volume up goes to the other one, CWM I think? I've never looked!
@berbatov93 you need a bit more patience and to read more things. Forums are awesome because you can get help from people all over the world but it rarely happens in real time.
stayawake said:
If you have Dual recovery, you are already running a custom recovery.
to enter the recovery menu whitout boot the system, you should:
Power On the device, and at the FIRST SONY screen, when the LED flashes, press volume up to enter TWRP
Click to expand...
Click to collapse
Its doesnt enogh to tap once volume up to enter to recovery ,when Sony logo shows he must tap few times volume up until notification led get purple color and phone goes in to recovery.This is procedure for Philzz Touch Recovery.
may i ask you something..did you unmount your memory card before you take it out?
if you want to have lastest version lolipop with root..
downgrade your phone to android lolipop 5.0.1..then follow this step http://forum.xda-developers.com/xperia-z1/general/root-xperia-running-lollipop-lb-ubl-t3123893..
then..
1. install busybox
2. turn on usb debugging and unknown source
3. find lolipop lastest version preroot...copy to your memory card (make sure to unmount it before you put it out) or just put the usb cable
4. install recovery (make sure to get lastest recovery.. can get it on nut.xperia-files.com/)
5. enter recovery then flash lastest pre root lolipop..
6. turn on your phone...
7.Good Luck
TA Partition Backup is for who want to unlock bootloader.. it backup DRM key which important for waranty.
Thank You, i hope this will help you
NamiDragneel said:
may i ask you something..did you unmount your memory card before you take it out?
if you want to have lastest version lolipop with root..
downgrade your phone to android lolipop 5.0.1..then follow this step http://forum.xda-developers.com/xperia-z1/general/root-xperia-running-lollipop-lb-ubl-t3123893..
then..
1. install busybox
2. turn on usb debugging and unknown source
3. find lolipop lastest version preroot...copy to your memory card (make sure to unmount it before you put it out) or just put the usb cable
4. install recovery (make sure to get lastest recovery.. can get it on nut.xperia-files.com/)
5. enter recovery then flash lastest pre root lolipop..
6. turn on your phone...
7.Good Luck
TA Partition Backup is for who want to unlock bootloader.. it backup DRM key which important for waranty.
Thank You, i hope this will help you
Click to expand...
Click to collapse
The DRM keys are unlikely to affect your warranty claim but they do other things including allowing your device to get OTA upgrades.
To unlock your bootloader you have to get an unlock code from Sony, to do that you give them your device details. So if you send it back for warranty and they look it up, I have no idea if they do, they'll see that you have unlocked your bootloader. Or at least got the code to do so, I doubt anyone gets the code without planing on using it.
Those DRM keys play a role in the Sony image processing for both the camera and the Bravia Engine. That is what you lose by unlocking the bootloader, warranty is not the major factor.
Hey
I had the same problem.
So what I did to solve this?
I did a factory reset > flash again flashable_D6502_23.4.A.0.546.zip > wipe dalvik >
And the problem was fixed.
Good luck
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Go to fastboot and boot into stock recovery, don't install. Just boot to recovery, command should be something like below.
fastboot boot recovery-name.img
If you can go to opx recovery, flash stock rom and see
tech_master said:
Hi everyone,
I was on Cyanogenmod and had disabled bootloader unlocking from development settings. After trying to update, I'm now stuck in recovery. While rebooting, the oneplus logo appears but later it just reboots to recovery. In fastboot, I can't flash anything because it says the bootloader is locked (I obviously can't fix that from settings because the phone won't boot). I'm able to get into TWRP so is there a way to enable bootloader unlocking using it?
Click to expand...
Click to collapse
Have you tried going through the steps for unlocking bootloader again?
Exodusche said:
Have you tried going through the steps for unlocking bootloader again?
Click to expand...
Click to collapse
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
tech_master said:
That didn't work. Had to flash the stock rom, re-enable unlocking, unlock and flash.
Click to expand...
Click to collapse
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
Ah no. You'll probably need to find someone who can re-sign CM so that it'll flash.
Thanks for the answer, I have no idea how to do this, how is this done? I don't seem to find much info online...
Sent from my HUAWEI TAG-L21 using Tapatalk
reebomber said:
I have the same problem, stuck in recovery, can't unlock, but worse: For some reason I have Cyanogenmod recovery installed, not TWRP. Now, can't install any stock rom. Tried from SD card and by sideload, but it seems that it just doesnt "stick" to /system. So, I am stuck in recovery, can't install CM, and can't unlock, to install TWRP.
Any ideas, other than getting a new phone tomorrow morning?
Thanks
Click to expand...
Click to collapse
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
yuv93 said:
NO Need To Worry by following this procedure you are going to install stock recovery. first, you have to download this zip.
link - https://www.androidfilehost.com/?fid=24269982087019810
after downloading this zip copy and extract it on your desktop (PC or Laptop). now switch OFF your opx and connect it with your pc by pressing vol Up button, you will find that pc installing some drivers if it install the drivers then you are going right. now after connecting your opx to pc open the extracted folder and open "MsmDownloadTool V2.0" . on opening this you will see the list of attached devices (for ex. com device and if your device is not connected then it will show No device). If you your device is attached then you have to click on START Tab on left top corner. it takes 30 ~ 40 Sec to complete the whole process after that your opx restart with installed stock recovery. through this recovery you can flash H2OS and OOS. If you want to install TWRP first of all you have to install oos or H20s after flashing, you have to allow oem unlock in developer setting.
Click to expand...
Click to collapse
Thank you. I had tried this procedure previosuly, and didn't work. This time, since you insisted, I tried again, on another computer, and the phone was correctly detected, drivers installed and factory image installed on phone. I am happy again
Hey guys, I'm facing an issue right now.
I had a rooted OPX with TWRP and Lolipop. I downloaded the new OOS 3.1.3 from OnePlus site, flashed it. There was an error, fixed it by updating updater-script. Flashed the zip, then just after that flashed SuperSU zip and TWRP image over recovery. I don't know why I did that but that's the order. Then I forgot to wipe Dalvik/Cache and rebooted into recovery...It stuck in OnePlus Logo screen with powered by android written at bottom. Then I tried to boot into System by pressing the power button, it got stuck in the boot animation (The new one in Marshmallow update). It just keeps rotating infinitely (I think). I have waited for about 30 minutes on that screen, no luck.
What should I do? Is there a way that fastboot mode would be recognized by my PC and I can boot into recovery via image? Or any way for factory reset? Data is all backed up, so no issue about that. Just need it to get running asap.
Please reply asap.
Thanks for reading.
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Joshwin Aranha said:
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Click to expand...
Click to collapse
Just as I mentioned, booting into recovery doesn't work. Stuck at the OnePlus Logo Screen if I do that manually.
Though I can boot into fastboot. But after doing that, when I connect the phone to the PC, fastboot devices command returns an empty line.
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Exodusche said:
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Click to expand...
Click to collapse
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
choubeyaakash77 said:
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
Click to expand...
Click to collapse
You have to use the modded SuperSU. You can find it in the many guides posted for oos3.