Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Seleren said:
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Click to expand...
Click to collapse
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Lucky Thirteen said:
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
Click to expand...
Click to collapse
I have the International model.
jbharbin said:
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Click to expand...
Click to collapse
Tried that already, nothing changed at all, TWRP logo shows up and then the phone reboots to ROM. CWM works partially as I said, it reboots when I tell it do do anything (backup/wipe/flash) and the phone is unaffected.
Bump. Help please, I tried flashing another kernel but that didn't help. I can't even wipe or flash another ROM in CWM.
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Try redownloading the recovery and rewriting it. It may be a bad download.
Sent from my One X+ using xda premium
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Flash the kernel and then the recovery with fastboot and see what happens.
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
@Seleren I would be interested to know if the above worked for you? Also useful if anyone else gets this problem
Lucky Thirteen said:
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
Click to expand...
Click to collapse
I've already tried that numerous times, I can get to erasing cache etc but once I try to boot into the recovery ... I'm done. TWRP won't boot even after erasing cache. CWM fails at wiping/backuping/flashing and just reboots without any notice at all. I'm really out of ideas now.
Sorry for a bit late answer.
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
Seleren said:
Hello there,
... A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery....
Click to expand...
Click to collapse
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Lucky Thirteen said:
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Click to expand...
Click to collapse
Yes, I am correctly rooted, I've rooted numerous phones, I unlocked using the official HTC method. I could say I'm not a complete noob to Android. I wouldn't even post here if I didn't try all the standard procedures.
I flashed the Non-touch CWM yesterday and nothing changed (not that I expected it to). I decided I'll try flashing the bootloader in the end but I have to back up my whole SDCard before that ...
Bump.
SALVATION
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
hukel56 said:
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
Click to expand...
Click to collapse
wut?! TWRP = Recovery
boot.img = KERNEL
Seleren said:
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Click to expand...
Click to collapse
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Lloir said:
wut?! TWRP = Recovery
boot.img = KERNEL
Click to expand...
Click to collapse
Yea idk. But this happens
Lloir said:
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Click to expand...
Click to collapse
I wish that was the problem, I tried quite a few versions, including the one from ALL IN ONE toolkit, an older version that previously worked, the latest version and the ViperX version. Trust me, that was not the problem.
hukel56 said:
Yea idk. But this happens
Click to expand...
Click to collapse
What Lloir meant to say was that the boot.img has nothing to do with the recovery, so flashing a boot.img will NOT change your recovery to so-said TWRP.
TWRP is being flashed by a different command namely 'flash recovery' instead of 'flash boot' like previously mentioned boot.img
Related
Alright, so i have an EVO 4g lte and i attempted to root it today. It didnt turn out very well to say the least... I unlocked bootloader and flashed TWRP recovery.I then flashed superSU, and at the same time i flashed a custom rom and gapps zip. Then hit reboot. It has not booted up since.. It will just sit at the white HTC screen. i tried clearing cache and Dalvik cache, also did a factory reset. tried flashing cm10 rom onto the device as well as a rooted stock rom. nothing works! the farthest i have gotten was with the cm10 rom and it went to the cyanogenmod boot logo but was in bootloop still. I downloaded the ADT tool bundle but the phone wont show up on the device list. Can anyone help? im completely stumped.. Im fairly new to rooting and custom roms, but i have rooted multiple tablets and samsung galaxy phones and havent had any issues. this is my only phone also, i just gave my backup to my mother because her phone broke... please if anyone knows how to fix this let me know. when i boot into recovery mode it says Tampered and Unlocked at the top as well as S-On. I can also go into TWRP recovery with no problems. just cant use fastboot with my computer (windows 7 PC).
I am pretty sure i know what i did wrong, I flashed SuperSU to gain root at the same time i flashed the custom rom and gapps.. on all the other devices i would reboot after root and then flash the custom rom seperately.. but is there a way to correct my mistake?
Since you are s-on you have to fastboot flash the boot.img/kernel first and then flash CM and gapps
Any questions PM me
OK sorry to be a noob but how do I do that? I used cmd.exe while rooting but now it won't recognize my device. Much thanks for any help!!
Sent from my GT-P5110 using xda app
If in bootloader type fastboot devices
In recovery type adb devices
See if you get a reply
In fast boot USB menu on the phone, I typed fastboot devices on cmd and it came up blank.
Sent from my GT-P5110 using xda app
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
bigdaddy619 said:
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
Click to expand...
Click to collapse
ok ill uninstall all that and give it a try. is pm a better contact method for you?
AUSRA15 said:
ok ill uninstall all that and give it a try. is pm a better contact method for you?
Click to expand...
Click to collapse
Here is fine
bigdaddy619 said:
Here is fine
Click to expand...
Click to collapse
OK rebooting now I'll see if it uninstalled everything.
:fingerscrossed:
OK were connected now, now what? :good:
PC and phone are talking ?
fastboot devices
yes they are talking now. fastboot devices and my phone shows up.
i tried fastboot flash boot.img but it wont recognize the command, i placed the boot.img file into the platform-tools folder inside my C drive. what am i doing wrong? its late at night and im frustrated so i know im screwing something up...
ok good BTW which version of twrp are you using? Let me know before you continue.
pull the boot.img from the rom zip and copy it to the folder you opened your cmd window from
then type fastboot boot boot.img
once it says successful press the power button to return to HBOOT and use the vol keys to navigate to recovery
Once there choose wipe and wipe cache/dalvik cahce/system/data or factory reset depending which version of twrp you are using
then flash CM and gapps
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
AUSRA15 said:
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
Click to expand...
Click to collapse
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
bigdaddy619 said:
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
Click to expand...
Click to collapse
same thing, cannot load unknown error. also i am using twrp 2.6.0.0
Ok lets try something different at least it will get you up and running
Get twrp v2.4.1.0 from http://techerrata.com/browse/twrp2/jewel
put it in the same folder you are using and we will downgrade your twrp for now
copy and paste this in the cmd window
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
then fastboot erase cache
ok got the twrp done succesfully as well as the wipe cache. whats next? i think i figured out what i was doing wrong, i hadnt opened the file directory. cd downloads, cd android files, etc.
should i try going into recovery now on the phone and flash a rom, or should we stay on fastboot and push the boot.img?
Easiest way to open a cmd window is to press shift and right click inside the folder and choose open cdm window here
That way you know you are in the correct folder.
Yeah go ahead and try to flash the boot.img again
Okay, I need some help here with my One X+. Here's what happened: I tried installing a kernel and messed it up (pretty sure), then tried restoring it from a backup. Didn't work. Then I wiped the device. Then I sent a rom through adb to the sdcard and tried installing it. Nothing, happened, told me I have no OS installed. So right now my situation is that my i don't know what to do to fix my device. I think i have to install a different kernel and rom that work together but not 100%, some clarification would be nice. I can use adb and fastboot and have access to TWRP.
Device Specs:
Rooted
Unlocked Bootloader
HTC One X+ International Version 64gig Space
If nobody reply's soon I'll delete this thread, although like 60 people have looked at this thread.
EpicGuitar said:
Okay, I need some help here with my One X+. Here's what happened: I tried installing a kernel and messed it up (pretty sure), then tried restoring it from a backup. Didn't work. Then I wiped the device. Then I sent a rom through adb to the sdcard and tried installing it. Nothing, happened, told me I have no OS installed. So right now my situation is that my i don't know what to do to fix my device. I think i have to install a different kernel and rom that work together but not 100%, some clarification would be nice. I can use adb and fastboot and have access to TWRP.
Device Specs:
Rooted
Unlocked Bootloader
HTC One X+ International Version 64gig Space
Click to expand...
Click to collapse
Try this send a ROM as u did through adb and install it and flash the appropriate Kernel for that ROM....
The kernel has to be flashed seperately from fastboot mode........
or If u have the nandroid backup restore that and copy the boot.emmc.win from the TWRP backup folder to PC
flash the boot.emmc.win from fastboot mode.....
both would get ur phone boot....
Try this send a ROM as u did through adb and install it and flash the appropriate Kernel for that ROM....
The kernel has to be flashed seperately from fastboot mode........
or If u have the nandroid backup restore that and copy the boot.emmc.win from the TWRP backup folder to PC
flash the boot.emmc.win from fastboot mode.....
both would get ur phone boot....
Click to expand...
Click to collapse
I can flash the ROM but how do i flash the kernel, look I'm not very good at these things so don't go far out with the terms.
EpicGuitar said:
I can flash the ROM but how do i flash the kernel, look I'm not very good at these things so don't go far out with the terms.
Click to expand...
Click to collapse
after flashing the ROM
reboot to bootloader then connect ur phone to pc
it will show as fastboot usb on ur phone
now copy the kernel to the folder where u had installed the fastboot
open the CMD prompt on ur PC navigate to fastboot folder
In cmd type the following command
fastboot flash boot boot.img(boot.img is the filename of ur kernel)
fastboot erase cache
reboot ur phone
[email protected] said:
after flashing the ROM
reboot to bootloader then connect ur phone to pc
it will show as fastboot usb on ur phone
now copy the kernel to the folder where u had installed the fastboot
open the CMD prompt on ur PC navigate to fastboot folder
In cmd type the following command
fastboot flash boot boot.img(boot.img is the filename of ur kernel)
fastboot erase cache
reboot ur phone
Click to expand...
Click to collapse
I will try this thank you very much for being one of out the 115 people who looked at this thread who actually responded.:good:
[email protected] said:
after flashing the ROM
reboot to bootloader then connect ur phone to pc
it will show as fastboot usb on ur phone
now copy the kernel to the folder where u had installed the fastboot
open the CMD prompt on ur PC navigate to fastboot folder
In cmd type the following command
fastboot flash boot boot.img(boot.img is the filename of ur kernel)
fastboot erase cache
reboot ur phone
Click to expand...
Click to collapse
I did flash the rom and it worked fine. The kernel I downloaded was automatically flashed the boot.img for using windows.bat. But when I go to reboot the device TWRP tells me that my phone has no OS...
Go to Viper ROM Thread in Development Section (http://forum.xda-developers.com/showthread.php?t=2122390) and download the ROM, then download Kernel and Recovery Flasher (http://d-h.st/rNC).
Start Kernel and Recovery Flasher as Administrator on your PC, change to manual mode and put in the fields out of the downloaded files of the flasher (boot.img, modules folder). Put the ROM on your SD via adb, start again in TWRP and flash the ROM.
I assume you flashed your boot.img with kernel you tried to install, so only install a ROM does not help....
Hope it helps!
Yezariael said:
Go to Viper ROM Thread in Development Section (http://forum.xda-developers.com/showthread.php?t=2122390) and download the ROM, then download Kernel and Recovery Flasher (http://d-h.st/rNC).
Start Kernel and Recovery Flasher as Administrator on your PC, change to manual mode and put in the fields out of the downloaded files of the flasher (boot.img, modules folder). Put the ROM on your SD via adb, start again in TWRP and flash the ROM.
I assume you flashed your boot.img with kernel you tried to install, so only install a ROM does not help....
Hope it helps!
Click to expand...
Click to collapse
Funny thing is that viper rom was the ROM that i installed and the kernel... Oh well I'll try this method too. Thanks for the help! (I'll try to spam your thanks button for that!) :good:
EpicGuitar said:
Funny thing is that viper rom was the ROM that i installed and the kernel... Oh well I'll try this method too. Thanks for the help! (I'll try to spam your thanks button for that!) :good:
Click to expand...
Click to collapse
So after installing the ROM did u wipe any of the partitions....????
after installing just wipe the cache and dalvik cache and nothing else
DONT EVER WIPE SYSTEM AND DATA AFTER A FRESH INSTALL
if u do so u ll get that message NO OS installed.....
[email protected] said:
So after installing the ROM did u wipe any of the partitions....????
after installing just wipe the cache and dalvik cache and nothing else
DONT EVER WIPE SYSTEM AND DATA AFTER A FRESH INSTALL
if u do so u ll get that message NO OS installed.....
Click to expand...
Click to collapse
Why not?? TWRP don't touches your user data, and the other wipes never ever kill you OS... (Sure it makes no sense to delete after installing ROM before 1st startup...)
Yezariael said:
Why not?? TWRP don't touches your user data, and the other wipes never ever kill you OS... (Sure it makes no sense to delete after installing ROM before 1st startup...)
Click to expand...
Click to collapse
I said wiping the SYSTEM and DATA is unnecessary(stupid)...after an INSTALL
[email protected] said:
So after installing the ROM did u wipe any of the partitions....????
after installing just wipe the cache and dalvik cache and nothing else
DONT EVER WIPE SYSTEM AND DATA AFTER A FRESH INSTALL
if u do so u ll get that message NO OS installed.....
Click to expand...
Click to collapse
No I didn't wipe the system or data after the install. Yet it still tells me no OS.
EpicGuitar said:
No I didn't wipe the system or data after tit he install. Yet it still tells me no OS.
Click to expand...
Click to collapse
I installed the ViperX+ Rom, that went smoothly, then I extracted the Kernel_Flasher and started the Venom Flasher went to manual mode and selected the boot image and recovery image the process is fine until it finishes installing then turns off my phone and tries to start in fastboot mode, however the device ignores that and tries booting normally. I tried booting in TWRP but it tells me still no OS.
EpicGuitar said:
I installed the ViperX+ Rom, that went smoothly, then I extracted the Kernel_Flasher and started the Venom Flasher went to manual mode and selected the boot image and recovery image the process is fine until it finishes installing then turns off my phone and tries to start in fastboot mode, however the device ignores that and tries booting normally. I tried booting in TWRP but it tells me still no OS.
Click to expand...
Click to collapse
Just reboot in bootloader mannually using power + volume up.choose fastboot . Then when is there flash kernel. It may tell you that it can't find device what u do is close that window and then it will flash.
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:23 PM ---------- Previous post was at 07:19 PM ----------
EpicGuitar said:
I installed the ViperX+ Rom, that went smoothly, then I extracted the Kernel_Flasher and started the Venom Flasher went to manual mode and selected the boot image and recovery image the process is fine until it finishes installing then turns off my phone and tries to start in fastboot mode, however the device ignores that and tries booting normally. I tried booting in TWRP but it tells me still no OS.
Click to expand...
Click to collapse
Or simply try another rom and flash kernel manualy or use a tool that does it for you.
Sent from my HTC One X+ using xda app-developers app
grigoriisi said:
Just reboot in bootloader mannually using power + volume up.choose fastboot . Then when is there flash kernel. It may tell you that it can't find device what u do is close that window and then it will flash.
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:23 PM ---------- Previous post was at 07:19 PM ----------
Or simply try another rom and flash kernel manualy or use a tool that does it for you.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
So when the venom flasher is waiting for fastboot mode i just close the Venom Flasher program?
EpicGuitar said:
So when the venom flasher is waiting for fastboot mode i just close the Venom Flasher program?
Click to expand...
Click to collapse
i never used that. i can only comment on my experience. i use other rom. and my kernel flasher is hasoons tool for one x plus.
Since nobody willing to help me anymore, i'm going to have go back to my old galaxy y, not enough money for a new hox, thanks to all the people who answered atleast.. none of the 1500 people who viewed this thread can't provide more answers..
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
choubeyaakash77 said:
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/oneplus-x/general/oos-2-2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
If you can enter in fastboot mode, flash the recovery from fastboot command. Flash blu_sparks recovery, it's better
seems you can still go to TWRP recovery? just flash the OOS 2.2.0 full ROM.
choubeyaakash77 said:
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
Obviously...
You told the phone to boot to TWRP by flashing it to 'Boot' and that's exactly what is happening.
Just reflash your ROM and you're good to go.
choubeyaakash77 said:
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
Click to expand...
Click to collapse
If you didn't know what you were doing, why ask before doing it?
You always have to flash the recovery .img from fastboot mode via adb. Not flashed by twrp.
Reference thread :
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Maybe, just flash from adb the OLD recovery.
From this recovery, reinstall your Save.
Then install new recovery via ADB.
Or flash full ROM, then reflash, VIA ADB, the OLD recovery.
Then same as above. Restora + new recovery.
Boot your phone into fastboot mode, connect it to the PC, in adb directory, open cmd promote, type
fastboot flash recovery twrp. img
Click to expand...
Click to collapse
(replace twrp. img to the recovery img you downloaded, and put it under the adb directory). Or you can type
fastboot boot twrp.img
Click to expand...
Click to collapse
, the phone will then boot into the recovery you downloaded, where you can flash a new rom. DON'T flash recovery from recovery!
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
And if you want restore the backup on th sdcard, you might need change the storage location to sdcard in TWRP recovery,
Thanks all you guys. I'm back on with OOS 2.2.0. Had to download the complete ROM and flash it through TWRP.
I didn't wanted to download a whole almost 1 GB zip, so I tried to search for the original OxygenOS boot.img to flash it to boot. It might have worked if I hadn't completely wiped out my OS by wiping /system. Plus its almost impossibe to find that file online...
Anyway, had a nice experience screwing things up and getting back up better than before. Had fun. Learned stuff...so probably I'm not a newbie to rooting anymore.
Thanks guys for your support.
Here's the ROM I downloaded (for future reference) : https://www.androidfilehost.com/?fid=24389512218017971
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
FixFaier said:
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
Click to expand...
Click to collapse
fking hell.
this helped me a lot.
thx man :good:
Thank you so much. For now just gonna be content witht the stock rom.
I was into the process of rooting my XT1506. Unlocked the bootloader and installed twrp successfully and then in an attempt to installing custom rom via Fastboot, i run the command
fastboot -w
and then when i tried to run "fastboot update rom.zip", it didn't succeed. After that, whatever i do, the phone just boots into recovery and never into the system. Badly need your help, Guys....!!! I shall be really thankful.....
I think i made the thread in wrong section and now i cant find the option to move/delete it. I apologize Mods for this mistake and request them to move it.
aanishjangra said:
I was into the process of rooting my XT1506. Unlocked the bootloader and installed twrp successfully and then in an attempt to installing custom rom via Fastboot, i run the command
fastboot -w
and then when i tried to run "fastboot update rom.zip", it didn't succeed. After that, whatever i do, the phone just boots into recovery and never into the system. Badly need your help, Guys....!!! I shall be really thankful.....
Click to expand...
Click to collapse
If you still have twrp installed, you can wipe everything and flash the custom ROM from the recovery itself.
Tried that too...still it boots into recovery...One more thing i have noticed that in fastboot mode, clicking on "Factory" boots the phone normally.
Is there any problem related with recovery. I have presently Flyrom 5.1.2 installed and recovery is 3.0.1 (also tried twrp-otus-2.7.x), if that helps..
Download any Custom ROM (Lineage OS recommended)
Put that in your SDCard or Internal Storage (USB MTP works in recovery mode)
Go To Wipe Section and check All (Excluding Internal Or MicroSD)
Swipe to format
Then Press the HOME Button
Click on Install
Go to the path where ROM is (Root of the storage is best)
Flash the ROM
Wipe cache/Dalvik Cache (Must Do This)
First Boot may take 15-20 min...
Enjoy :fingers-crossed:
Hit Thanks If I Helped you
Problem solved. I think it was a problem with the recovery. I achieved the solution by flashing stock recovery. Now the phone is booting normal.
I am curious if anybody can suggest me a compatible recovery for this phone. By the way, thanx to all who helped me....You are awesome
Go for this : Recovery
And thread here : https://forum.xda-developers.com/moto-e-2015/orig-development/twrp-recovery-moto-e-3g-2015-t3084849
shaktiman01 said:
Go for this : Recovery
And thread here : https://forum.xda-developers.com/moto-e-2015/orig-development/twrp-recovery-moto-e-3g-2015-t3084849
Click to expand...
Click to collapse
That is the same recovery which caused the problems. Anyways, i'll try to put that in again and see if there'll be any difference. Btw, thanx mate..
@ aanishjangra try squid2's port of the recovery and see if it helps, although ensure you flash the recovery and immediately reboot to recovery (Not system) and the ROM gets patched.
aanishjangra said:
I was into the process of rooting my XT1506. Unlocked the bootloader and installed twrp successfully and then in an attempt to installing custom rom via Fastboot, i run the command
fastboot -w
and then when i tried to run "fastboot update rom.zip", it didn't succeed. After that, whatever i do, the phone just boots into recovery and never into the system. Badly need your help, Guys....!!! I shall be really thankful.....
Click to expand...
Click to collapse
https://chat.whatsapp.com/AimXKJXu6uUJp6qOvBeOan
Join whtsapp group if u need any help!!