Australian Telstra RazrM. I am trying to update it to a recent android build. Preferably KitKat. I have tried several recoveries and ROMs. The recoveries flash OK. But I get various errors when trying to flash the ROMs. Cannibal Open touch JBBL and then CWM 6.0.3.2 are the two recoverys I tried. Then the ROM [cm-11-20150203-NIGHTLY-moto_msm8960_jbbl]. But it keeps coming up with errors saying incompatible data on device and so forth. Tried a non jbbl CM ROM but is was incompatible becuase it was xm907.
Not sure where I am going wrong. Could someone please suggest a compatible recovery and ROM combination to get KitKat on my Australian xt905 razr.
You are wiping everything except external sd and then flashing from external, correct? If not give it a try. I'm using xt907 not 905 but it worked for me when my first cm12 nightly got stuck on boot animation
I am being using CarbonROM for quite a while. It is very stable (not rock-solid though).
And I have used different recoveries and all work, I don't think that combination matters.
Just download any of the latest recovery compatiable with your bootloader version and you are good to go.
How do ascertain my bootloader version? I unlocked the factory bootloader using Motorola website unlock tool but have not loaded a differnt one. But I am not sure what version it is.
Currently have CWM 6.0.3.2 as a recovery but my next step (when I get hold of the handset again) is to try flashing "recovery-clockwork-6.0.4.4-xt907" which is a bit newer. then hopefully it will work.
I think I just wiped all user data. Next time will see if there are other options to wiper everthing bar external SD which I ma loading from. Thnx guys.
EDIT: Flashed "recovery-clockwork-6.0.4.4-xt907" , Cleared user data and cache and successfully flashed "cm-11-20150203-NIGHTLY-moto_msm8960_jbbl" . Yay!!
Now I just need a suitable Gapps package and all good.
Related
Hi XDA, I'm a relatively new owner to Android phones (3 weeks) and have a problem that I can't find any leads on.
I cannot flash any Touchwiz-based ROMS without the phone going into a boot loop and having to reflash via Odin. I know that AOSP ROMS work fine because I use goomanager to flash CM10, Carbon, and Liquid smooth previously. The problem only occurs with touchwiz roms. Here is the rundown of how I noticed the problem:
I download Crash ROM and move it to my internal SD card. I install TWRP via goomanager. I then use goomanager to wipe the data, cache, and dalvik cache, and to install the Crash ROM zip. The phone gets to the samsung logo then gets stuck in a boot loop.
I reflash it through Odin using the tutorial at GalaxyS4root and it boots fine. I use goomanager to reinstall TWRP and try flashing it through TWRP instead, again doign a full wipe of the data, system, cache, and dalvik cache. Same thing occurs and I reflash through Odin.
Fast-forward to last night; I decide to try another Touchwiz rom, this time Wicked ROM. I download it and put it on the internal SD card; using TWRP I wipe it again, and install it. Aroma Installer comes up and I make sure to select AT&T as my carrier. I get to the end of the installation and the phone reboots. This time its much worse than it was with Crash ROM, the phone is vibrating to signal it starting up, but the screen stays blank and then a few seconds later it vibrates again. This repeats constantly and the phone also couldn't boot into recovery mode (but it could boot to download mode). So I tried reflashing it twice, but the issue persisted. Through google I determined it to be a stuck power button. I've returned the phone to AT&T to be replaced for faulty hardware and am awaiting its return.
So now is where I ask you guys. I've spent a solid hour googling this and nothing related to my problem comes up. So does anyone have any experience with the S4 not being able to flash touchwiz based roms? Or could anyone point me to any leads as to why this would occur that I can investigate further?
Thanks for the help.
-Tryer
EDIT: I'm pretty sure it wasn't MF3 because I could flash certain ROMS fine.
You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?
DeadlySin9 said:
You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?
Click to expand...
Click to collapse
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.
Tryer1234 said:
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.
Click to expand...
Click to collapse
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.
Aou said:
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.
Click to expand...
Click to collapse
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?
Tryer1234 said:
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?
Click to expand...
Click to collapse
when the device reboots after the aroma install, i would pull the battery, replace it and use the 3-button combo to enter custom recovery. then i'd flash the loki-doki zip. thats just me though. i hate aroma.
http://lmgtfy.com/?q=what+is+loki+doki
also: http://forum.xda-developers.com/showthread.php?t=2292157
Hi there.
I have a Samsung Galaxy S4 GT-I9505 and I’m using TWRP Recovery 6.0.4.4.
I tried to flash a nightly-version of CyanogenMod (cm-10.2-20131101-NIGHTLY-jfltexx.zip). I did a Factory Reset before flashing, TWRP said it had been successful.
When I tried to boot my phone, I can see the "SAMSUNG GALAXY S4 GT-I9505" logo, here it got stuck. I can not see the cyanogen boot animation.
Though MD5 hashes and file sizes are ok, I tried another ROM: SuperNexus http://forum.xda-developers.com/showthread.php?t=2407616
Here it was exactly the same. My device gets stuck even before the boot animation.
I was so desperate, that I tried to format my complete internal storage. Flashing the ROMs was successful again, I could boot both ROMs CM and Supernexus then. But after I turned off my device I can't boot any more. Again I can not see the boot animation.
I have already tried it with PhilZ and CWM. I flashed them using my current recovery.
Any advice?
I am sorry for my English, if you need more detailed explanation, please ask. I tried to describe everything as detailed as I can.
Can you get into download mode? You may have to flash a stock ROM to get it to working again. Was the phone previously rooted?
And are you currently on a stock ROM or coming from a custom ROM?
Yeah, I can get into Download mode.
Well, I am not sure what ROM I'm currently using since I wiped everything. Previously I had FoxHound ROM, samsung-based pre-rooted custom ROM.
Have you tried flashing a custom Kernel?
Sounds like what I had when I tried to flash a TW Kernel for a AOSP ROM.
If you can't get into recovery, go into download mode and flash the latest CWM. Got my phone working.
FoxHound ROM installed a custom Kernel, "Ausdim Kernel" I think.
Now I have CWM 6.0.3.2 from here: http://forum.xda-developers.com/showthread.php?t=2279579
Not sure if this is the latest version ... I can't find an Odin-flashable *.tar
Anyway it doesn't work too. This recovery can't even flash CM, it gets stuck at "opening update package ..."
Sorry its a bit late.
http://forum.xda-developers.com/showpost.php?p=46312260&postcount=149
Use them. This may help as a tutorial to follow loosely but that was for non working WiFi.
http://forum.xda-developers.com/showpost.php?p=47076192&postcount=6
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
1. Use TWRP, CWM is outdated.
2. "Nightly" realeases are testing firmwares. CM13 for GT-i9505 is in early releases too. They have lot of bugs still.
3. - Download the latest stable CM firmware: HERE and copy it to your SDCARD external + Gapps (ARM+ android 5.1 + nano).
- Go to DOWNLOAD MODE and flash TWRP. Boot in TWRP - Select Wipe - Advanced Wipe and wipe all (less usb-otg and external memory).
- Flash CM12.1 firmware and GApps then. Reboot and enjoy.
Use TWRP. Google for s4 twrp. On that page you will also have various install instructions. Afterwards you can flash pretty much any custom rom.
Well, tried exactly these steps, I only skipped gapps for now. I installed following version: cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx. However the phone still hangs while booting... I will let it for a while and see if it boots, but I think it's still stuck... The stock Samsung Kitkat flashes properly from Odin and can be booted... Really strange. Is there anything I can do to see what's going on? I only get the Cyanogenmod Bootscreen, but no adb access...
Well, I am getting some errors: unable to mount /efs... This seems to be the problem, no idea why this is happening... I will keep looking around for a fix... I still don't quite understand why a stock KitKat works...
mschmiedel said:
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
Click to expand...
Click to collapse
Try dowloading the rom from a thread here on the forum.
You didn't mention what phone model you got so I assume it is a GT-I9505. You can find the official thread in the I9505 original android development section. The maintainer is AntaresOne.
It is the GT-I9505, I now was able to install a stock Kitkat, and it now is allowing me to update via OTA, (first time I got a message that I had a "changed" phone and OTA was disabled). I will let it install this way and see what happens.
Last time I tried with TWRP I was getting the error "unable to mount /efs", but after flashing an ODIN ROM the phone works, I have LTE Data and can place and receive calls, IMEI is there, so I am now confused about what can be wrong.
When this OTA update works, I will try to reflash TWRP via Odin (and not mess around with heimdall anymore), and see if then I can install CM12...
I downloaded the version from the Cyanogenmod site, the latest stable CM12.1 release, so I guess it should be as good as downloading it from an xda thread...
I don't know. It's worth a try.
If you get errors about efs,be careful.The EFS partition contains the most important stuff like your IMEI.There are some backup/restore tools of EFS, you should check them out.Wipe everything,flash cm,then restore EFS backup.
Hey guys,
I have a little problem with my new OP2.
I unlocked the bootloader and rooted etc.
I installed Paranoid Android and I wanst sure which kernel works on it.
So I tried flashing one for CM13 and one for OOS3, but both of them wouldnt work.
Now Im trying to get back to stock or atleast flash the boot.img from the Paranoid ROM.
I can boot, access the recovery and bootloader. I flashed different boot.imgs (Stock and Paranoid) and recoverys. But none of them helped.
The touchscreen wont react at all. If I boot, if I am in the recovery. It just wont work. Hardware button seems to be fine though.
Any ideas how to fix that?
Try wiping system partition and flash the PA ROM again (and Gapps of course) and it will restore system and kernel back to PA default.
If touch still doesn't work, then you'll probably have to wipe userdata partition as something you installed with the kernels not supporting other than official latest CM13 sources is messing with your system.
You need to flash full stock using fastboot from unbrick guide.
Sent from my ONE A2005 using Tapatalk
google megaunbrick guide oneplus2 and follow that!
didn't got your logic behind flashing custom kernel that too on paranoid android, I can understand that for cm13 as the battery life sucks there but pa easily gives 6+ hrs of sot which any other rom or even a custom kernel can't even come closer to it in my personal experience.
meaning you can try to flash the whole rom through fast boot or use unbrick guide to go full stock.
I wanted to upload a new rom to my phone (pine, 16GB), but it will never boot. Always after rebooting, TWRP will be loaded again. I'm tried multiple ROMs (LineageOS, DotOS, MokeeOS ), but the problem occurs for all rom. TWRP says, flash succed for every one system, but not booting after reboot.
I'm used twrp-3.5.0_9-20210101-pine-arm64 version. Only I can do flash a stock rom using MiFlash, but no custom rom via TWRP.
Mi device is correctly unlocked via Official Unlock Tool app.
Can you tell me why?
Thanks
Maybe try another twrp version or another completely like OrangeFox can't really tell you why i don't have as much knowledge in why or how it works but i have tried a lot on mine so this should be ur first troubleshooting step from my point of view also have you flashed the ROMs with their instructions some say the sequence you should format or wipe ur data etc...
Working for now,
The problem was that I didn't choose to Format data