Hi,
I've Xperia Pro MK16i, with stock 4.0.4 ROM, boot loader unlocked and rooted.
I really want to install recently released CM9-RC1 ROM but have been unsuccessful probably due to CWM recovery.
I was only able to install CWM auto installer which would only boot into recovery if i do it from within booted stock rom, but not manually when i reboot and try to go into recovery mode. i tried all key combinations like volume key down/up when at reboot sony logo flashes bright and led turns blue for a second.
Nevetheless i tried to install CM90RC1 by following official cyanogenmod instructions in which i failed when the guidelines states to fastboot and flash boot.img extracted from CM9-RC1.zip file and then reboot from fastboot. it just stuck there and would not even flash sony logo.
I relocked the bootloader and installed the stock ROM through Sony PC companion repair option.
Now i have again unlocked the bootloader and rooted. but not sure how to proceed now.
I guessed may be i need custom ROM with CWM recovery builtin. i came across this site
http://forum.xda-developers.com/showthread.php?t=1315904&highlight=108
kindly guide me if the link above will help me installing Cyanogenmod ROM and does it come with CWM recovery built in.
Also whats the difference between multiple downloads on the above link like FXP129 and CM9 baseband?
What files do i have to download now, to install Cyanogenmod ROM?
Regards
Hey guys,
I'm currently on OxygenOS 3, and wanted to flash cm14 by Ashwin. I used flashify, rashr to flash bluspark v41 and other oos3 compatible recoveries but the phone just wouldn't boot in the recovery, the OnePlus splash screen shows up for a second and phone boots back into the system.
Now, what I can do:- I can flash stock mm recovery and flash oos 2 but then I would lose the new bootloader and hence won't be able to boot into CM14, hence failing the actual purpose. Please help, I'm getting very frustrated.
Thanks.
Go to fastboot mode and flash bluespark recovery... After doing that boot into it directly
Before doing the above check for ur bootloader information oem unlock
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
funkyhunky said:
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
Click to expand...
Click to collapse
Go into developer options and enable OEM unlocking
---------- Post added at 02:26 AM ---------- Previous post was at 02:17 AM ----------
funkyhunky said:
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
Click to expand...
Click to collapse
I have just now read your post thoroughly you said that the touchscreenis buggy,is it twrp or in the system
If it's twrp don't worry I too have the same problem in the version I tried eg. 3.0.2.0,3.0.1.0,3.0.0.0
But if it's in system try factory resetting
And change smart power saving mode to performance
But to unlock frp(i suppose you have already unlocked your bootloader) just go into developer options and enable OEM unlocking option
Ok I got the stock recovery back:
I booted into the bootloader and used the local command window to fastboot boot a twrp image from my computer
With TWRP booted (but not installed) on my phone I put in a sd card with a stock recovery image, and used the booted TWRP to install the stock recovery
Unfortunately, I have not figured out how to relock the boot loader, but hopefully they overlook/don't care about that for a return - I did not root the phone
U can relock bootloader in honor5x
I think I have a similar problem. I bought new KIW-L24, I unlocked bootloader, flashed twrp to go to RR Nougat ROM. When I started Twrp to install ROM it said "Comparing tarz 2.2 to 2.5" so I read that I had update to MM.
I went to settings>updater and started update to M331 EMUI 4.0 ROM on the twrp recovery instead of stock recovery. I have M331 ROM now but I can't fastboot the TWRP recovery anymore. It sat twrp installed successful but the EMUI Stock recovery opens up when hitting Vol. + and Power instead of Twrp.
I noticed fastboot menu shows Phone unlocked but it does not say FRP Unlocked anymore. Does that prevent me from installing custom recovery now? Please...any help is appreciated.
cyrusalmighty said:
I think I have a similar problem. I bought new KIW-L24, I unlocked bootloader, flashed twrp to go to RR Nougat ROM. When I started Twrp to install ROM it said "Comparing tarz 2.2 to 2.5" so I read that I had update to MM.
I went to settings>updater and started update to M331 EMUI 4.0 ROM on the twrp recovery instead of stock recovery. I have M331 ROM now but I can't fastboot the TWRP recovery anymore. It sat twrp installed successful but the EMUI Stock recovery opens up when hitting Vol. + and Power instead of Twrp.
I noticed fastboot menu shows Phone unlocked but it does not say FRP Unlocked anymore. Does that prevent me from installing custom recovery now? Please...any help is appreciated.
Click to expand...
Click to collapse
Just delete the google account in your phone and do a factory reset. Later reboot but skip adding gmail . This will unlock frp .
gopinaidu77 said:
Just delete the google account in your phone and do a factory reset. Later reboot but skip adding gmail . This will unlock frp .
Click to expand...
Click to collapse
Can the frp relocking stop me from flahing twrp? Or is it this stock rom I am on? Do you know if other people have problems flashing twrp on L24 B311 MM update? Could I have caused my issue when I updated to the official rom using the twrp? I didn't think the update would work without stock recovery but it did. I did factory resets but I still can't install install any custom recovery. Can I go back to earlier stock rom?
I followed your instructions and deleted Google accounts and factory restored. I go to bootloader and it says Phone Unlocked but does not say FRP unlocked anywhere. I flshed twrp anyways and although cmd window shows it flashed OK when I reboot the stock EMUI Recovery opens again.
Edit: Now I use adb and mfastboot.exe to open twrp and do a backup. I don't know if I install a different rom if I will able to finally install twrp. I wonder if this 331 stock rom is the problem or FRP is issue here. Never had this problem with my Gold Honor 5X.
cyrusalmighty said:
I followed your instructions and deleted Google accounts and factory restored. I go to bootloader and it says Phone Unlocked but does not say FRP unlocked anywhere. I flshed twrp anyways and although cmd window shows it flashed OK when I reboot the stock EMUI Recovery opens again.
Edit: Now I use adb and mfastboot.exe to open twrp and do a backup. I don't know if I install a different rom if I will able to finally install twrp. I wonder if this 331 stock rom is the problem or FRP is issue here. Never had this problem with my Gold Honor 5X.
Click to expand...
Click to collapse
Plz boot recovery first and install recovery from twrp . This may do some help
gopinaidu77 said:
Plz boot recovery first and install recovery from twrp . This may do some help
Click to expand...
Click to collapse
Ok. Ive never done this this way. When installing Twrp image it asks where to install? Select Partition to Flash image: Boot, OEMinfo, or Recovery. Do I just press Recovery only?
cyrusalmighty said:
Ok. Ive never done this this way. When installing Twrp image it asks where to install? Select Partition to Flash image: Boot, OEMinfo, or Recovery. Do I just press Recovery only?
Click to expand...
Click to collapse
Select only recovery
ok I installed image, chose recovery, and installed superSU_2.46.zip but it still only boots up EMUI Stock recovery. Unfortunately its stuck in bootloop now so now I cant even adb/fastboot into twrp anymore. Now my only option is holding vol +- and Power to install update from sd card (dload folder). I just dont kmow what FW file to use.
cyrusalmighty said:
ok I installed image, chose recovery, and installed superSU_2.46.zip but it still only boots up EMUI Stock recovery. Unfortunately its stuck in bootloop now so now I cant even adb/fastboot into twrp anymore. Now my only option is holding vol +- and Power to install update from sd card (dload folder). I just dont kmow what FW file to use.
Click to expand...
Click to collapse
Fastboot boot recovery.img dint helped?
gopinaidu77 said:
Fastboot boot recovery.img dint helped?
Click to expand...
Click to collapse
I ended up trying everything. I held volume - and Power to force Fastboot&Rescue Mode. I did fastboot boot twrp_kiwi.IMG. When in Twrp I install twrp_kiwi.IMG (For permanent Install) but EMUi recovery still stays.
I believe the custom recovery is installing but NOT where it needs to install.(Probably a different partition). I noticed a erecovery when I extracted an update file with HuaweiExtractor with does program. I DID get out of Bootloop by applying update from SD card (Force Update Volume - and Plug in USB cable). I rolled the FW back to B130 Emui 3.1 Firmware. I still need to fash Twrp and update this phone now.
cyrusalmighty said:
I ended up trying everything. I held volume - and Power to force Fastboot&Rescue Mode. I did fastboot boot twrp_kiwi.IMG. When in Twrp I install twrp_kiwi.IMG (For permanent Install) but EMUi recovery still stays.
I believe the custom recovery is installing but NOT where it needs to install.(Probably a different partition). I noticed a erecovery when I extracted an update file with HuaweiExtractor with does program. I DID get out of Bootloop by applying update from SD card (Force Update Volume - and Plug in USB cable). I rolled the FW back to B130 Emui 3.1 Firmware. I still need to fash Twrp and update this phone now.
Click to expand...
Click to collapse
So the frp lock still exists is it?
gopinaidu77 said:
So the frp lock still exists is it?
Click to expand...
Click to collapse
Yes I think the FRP Lock is on. It only says: Phone Unlocked. Before it used to say hone Unlocked and FRP unlocked.
cyrusalmighty said:
Yes I think the FRP Lock is on. It only says: Phone Unlocked. Before it used to say hone Unlocked and FRP unlocked.
Click to expand...
Click to collapse
Have u removed gmail account ?
gopinaidu77 said:
Have u removed gmail account ?
Click to expand...
Click to collapse
Yes I had removed gmail account. I went to settings>accounts and deleted Google and all other accounts. Does FRP Unlock when you unlock Bootloader?
cyrusalmighty said:
Yes I had removed gmail account. I went to settings>accounts and deleted Google and all other accounts. Does FRP Unlock when you unlock Bootloader?
Click to expand...
Click to collapse
U can try that
My story:
1. I flashed my device with custom twrp recovery image before and was working normal.
2. Rooted the phone with supersu using that recovery image.
3. Flashed custom ROM to replace android 6.0 with 7.1, worked but got problem with file manger in custom ROM
4. Flashed new recovery image for android 7.1 as mentioned in the thread.
5. Again flashed same custom ROM but device start booting to new twrp recovery instead of regular ROM boot
6. Tried to flash old recovery image in order to fix the no. 5 problem.
In fact I accidentally flashed wrong recovery image which was for another Motorola device.
I cannot access recovery now, neither I can charge my phone.
Whenever I plug USB cable in my phone, Lenovo logo shows up and disappear, just stuck in boot loop
My phone Information:
Model: Lenovo A7010a48
Any Idea to access fastboot?
Did I just missed my phone?
I had RNE-L21C185 with Stock Oreo updated
Then flashed Mofruz latest rom working fine, but then I tried to install Stock recovery, I was not able to do so
as it would show error with partition etc. Then tried to install the same TWRP from Morfuz ROM back again.
In fastboot mode I already have PHONE Unlocked and FRP Unlocked messages
So either Morfuz ROM TWRP or any other TWRP recovery, show properly completion of flash command
But when tried to boot into recovery it goes in a loop (the loop shows phenom image, then shows the default
screen that is shown before launching of recovery), then restarts again, and it goes on loop.
So I dont know why I cannot get to load into any of TWRP I have.
The ROM is working fine, if I properly shutdown mobile and start it again, it boots to the phone and
I can use my phone as normal.
Any help guys ?
try to flash stock rom via hisuite
http://huawei-firmware.com/rom/huawei-mate-10-lite/rnel21/8437
or try one of these twrp
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view
https://mega.nz/#!OzQ3GCJK!ofjiXcb7VRpGkhrd1vwXrVeSAO2vF1BVYLYRX2fExn4
.
Thanks problem solved by:
Tried to use fastboot command to flash official stock Kernal and ramdisk (Oreo version) phone got no OS after it as
it will go on bootloop, now even the forced download (dload folder) method wont work, factory data reset wont work
(both of above will show EMUI circle with no processing or text whatsoever)
At this stage, flashed Catuva recovery from Morfuz ROM again, and it worked