Related
Hi guys... I have just returned to android after joining the other side. My last android device was an htc hero which was rooted and running a custom rom, but that was a very long time ago and android has moved on so much since then. I recently purchased a motorola atrix which was locked to t-mobile uk, I used an unlocking code to use on the o2 network. I then rooted the device. I have looked through the many many posts of how to unlock my bootloader and usually I wouldnt have any issues but many of the download links are down, so I read another method and the more I read the more I doubt myself.
please dont flame me, if somebody could spare a few moments i'd be very grateful...
my device details are as follows...
Model - MB860
Android Version - 2.3.4
system version - 45.31.2MB860.T-Mobile.en.GB
Baseband version - N_01.100.00R
Build number - 4.5.2A-74_OLE-31.2
Also, any good rom suggestions? I drive for a living so I use co-pilot sat nav alot, I also love taking pics and videos, so would like a rom that has working camera and video recording....
thanks again...
I am not certain with what your issues are with following the method in the sticky at the top of this thread. If some download is not working, seach around for the same file. It is all about getting the unlocked bootloader to flash.
AFAIK, the only way to unlock a moto phone is to flash a moto signed unlocked bootloader.
I do wonder if just burning the fuse would do the trick, but do not know either if it can be done or if it works. But I seriously doubt you want to go there.
Sorry guys.... The sticky somehow got linked to my question.... please ignore the sticky!!! I have no idea how that happened.
Ok, I managed to sort everything out... I'm running Nottach Trix4g custom rom.
But I did notice something whilst running rsd lite, I made sure that I followed the instructions exactly, my phone was detected and started to unlock my bootloader, all files extracted and for some reason on the last section my phone rebooted but the operation had not complete on rsd lite. So I tried again with the same thing happening, the device would reboot with no 'UNLOCKED' on the boot screen. After the second time I was alittle worried so checked the phone was working properly and noticed a decrease in performance. I then checked available memory and it was at 78mb free, even after rebooting with 200mb used!!!
Basically I ended up unlocking the bootloader via command prompt and it worked first time, I've made a back up of my stock rom and then went ahead and installed the nottach Trix4g custom rom, this rom has the ramfix as an option during install.
So right now after checking my running services I have 440mb free with 222mb used, does that seem right?
After I installed the new rom I let it settle for around 30mins before using the device.
It seems ok but what do the more experienced users think, have I messed something up?
yup sounds about right thats a good rom too
Sent from my MB860 using Tapatalk
Really happy with the rom too. If i was to change roms would I have to re-apply the ramfix?
thanks for your help.
hope this helped!!
depends if you have bell atrix AT&T atrix or international. all international users have to flsh the ramfix when needed. i have att atrix so i can flash either flaux123 clesmyns or cm9 kernels well depending on the rom. cm9 uses cm9 or flauxes123 kernel and gingerbread uses gb kernels.
oh ok, I see..... im from the uk so I had to flash ramfix. Does that mean that even if I was to flash a stock rom that I'd still have to flash ramfix, or would it be back to normal? I suppose what im trying to say is, using the method I used to unlock my bootloader have I damaged the ram in anyway?
Whats the best ics custom rom available at the moment?
Thanks again....
No by unlocking the boot loader you didn't mess up anything. You just voided your warranty. Now if you were to put stock rom u don't have to flash ram fix. If it boots up and passed the boot logo then you're good. But if it stays stuck on boot logo for more than 2 minutes then logically u need to apply ram fix. U can flash any ATRIX rom. If it gets stuck then u need ram fix. And best ics rom as from right now will be the one from jokerjax.com.
sent from "ATRIX-BEAST" using voice commands.
thanks guys, I really appreciate your help. All seems to be running surprisingly well with the new rom.
now to try cm9.....
Guys i came up with an idea
to change the kernel
by rewriting the kernel
i know this idea is crazy
but i just came up with this idea because im soo sick of using this stock roms stuck too much unlike the unlocked ones
im having 12W01 w8 mobile no wonder i bricked my phone twice
every one knows that we can modify the codes using rom manager so we just have to copy and paste whats in nAa kernel methods and implementations to stock tweaks
hope this will work
DEVELOPERS please consider
eh? explai better? you wanna unlock the bootloader with kernel for install kernel? ._.
its like this after 11W29+ they have blocked the kernel right
but still with using tools we can modify the running methods and implement new
so as i was trying to say it has to work if we replace the whole nAa Kernel methods and implementations to stock the whole bunch with out removing the kernel files
I dont think you can mod it whitout flashing it again...
Sent from my X8 using xda app-developers app
eh, nice idea bro!
but still, i don't think it could be possible without unlocked bootloader and trying it may brick your phone again as u need to probably reflash it, as said by Lukenda too...
good luck if you wanna try it. :good:
fingers crossed :fingers-crossed:
Do you mean something like this? I don't know if it works on X8 but with this thing we could be able to "install" custom kernels on devices with locked bootloader.
fifo171 said:
Do you mean something like this? I don't know if it works on X8 but with this thing we could be able to "install" custom kernels on devices with locked bootloader.
Click to expand...
Click to collapse
That could work. But i think the op is talking about modifying the kernel the phone is on as opposed to running a kernel on top of what's already there. At least that's how i understood the guide...
Sent from my rooted tomato using xda app
@OP : As long as the bootloader is locked, you can modify all the kernels you want, but it still won't be flashable to our phones.
untill your bootloader locked you cant flash any kernel mod into your device :'(
rohin he means to say to make changes in the stock kernel present in the phone some how and not flash new kernel...
it might work if some developer works on it....like alfsamsung and nobodyatall coming together and do it?
aZuZus method might be some help.. may be cwm flashable kernel? but that would require unlocked bootloader too.
CnC-ROCK said:
rohin he means to say to make changes in the stock kernel present in the phone some how and not flash new kernel...
it might work if some developer works on it....like alfsamsung and nobodyatall coming together and do it?
aZuZus method might be some help.. may be cwm flashable kernel? but that would require unlocked bootloader too.
Click to expand...
Click to collapse
To tamper with even the stock kernel, the bootloader needs to be unlocked. It's like trying to edit a stock rom (2.1 like Matej2010) without root. It's impossible.
Are you sure it won't work on locked BL? Then how is it possible that with kexec method X10 users can run custom kernels with locked BL? AFAIK they use the kexec to unload stock kernel and load custom kernel (for example like doixanhs DT module - it unloads the stock screen driver and loads the modified one. I think that kexec does the same with the whole kernel).
Provided you can load/unload the whole kernel w/o f*cking the system up
RohinZaraki said:
Provided you can load/unload the whole kernel w/o f*cking the system up
Click to expand...
Click to collapse
i suppose that if x10minipro can do it then so can x8
Yeah, maybe it's possible. Isn't here anyone to so that willingly?
Sent from my MANGO using Tapatalk2
Infact idea is working on the Samsung Galaxy S3 whereby Kexec is loading and selecting the boot from the recovery partition
But then we does need figure out a way to enable the system to boot from different partition.
hell of a work to rewrite script
Somebody should ask nAa and dx,they should know the answer
Sent from my X8 using xda app-developers app
@all azuzu's SBoot tool will make use of the kexec module. A kernel with a kexec module does not necessarily need an unlocked bootloader. It will (AFAIK) load up the new kernel for debugging over the existing stock kernel. We won't see such a kernel soon but that soon doesn't necessarily mean never.
Can we run 2 kernel om 2 different roms,like multibooting them? That way would be possible..
Sent from my X8 using Tapatalk 2
Lukenda said:
Can we run 2 kernel om 2 different roms,like multibooting them? That way would be possible..
Sent from my X8 using Tapatalk 2
Click to expand...
Click to collapse
Huh? Really explain what you mean and give an example if you can.
Hi guys,
so I'm currently switching from my Defy to the Razr I.
I already browsed the forum but still have some questions.
As I am used to have all the great CM features on my Defy, I'd like to have as much modification for my Razr I as possible.
But of course I'm well aware that the dev is not that big for the Razr I...
1st of all, I do NOT want to unlock my BL for warranty issues (I mean, who would like to unlock a brand new phone and void the 2year warranty?)
So I'm planning on staying on ICS but I'd like to get as much AOSP / JB features as possible on my phone (rooted with the motofail2go)
I was thinking that instead of flashing the zips in CWM I'd just replace the system apks with a root explorer manually...
So is there any chance, I can implement features from the [KERNEL][ROM][MOD]infiniROM to ICS?
What I'd really like to have:
2G setting, flashplayer, brightness settings, better batter life, and any way that brings back a power bar or whatever it is called to have settings like brightness, wifi AP on/off, GPS on/off;flashlight in the notification bar
As Razr i has unlockable bootloader, there is nobody who had played with second init like with defy (I had defy before razr i too) as there wasn't a reason to.
As you may know, there is official update to JB, which at least for me meant much better battery life than I had on ICS and this gets even better on Omar's ROM.
See this thread, there is link for root tool for locked bootloader but that works on ICS only. With root you should be able at least to change brightness and some other thinghs. For power bar search "power toggle" on the play store.
To be honest I was a little worried to unlock my bootloader too but after couple of days when I was sure the phone works well I took the risk as many other users here. And if you'll lock bootloader again there is possibility that shop where you bought your phone won't even dig if you unlocked it or not and you might be just fine with possible warranty claim.
thanks for the reply, I am however not going to unlock the BL.
So what is possible with ICS besides power toggle?
Can I install the AIO kernel on my ICS?
dagoban said:
thanks for the reply, I am however not going to unlock the BL.
So what is possible with ICS besides power toggle?
Can I install the AIO kernel on my ICS?
Click to expand...
Click to collapse
Sorry, but if you want a new kernel, or the roms here, i recommend you 100% unlock the booloader to avoid bricks, without that, you will have to not prove things without freedom of bricks
Intel device - Razr i Owner
Hit thanks if i help you or you like my style
OK, seems like nobody has tried flashing the kernel with a locked BL...
But what about the systemui.apk? Can I just replace that with the one from the mod? That should work, right?
Why should one flash a wrong Kernel or SystemUI?
Deal with ICS, stay on JB stock or try yourself if you want to see bootloops. Good luck...
Well I thought before I get bootloops I would just ask here if someone tried that out before?
Nothing wrong with that I think...
And it could be possible to flash a different kernel than the rom.
On my Defy I have a froyo Kernel with GB, and froyo Kernel with JB...
dagoban said:
And it could be possible to flash a different kernel than the rom.
On my Defy I have a froyo Kernel with GB, and froyo Kernel with JB...
Click to expand...
Click to collapse
Yes, that's right but all kernels used in defy are signed by motorola otherwise it won't be possible to use them since bootloader is not unlockable. Plus due to x86 architecture it'd be complicated try to port jb or newer (in future) to work on ics as everything would have to be done from sctrach - no point do that.
I just hope we won't see new topic "help, I bricked my phone" created by you...
dara85 said:
I just hope we won't see new topic "help, I bricked my phone" created by you...
Click to expand...
Click to collapse
lol, me neither
So, no different kernel, but what about the systemui.apk? I mean, I can copy any modded google app to my phone, so does that mean I can also use the modded systemui?
Man, sorry for sounding rude (truth is sometimes uncomfortable), but as SystemUI is dependent on the framework (of either ICS or JB), there's no chance to switch between them.
You don't want to unlock? So there are two options: Stay at ICS rooted or JB stock unrooted.
The more you ask, the less you get another or better truth.
If you don't believe, try it. Why not? The chance for curing a boot loop with ADB enabled in developer options is 99% (if you are fit with command line) - otherwise you flash ICS stock with RSDlite again, then you are 100% safe.
But DO NOT flash a JB kernel over ICS!
shaftenberg said:
Man, sorry for sounding rude (truth is sometimes uncomfortable), but as SystemUI is dependent on the framework (of either ICS or JB), there's no chance to switch between them.
Click to expand...
Click to collapse
OK, didn't know that the systemUI is part of the framework, I thought its a regular apk like any other apk, like the clock or regular gapps...
Hi,
Some of you may recognise my name from around the forums, especially if you have had an Xperia device before. I started my first android developments on the Xperia Play and then continued onto the Xperia U. I then lost mass interest in development due to joining college and being overloaded with work due to a computing course. I was no longer able to contribute to any developments.
Now, I am in the second year of college and have dropped a subject I am finding myself with more free time so I have decided to start developing again, only this time I have an Xperia SP.
There's only one catch, the device I have is network locked to O2 and therefore I cannot unlock my boot loader, so most if not all of my work will be for those with a locked bootloader. I am mostly interested in creating custom ROMs based on stock and also creating my own applications and embedding them into the stock ROM.
And the flashy bar at the bottom, yeah I have ideas for that.
Developments for Xperia SP:
illumination app
~Keiran
Sent from my C5303 using Tapatalk
Thank you!
Sent from my C5303 using XDA Premium 4 mobile app
Thank you!
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
MrZender said:
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
Click to expand...
Click to collapse
I can't, it just means that I will only be able to developed for locked bootloader which is no problem really. All it means is that I cannot change the kernel image, using scripts I can mess about with the ramdisk though and may be able to boot CM on a locked boot loader if the stock kernel allows it.
Sent from my C5303 using Tapatalk
Glad to see you back in the game mate ! Too bad that you can't unlock your bootloader. Although I know that would not be a problem for you.
Sent from my C5303 using Tapatalk
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
adfad666 said:
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
Click to expand...
Click to collapse
I'm sure it is very possible, as there is a way that could work really, I could probably set it up as a dual boot. You would need the AOSP ramdisk in tar format somewhere on your phone and at boot time if you wish to boot AOSP then it would delete everything at / and extract that ramdisk to / and then continue boot process with that ramdisk.. as long as stock kernel is compatible.
Sent from my C5303 using Tapatalk
Welcome in SP section
Happy to see more real dev here
Well, maybe you could port kexec to our locked SP's? The main part of the module and binary is done, there is only one thing left - implementing proper hardboot and finally porting to our phones. I think some Xperia SP devs might help you. There's a thread in Z1 forums where delewer tries to get last parts of the job done. If you decide to start working on it, I want to be a alpha or beta tester
http://forum.xda-developers.com/showthread.php?t=2495152
Welcome mate, glad you are here can't wait to see your work I also had an xperia play and I'm pretty sure I had a few of your roms and mods installed at some point.
Sent from my C5303 using XDA Premium HD app
I have a few projects in mind at the moment:
1. Getting the 4.3 leak to boot on locked bootloader
2. When 4.3 is released get AOSP 4.3 to run also on locked boot loader - I will be working with @adfad666 on this - most priority
3. Maybe a stock based custom ROM - least priority.
Sent from my C5303 using Tapatalk
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
MrSteve555 said:
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
Click to expand...
Click to collapse
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
I think I'll try to boot 4.3 today, with the method described in this thread: http://forum.xda-developers.com/showthread.php?t=2593806
I'll post my results later.
KeiranFTW said:
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
adfad666 said:
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
Click to expand...
Click to collapse
then /system/bin/charger
Sent from my C5303 using Tapatalk
Well, pre_hw_config.sh doesn't exist even in stock 4.1.2. I think we should try with chargemon, not charger(because it's executed earlier). I tried booting DooMLord's DoomKernel ramdisk on stock kernel. Absolutely no luck. I don't even know what's wrong - after loading ramdisk, kernel panic occurs. Maybe someone more clever will figure it out.:silly:
I think I'm nearly there at hijacking the boot process to inject new ramdisk, I just have a little test that I will have to do later as I need to go out now.
What I'm going to do is use the same ramdisk as that's in the kernel but inject it again after removing anything, this way I don't need to change my ROM and I know that I can inject a new ramdisk. I'll upload my work to github later too so people can contribute
~Keiran
Sent from my C5303 using Tapatalk
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
KeiranFTW said:
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
Click to expand...
Click to collapse
I tried your method, but it has one bug - it doesn't symlink /data/media to /storage/sdcard0, so the data from internal memory isn't accesible through that path. Still amazing work, but I suggest you to change the format of ramdisk read by the script to .cpio, because it's easier to get from kernels. :good:
I'm wanting to update my gf's M to 4.4.2 and am wondering the easiest way to go about it. It's currently rooted and running a custom ROM, but she doesn't care about any of that. Could I just download the sbf and used RSD Lite to flash it? Or would I need to flash an earlier build and then take the OTA? I'm not worried about keeping root or an unlocked bootloader, but would there be any way to keep her Candy Crush data (that's the only thing on the phone that means anything to her)?
Yea just grab 4.4.2 KitKat and flash it with rsd. . then flash SuperSU or use towelroot to get root back
Sent from my XT907 using XDA Premium 4 mobile app
Awesome! Any chance at saving her game data? I was going to try Helium, but I remember that Moto broke it.
stick1300 said:
Awesome! Any chance at saving her game data? I was going to try Helium, but I remember that Moto broke it.
Click to expand...
Click to collapse
Titanium Backup attempts to recover/restore app data. It works on about 75% of apps I try, but some lose their data.
ezknives said:
Yea just grab 4.4.2 Kitkat and flash it with rsd. then flash towel root to get root back
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will this work if I already have an unlocked bootloader (from the exploit in Jelly Bean)?
thad137 said:
Will this work if I already have an unlocked bootloader (from the exploit in Jelly Bean)?
Click to expand...
Click to collapse
Sure will. You will lose root but not the unlocked bootloader.
Sent from my DROID RAZR M using Tapatalk
You can edit the .xml file so that it doesn't wipe userdata, and that should let her phone keep all its settings, apps, data, etc. It'd definitely be smart to also back that stuff up with TB as well, though. If you do edit the .xml that RSD Lite uses to flash, make sure to use something like Notepad++, and not just Windows Notepad. I think you also have to edit out the getvar line if you're flashing over a non-stock ROM. If you've done the NV edit with RadioComm, supposedly you can also delete the modemst1 and modemst2 lines, and you shouldn't have to redo the GSM hack.
Is there a way a person could flash just the bootloader in RSD instead of wiping my custom rom?
thad137 said:
Is there a way a person could flash just the bootloader in RSD instead of wiping my custom rom?
Click to expand...
Click to collapse
I've seen some reports that you can do the boot.img file, but it softbricks most devices. I'd suggest just backing up your stuff and flashing stock and then go back to your ROM. Or just leave it, unless its CM11.
Sent from my DROID RAZR M using Tapatalk
thad137 said:
Is there a way a person could flash just the bootloader in RSD instead of wiping my custom rom?
Click to expand...
Click to collapse
I believe the answer would be no... I think your asking if you could go from the jb bootloader to the kk one or vise versa via rsd by only flashing the boot loader and keep your current ROM... if that's the case no as the Roms (not sure how it all works) have become dependent on which boot loader you have... So the ROM your on probably will not function if you could flash just the boot loader... Like as I'm on kk I can't use PAC man as it needs the jb boot loader or whatever... And if your on jb (last I checked) you can't use the newer builds of kitstalk... So your best bet would be stay as you are or flash the whole thing IMHO...but I may be wrong
Edit... That's the second time we have started a reply at the same time @xKroniK13x you get it out faster tho....
ezknives said:
I believe the answer would be no... I think your asking if you could go from the jb bootloader to the kk one or vise versa via rsd by only flashing the boot loader and keep your current ROM... if that's the case no as the Roms (not sure how it all works) have become dependent on which boot loader you have... So the ROM your on probably will not function if you could flash just the boot loader... Like as I'm on kk I can't use PAC man as it needs the jb boot loader or whatever... And if your on jb (last I checked) you can't use the newer builds of kitstalk... So your best bet would be stay as you are or flash the whole thing IMHO...but I may be wrong
Edit... That's the second time we have started a reply at the same time @xKroniK13x you get it out faster tho....
Click to expand...
Click to collapse
At least we post similar responses! ?
Sent from my DROID RAZR M using Tapatalk
xKroniK13x said:
I've seen some reports that you can do the boot.img file, but it softbricks most devices. I'd suggest just backing up your stuff and flashing stock and then go back to your ROM. Or just leave it, unless its CM11.
Sent from my DROID RAZR M using Tapatalk
Click to expand...
Click to collapse
ezknives said:
I believe the answer would be no... I think your asking if you could go from the jb bootloader to the kk one or vise versa via rsd by only flashing the boot loader and keep your current ROM... if that's the case no as the Roms (not sure how it all works) have become dependent on which boot loader you have... So the ROM your on probably will not function if you could flash just the boot loader... Like as I'm on kk I can't use PAC man as it needs the jb boot loader or whatever... And if your on jb (last I checked) you can't use the newer builds of kitstalk... So your best bet would be stay as you are or flash the whole thing IMHO...but I may be wrong
Edit... That's the second time we have started a reply at the same time @xKroniK13x you get it out faster tho....
Click to expand...
Click to collapse
Thanks I'll just go ahead and go through the entire process of flashing everything for the new version of Paranoid Android.
UPDATE: I manually flashed everything but "system" and "recovery" and then flashed dhacker's recovery from here ( loki.rombitch . com/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img ) then I flashed the Paranoid Android update and everything is working.
thad137 said:
Thanks I'll just go ahead and go through the entire process of flashing everything for the new version of Paranoid Android.
Click to expand...
Click to collapse
Paranoid has a 3.4 kernel ROM? How did I miss that?!
xKroniK13x said:
Paranoid has a 3.4 kernel ROM? How did I miss that?!
Click to expand...
Click to collapse
heres a link..http://www.drdevs.com/devs/?dir=cj360/Aospa
xKroniK13x said:
Paranoid has a 3.4 kernel ROM? How did I miss that?!
Click to expand...
Click to collapse
I'm still new, so I can't link it, but... http://forum.xda-developers.com/showthread.php?t=2696606
(second post) (I think he meant 07-02-2014)
5318008 said:
You can edit the .xml file so that it doesn't wipe userdata, and that should let her phone keep all its settings, apps, data, etc. It'd definitely be smart to also back that stuff up with TB as well, though. If you do edit the .xml that RSD Lite uses to flash, make sure to use something like Notepad++, and not just Windows Notepad. I think you also have to edit out the getvar line if you're flashing over a non-stock ROM. If you've done the NV edit with RadioComm, supposedly you can also delete the modemst1 and modemst2 lines, and you shouldn't have to redo the GSM hack.
Click to expand...
Click to collapse
Yeah, I read about this in another thread and it worked fine. She's now on stock 4.42 and has her treasured Candy Crush data.
Now, if I could just get her wifi working again. I've done so much reading about the issue lying in the /persist (and/or /prima) folder, but, even after trying multiple "clean" copies of it and fixing permissions and everything else people have suggested, I can't get it working again.
I wish I could help there but I don't have any useful info to offer. I've heard a number of complaints about the WiFi on KK on the Razr M, so I don't think it's just you. I heard they're testing another KK update, maybe it'll fix it when it rolls out. I did notice that the time I tried flashing the KK radio onto my stock JB, it totally broke my WiFi and I had to flash back.
5318008 said:
I wish I could help there but I don't have any useful info to offer. I've heard a number of complaints about the WiFi on KK on the Razr M, so I don't think it's just you. I heard they're testing another KK update, maybe it'll fix it when it rolls out. I did notice that the time I tried flashing the KK radio onto my stock JB, it totally broke my WiFi and I had to flash back.
Click to expand...
Click to collapse
It stopped working when she was still on JB. I had hoped updating would fix it, but no such luck. The only way I managed to get it working in the past was by reflashing the ROM that was on the phone, but it stopped working again after a few weeks.