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.
Related
I just want to let everyone know that it is possible to go back to ICS after updating to 4.1.2(9.16.6) I was rooted on 4.1.1 today, used ota root keeper to temp unroot and update to 4.1.2 and restore root. I just used Matts RazrHD utility 1.10 and went back to ICS 4.0.4 with no problems what so ever...
Im not sure why its stated that once you update to the newest release that you cannot go back, but its possible. So for everyone that wants to try out 4.1.2 and didnt want to be stuck, you can downgrade.
Hope this helps.
Also for everyone willing to try to downgrade please post results and type of phone you have, also the way you downgraded...
Device: Razr HD XT926 US Verizon non dev ed.
Original firmware 4.0.4(0.6.25)
Used RazrHD Utility 1.10 to downgrade
UPDATE: 3/21
I tried to downgrade again so I can post screen shots for everyone, and it did not work this time!!! Something must have changed/sync'd with my phone since the last time I downgraded that did not sync the first time. This has been a strange experience, but I would not have posted if I really did not have success the first time! It now gives errors, and I have tried everything I could imagine. My phone is not bricked and I am still rooted and have SS.
Preserving the option to downgrade to ICS is certainly important to me. Please, what phone do you have and from what country is your carrier (and thus, presumably, your version of stock ICS)?
lesdense said:
Preserving the option to downgrade to ICS is certainly important to me. Please, what phone do you have and from what country is your carrier (and thus, presumably, your version of stock ICS)?
Click to expand...
Click to collapse
XT926 Verizon US non dev edition, ICS 4.0.4 (0.6.25)
I will add it to the OP
OK ... I've got to know. Why did you leave 9.1.2 immediately after upgrading to it? The knowledge that downgrading back to 4.0.4 from 4.1.2 is certainly valuable, but knowing what prompted you to upgrade and then so quickly downgrade would be valuable to know as well. Did the upgrade go smoothly? Did the upgrade not function as expected?
lesdense said:
OK ... I've got to know. Why did you leave 9.1.2 immediately after upgrading to it? The knowledge that downgrading back to 4.0.4 from 4.1.2 is certainly valuable, but knowing what prompted you to upgrade and then so quickly downgrade would be valuable to know as well. Did the upgrade go smoothly? Did the upgrade not function as expected?
Click to expand...
Click to collapse
No it was fine... I had some weird problems with data switching, from wifi to mobile... Sometimes it wouldn't switch back to mobile after turning off wifi but that was only a couple of times. I really just wanted to see if it was possible to downgrade and was willing to do it even though I could of been stuck without a phone. I also like to start fresh by downgrading and wiping/formatting my sd card every month or so. Im back on 4.1.1 now and will probably go to 4.1.2 soon on my stock slot either way.
What I did was Remote into a DROID RAZR HD owner's computer and flash the ICS boot.img file through fastboot. It failed pre-flash validation so I flashed to new boot.img back on there and considered it a case closed.
If it works to go back by using the Utility, thats great news. However I am not going to remove the warning until I get more than just one confirmation on it.
great news thx
Sent from my DROID RAZR HD using xda app-developers app
I have JB 4.1.2 now and using Matt's tool, I can't seem to get it to downgrade. It will run through the process, then it will just boot up into 4.1.2 again. It gets a couple failed things along the way.
Because I'm still weighing whether to upgrade to 4.1.2 can you tell me -- did you get 4.1.2 OTA or did you flash a file? If you did a "manual" upgrade, how is the experience? Problems? Anything not working, or not working right?
Ota, everything went fine during the upgrade. Just make sure if you are rooted to activate stock slot and wipe all other slots. I also restored a backup of stock jb 4.1.1 I made a week ago with all apps updated and working. Then just booted up and temp unrooted with ota root keeper and accepted the ota. Restored root after it booted. Only thing that was different from other updates is that safe strap did not work afterwards so I had to uninstall and reinstall.
I don't see much improvement, but I just got back to 4.1.2 late last night after downgrading so that's not much time to tell if the improvements are there. I have not tried HDMI out yet,but will later today.
If anyone else tries to downgrade to stock 4.0.4 ICS from this latest update 4.1.2, please post what type of phone you have and if it worked for you. Any problems...???
Sent from my XT926 using Tapatalk 2
an21281 said:
Ota, everything went fine during the upgrade. Just make sure if you are rooted to activate stock slot and wipe all other slots. I also restored a backup of stock jb 4.1.1 I made a week ago with all apps updated and working. Then just booted up and temp unrooted with ota root keeper and accepted the ota. Restored root after it booted. Only thing that was different from other updates is that safe strap did not work afterwards so I had to uninstall and reinstall.
I don't see much improvement, but I just got back to 4.1.2 late last night after downgrading so that's not much time to tell if the improvements are there. I have not tried HDMI out yet,but will later today.
If anyone else tries to downgrade to stock 4.0.4 ICS from this latest update 4.1.2, please post what type of phone you have and if it worked for you. Any problems...???
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
You don't have to wipe your rom slots.just go back to stock slot take the ota and then reinstall safestrap recovery (not the program).your roms will still be there and functional.
Sent from my DROID RAZR HD using Tapatalk 2
Don't know how I've missed all this "stock slot, rom slots" business. I've rooted Android phones and tablets, installed custom ROMs, I've still a noob but learning. Does "slots" refer to all that sdcard0, sdcard1, usbdisk_1.0 business in /storage? I don't think I'd seen that on any of my devices until I got my Maxx HD with 4.1.1. Or are slots part of SafeStrap (I have that too but only because it was on my phone when I bought it on eBay)? Upgrading to 4.1.2 sounds like it goes smoothly if you do it right and is a pain if you don't. Sure would appreciate a little guidance that's specific to this set of tasks.
Well I feel like an idiot. I got the leaked 4.1.2 and now it's literally impossible to downgrade. I hadn't installed any bootloaders/roots/ or anything before doing this, so now that my phone is 4.1.2, it's basically stuck there.
I've tried hours and hours of everything. If anyone has any idea on how to bypass this I'd be grateful.
Mystique5022 said:
Well I feel like an idiot. I got the leaked 4.1.2 and now it's literally impossible to downgrade. I hadn't installed any bootloaders/roots/ or anything before doing this, so now that my phone is 4.1.2, it's basically stuck there.
I've tried hours and hours of everything. If anyone has any idea on how to bypass this I'd be grateful.
Click to expand...
Click to collapse
Not sure why it wont work for you, but Im going to downgrade again and post up screen shots and a vid. also. Just waiting for my phone to charge.
only ocigrarn
an21281 said:
Not sure why it wont work for you, but Im going to downgrade again and post up screen shots and a vid. also. Just waiting for my phone to charge.
Click to expand...
Click to collapse
Did you do this procedure from stock? I tried from 100% stock. No unlocked bootloader, no root, nothing. I'm also using a Verizon Phone.
an21281 said:
I just want to let everyone know that it is possible to go back to ICS after updating to 4.1.2(9.16.6) I was rooted on 4.1.1 today, used ota root keeper to temp unroot and update to 4.1.2 and restore root. I just used Matts RazrHD utility 1.10 and went back to ICS 4.0.4 with no problems what so ever...
Im not sure why its stated that once you update to the newest release that you cannot go back, but its possible. So for everyone that wants to try out 4.1.2 and didnt want to be stuck, you can downgrade.
Hope this helps.
Also for everyone willing to try to downgrade please post results and type of phone you have, also the way you downgraded...
Device: Razr HD XT926 US Verizon non dev ed.
Original firmware 4.0.4(0.6.25)
Used RazrHD Utility 1.10 to downgrade
Click to expand...
Click to collapse
No you cant.
thewahlrus said:
No you cant.
Click to expand...
Click to collapse
I downgraded successfully yesterday, so I reported my experience... I have no reason to lie, otherwise I would not have posted this in the first place!
I had some problems with my comp. and the usb/moto drivers on win7 today so I was trying to fix that before I could try again. I attempted to downgrade/restore to ICS again and this time it did not work! I cant see how it worked for me yesterday and today it wont? I was so happy when it worked, but something must have changed within the last day which is odd. I always upgrade and root the same way, and I have tried everything today to get it to downgrade with no luck. My phone still works so it is not bricked, and I apologize to everyone, like I said it did downgrade yesterday with the RazrHD utility 1.10 and there were no errors what so ever. Now after it asks you to hit any key once the phone comes back on in FB errors come right up. Some things seem to flash though, which is strange and basically it does a factory reset on the 4.1.2 . SS is still installed, its still rooted, and works fine. I can even restore back up of 4.1.1 stock jb(which I made last night after I downgraded to ICS and was upgrading again) on stock slot after wiping data/cache/dalvic and system and boot up to show 4.1.1 and then either try to downgrade, which fails, or take the ota and/or flash 4.1.2 manually but it fails also. Then I just reflash a back up of 4.1.2 and its fine IDK... I also flashed Vit 1.9.3 on stock slot fine, boots etc. but still wont let me downgrade. Then I tried uninstalling all updated apps on 4.1.2 and clearing data on all apps, still nothing.
So for some reason it let me successfully downgrade yesterday, but not anymore. So like many people have said do not try until there's a safe way, unless you are willing to risk bricking.
I am downloading the 4.1.2 fastboot files now.
mattlgroff said:
I am downloading the 4.1.2 fastboot files now.
Click to expand...
Click to collapse
You're amazing.are you a moto insider lol
Sent from my DROID RAZR HD using Tapatalk 2
koftheworld said:
You're amazing.are you a moto insider lol
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
I have friends in the Firmware Team
I honestly don't know where to start, I bought the Samsung galaxy s4 i337m from virgin mobile, and use it with my Bell carrier. I was browsing the internet when I come to a video that states that you can flash i9505 roms on my i337/i337m phone! So silly of me to try that, it actually worked. When I was tired of that ROM, I go on this forum thread and look for another ROM, a ROM that is i337m cooked, and it soft bricked my phone, 3 times for 3 different i337m ROMS, at this point I have absolutely no clue what is going on with my phone, is the bootloader unlocked? WTF IS LOKI?? WHY does a i9505 ROM work on my phone, and a i337m cooked ROM does not, I just need some answers!! I have been flashing my phone with ROMs since my s1 and now the s4 comes along and completely wipes any knowledge I had before I got the phone, if anyone can help me on which ROMS I can and/or can't flash, that would be great, sorry for english not my first language!
Read and do some research. Just because you flashed a number of other phones doesn't mean you know how to flash this one. Every phone is different. It would also help to know what roms you flashed that didn't work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
TheAxman said:
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
Click to expand...
Click to collapse
I still don't understand, I have the north american version of the i337m from Canada....
Dragosmp said:
I still don't understand, I have the north american version of the i337m from Canada....
Click to expand...
Click to collapse
What roms did you try to flash? Where did you get them? The boot loader is not locked and they should flash. Did you check the md5sum? They could be bad downloads.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Loki is needed for phones purchased through at&t. The Canadian version is the same phone, but without a locked boot loader, so the Loki hack is not needed.
What I have found is that some of the custom recoveries don't wipe out the phone properly. Try using Odin and go back to stock, wipe, then restart fresh
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Matridom said:
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'd do the full wipe before flashing. If you wipe after DON'T wipe system or you'll be in trouble.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Actually, I totally found that the Loki fix was needed for my Canadian i337m device (Bell). Many ROMs wouldn't work without it; they'd just get stuck in the boot logo (including SlimRom and CyanogenMod).
Just flash the ROM, then flash the Loki-Fix and you should be good to go.
If you're seriously stuck and you can't get back into your custom recovery, let me know and I'll help you out.
Now I am confused. Why would the I337m need a loki anything?
It is not needed. I surprised it even flashed.
TheAxman said:
Now I am confused. Why would the I337m need a loki anything?
Click to expand...
Click to collapse
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
Do you know what your stock firmware was before you started flashing custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
jd1639 said:
Do you know what your stock firmware was before you started flashing custom roms?
Click to expand...
Click to collapse
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
TheAxman said:
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
Click to expand...
Click to collapse
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Te3k said:
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Click to expand...
Click to collapse
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
Which custom recovery are you using to flash with and how did you get it on your phone?
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
This is just not true. No way. Friggin way weird.
scott14719 said:
Which custom recovery are you using to flash with and how did you get it on your phone?
Click to expand...
Click to collapse
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
And this procedure worked for you? You said you had to loki, where did that come in?
TheAxman said:
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
And this procedure worked for you? You said you had to loki, where did that come in?
Click to expand...
Click to collapse
Phone identified as i337m from settings menu prior to any flashing. Model number under battery matches: Model: SGH-I337M / IC: 649E-I337M.
Using Loki came in where I found that flashing ROMs wasn't working. I had already rooted and tried to unlock the phone through the debug menu. Unlocking didn't work, but rooting did and I could load custom recoveries without problem. I thought that I should try flashing other ROMs to see if I could unlock the device through their debug menus, but no luck. The first ROM I tried to flash was a SlimRom nightly. That one appeared to flash properly (recovery said "success"), but upon reboot I got stuck in a boot loop. I then went back to recovery and messed around trying to flash other ROMs and ran into the same issue persistently. I eventually panicked and Odined back to stock ROM and kernel (numbers previously mentioned). Everything was fine after I figured out how to make Odin work. (I even learned how to make signed-MD5 tarballs with Cygwin to try to make flashing recoveries and roots simpler by using Odin.) After wondering why I couldn't flash any custom ROMs, I dug around a bit and found out that some ROMs' first-posts mentioned that certain fixes had to be applied—some of which were labelled ROM-specific (e.g. GOLDENEYE-i337m-FiX-XXUBMF8) and others that just said that they required a Loki fix, and sometimes provided a link to download it. At the time I didn't know what Loki was, and I wasn't understanding why certain ROMs would come pre-"Lokified" (brain was full after hacking around for >6h). So in the moment it made no sense not to try flashing that to see if it would help. Lo and behold, it worked! I started flashing Loki after every ROM install from then on out. Previously not-working ROMs that I had already tried suddenly worked just fine (I didn't redownload them; I kept the same zip files and just started flashing the Loki Fix after each of them to make them work).
It's still the case that when I want to flash a new ROM, I wipe everything from recovery and flash the ROM. If it doesn't boot, I flash the Loki Fix and then it does boot properly.
Realizing I can't unlock my bootloader via motopocalypse because its latest OTA and I can't GSM unlock it for use on US carriers. Am I stuck on stock with Verizon?
xlxcrossing said:
Realizing I can't unlock my bootloader via motopocalypse because its latest OTA and I can't GSM unlock it for use on US carriers. Am I stuck on stock with Verizon?
Click to expand...
Click to collapse
You can GSM unlock regardless of OTA version. There are a few stock-based ROMs out there for Safestrap once you root.
Sent from my XT907 using Tapatalk 4
OK I didn't have any luck with the radiocomm app and editing the nv item. I have root currently but that's it. I've never flashed a ROM without an unlocked bootloader so can you direct as to how this works as well as describing "safestrap".
xlxcrossing said:
OK I didn't have any luck with the radiocomm app and editing the nv item. I have root currently but that's it. I've never flashed a ROM without an unlocked bootloader so can you direct as to how this works as well as describing "safestrap".
Click to expand...
Click to collapse
http://blog.hash-of-codes.com/how-to-safestrap/
Thanks for the info. One question. Since virtual ROM slots use storage as would the stock system am I able to create a virtual ROM, install a custom ROM and delete the stock system?
I've used safe strap on the og RAZR and the d4... it does use the internal SD storage space... and I do not believe you can delete the stock slot nor flash anything on the stock slot... tho it may differ on this device...
Sent from my XT907 using xda app-developers app
xlxcrossing said:
Thanks for the info. One question. Since virtual ROM slots use storage as would the stock system am I able to create a virtual ROM, install a custom ROM and delete the stock system?
Click to expand...
Click to collapse
I wouldn't do that because the ROM slots depend on the stock boot.img to run. However, there is a restore procedure that should work. You can set up a slot, flash the ROM, set it up, and then back it up. Once you have it backed it up, you can restore (not flash) over your stock slot. Then you can delete the custom slot. I've never used this procedure, but I have seen quite a few people do this with success.
I see you're saying you can end up using your stock slot through this method. Basically what I want to know is if I flash a ROM on a virtual slot does my old stock ROM just sit on my sys partition without being used?
xlxcrossing said:
I see you're saying you can end up using your stock slot through this method. Basically what I want to know is if I flash a ROM on a virtual slot does my old stock ROM just sit on my sys partition without being used?
Click to expand...
Click to collapse
Yeah, supposedly you can use your stock slot. I'll post the link to the post on DroidRzr.com where it's discussed. Don't quote me on this, but I think it does sit there unused. The other slots only use its boot image. I'm pretty positive it doesn't do anything else when you boot into the safe side.
http://www.droidrzr.com/index.php/topic/11600-installing-custom-rom-to-stock-using-ss-312/
That app didn't work for me at all. Each time I installed to a ROM slot it would boot to a black screen, couldn't ever get a ROM to load. A bunch of people had the same issue. Tried reinstalling the slot multiple times before giving up. This phone has given me hell since I got it. Motorola phones are really locked down.
xlxcrossing said:
That app didn't work for me at all. Each time I installed to a ROM slot it would boot to a black screen, couldn't ever get a ROM to load. A bunch of people had the same issue. Tried reinstalling the slot multiple times before giving up. This phone has given me hell since I got it. Motorola phones are really locked down.
Click to expand...
Click to collapse
What ROMs were you trying? There are very few SS compitble ROMs out there. The app can still work for you, as far as making backups,etc.
I tried slimbean. I didn't know there was a requisite for what ROM you could flash. I'm selling the phone I'm not terribly concerned any more.
xlxcrossing said:
I tried slimbean. I didn't know there was a requisite for what ROM you could flash. I'm selling the phone I'm not terribly concerned any more.
Click to expand...
Click to collapse
Yeah, with SS you can only flash SS compatible ROMs. Slim Bean is not SS compatible. Either way, good luck with the sale.
RikRong said:
I wouldn't do that because the ROM slots depend on the stock boot.img to run. However, there is a restore procedure that should work. You can set up a slot, flash the ROM, set it up, and then back it up. Once you have it backed it up, you can restore (not flash) over your stock slot. Then you can delete the custom slot. I've never used this procedure, but I have seen quite a few people do this with success.
Click to expand...
Click to collapse
I asked about this before and couldn't get confirmation that this could be done. Suppose someone on droidrzr.com might know for sure? I want to do just as you say with a debloated stock "plus goodies" ROM and then restore over the stock slot.
HemRoyd said:
I asked about this before and couldn't get confirmation that this could be done. Suppose someone on droidrzr.com might know for sure? I want to do just as you say with a debloated stock "plus goodies" ROM and then restore over the stock slot.
Click to expand...
Click to collapse
The person that did the write up on DroidRzr did it and know other people have done it. I never did it but it makes sense that it should work. Just have utility or XML ready if something goes bad.
With a rooted, but locked bootloader, I will still be able to flash a SS rom that allows me to tether?
At this point, that and debloating are my main reasons for rooting.
I'm looking to upgrade from a Thunderbolt to a Razr M. I want to make sure I'm not trading one set of problems for a new set.
FirePsych said:
With a rooted, but locked bootloader, I will still be able to flash a SS rom that allows me to tether?
At this point, that and debloating are my main reasons for rooting.
I'm looking to upgrade from a Thunderbolt to a Razr M. I want to make sure I'm not trading one set of problems for a new set.
Click to expand...
Click to collapse
Yep. You can tether on stock actually... If you're on a share everything, you get it out of the box, otherwise you need to do a hack using sqlite editor or something
Sent from my Nexus 7 using Tapatalk 4
So which ROMs are safestrap compatabile with the locked bootloader? I am trying to help a friend with his phone unfortunately he took the ota update and his bootloader will stay locked for the moment. That said I rooted and installed safestrap so I'm looking to install a compatible ROM and get this phone on straight talk with a ST SIM card. Any suggestions?
Sent from my XT875 using XDA Premium 4 mobile app
Guys, my phone just told me there's another upgrade for the lg g2 D803 variant....Anybody seen this yet?
I'm wondering what the upgrade is, seeing it's 1.5 gb.
It's gonna take me to D803B20G. Not sure if the current rooting and autorec recovery method will work on this new firmware, sceptical about installing it......
rodpgfx said:
Guys, my phone just told me there's another upgrade for the lg g2 D803 variant....Anybody seen this yet?
I'm wondering what the upgrade is, seeing it's 1.5 gb.
It's gonna take me to D803B20G. Not sure if the current rooting and autorec recovery method will work on this new firmware, sceptical about installing it......
Click to expand...
Click to collapse
1. wrong place to post this.
2. general rule of thumb - if you like having root and recovery, NEVER take an OTA from the manufacturer EVER, until it's confirmed that it doens't block root / recovery /bootloader exploits (like the 4.4 ot'as blocked loki)
jakew02 said:
1. wrong place to post this.
jakew02 said:
Sorry, I wasn't sure where to put as there is no folder for 803 variant.....
Click to expand...
Click to collapse
Click to expand...
Click to collapse
jakew02 said:
1. wrong place to post this.
Click to expand...
Click to collapse
Sorry, I never seen a folder for the D803 variant so I wasn't sure where to put this.... Should it have gone in Q&A?
rodpgfx said:
Sorry, I never seen a folder for the D803 variant so I wasn't sure where to put this.... Should it have gone in Q&A?
Click to expand...
Click to collapse
Q&A if you're asking a question about it, General if you wanted to let people know about it..
yes probably in q&a or general maybe, like stated above please dont install on your phone if youre rooted with a non stock recovery otherwise you will mess up your phone big time! really not sure if its possible but if you can, switch off firmware updates as they are not compatible with the custom recoveries and whichever rom you are using will update soon enough anyway if your on stock rom the same applies if you have a custom recovery
martindar said:
yes probably in q&a or general maybe, like stated above please dont install on your phone if youre rooted with a non stock recovery otherwise you will mess up your phone big time! really not sure if its possible but if you can, switch off firmware updates as they are not compatible with the custom recoveries and whichever rom you are using will update soon enough anyway if your on stock rom the same applies if you have a custom recovery
Click to expand...
Click to collapse
I have stock Rom rooted and twrp recovery that's all.
Avoid the update.
However it has the knock knock code addon. Or, as far as I've heard, that's the only new update LG had planned for the LG G2.
Do not install it. If you REALLY want to try it, make a backup, store it on your PC, OTA. If you lose root, you can revert to stock, get a recovery, put your backup back on your phone and restore.....but that's honestly a lot of work just to possibly get the knock knock code. (I know turning on is knock on, but for the "code" you knock more than once minimum, so I call it knock knock).
You can also force supersu to keep root, but last time I tried that for an OTA I got stuck in a bootloop.
TL;DR: Might be knock on/knock knock code. Not sure what else. You can backup and try to OTA, but no one can be certain what will happen. Expect to lose root. You can force SuperSu to keep root, but you may bootloop.
I'd just wait for more info.
rodpgfx said:
I have stock Rom rooted and twrp recovery that's all.
Click to expand...
Click to collapse
twrp recovery is a custom recovery, so never update.
I'm pretty sure there is an app in /system that you can freeze to stop push updates. Sadly, that is the only info I have. It may have been carrier specific and I haven't been on stock since the first week I had the phone. Haha.
Guys I already know all what you just said......I've done this loads of times. Just wondering if I can uninstall custom recovery without re-installing stock firmware?
I know I can take my chance and try the OTA but not without recovery gone first.
It's a lot of work to just flash stock firmware, install update and if there's no big change, flash stock again.....
Thats why i was wondering if the only option is flash stock to get rid of recovery
martindar said:
twrp recovery is a custom rom so never update
Click to expand...
Click to collapse
Twrp is not a Rom it's a recovery. Hence the "recovery"
Sent from my VS980 4G using XDA Premium 4 mobile app
Esteway.619 said:
Twrp is not a Rom it's a recovery. Hence the "recovery"
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, yeah I didn't want to say anything. He should read up before doing anything with his phone.
rodpgfx said:
Guys I already know all what you just said......I've done this loads of times. Just wondering if I can uninstall custom recovery without re-installing stock firmware?
I know I can take my chance and try the OTA but not without recovery gone first.
It's a lot of work to just flash stock firmware, install update and if there's no big change, flash stock again.....
Thats why i was wondering if the only option is flash stock to get rid of recovery
Click to expand...
Click to collapse
I think its possible, (but it should be really hard to do so) but the easiest way is to flash a .kdz file And you should not take the chance to update when you have recovery, it just isn't worth it. Anyways I would just have sticked with a custom rom which gets updated regulary..or flashed a kdz and get back to stock.
Btw can the good judger @Judge Joseph Dredd move the thread to q and a section? I think that it is even more help to get there
OP Moved out of the Development Threads, since this does not belong there....Please read the Forum Rules on posting.
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Leraeniesh said:
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Click to expand...
Click to collapse
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Eclipse00 said:
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Click to expand...
Click to collapse
is the CWM 100% operational ?
Last time I checked it was half baked still.
Give the Devs some time. =) atleast we got KK officially =) Loving it.
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
j27h said:
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
Click to expand...
Click to collapse
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is the forum he was using to post that update. I sent him a PM letting him know about the resolution issue(XHDPI).
http://forum.xda-developers.com/showthread.php?p=53245960
It's here
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Just used it this morning to install root on 4.4.2. Worked fine.
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
I'm assuming you have an unlocked bootloader. I had that same issue after the initial upgrade to the new OTA and bootloader. I ran through a few steps like unlocking the bootloader again (may have not done anything), I used a pre-rooted RSD flash of stock and I used the ADB method of installing the recovery instead of using fastboot.
To use the adb method I downloaded the batman 1.2 recovery tool, just renamed the version of TWRP (in this case TWRP2710-RAZR_M-KITKAT.img) to TWRP.IMG and placed it in the root of the batman folder, then I ran the flash TWRP recovery option. Note that the batman tool was designed for older firmware and you should probably not run any other functions on it if you are on the new firmware.
Batman 1.2
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
You need to remove or rename,
Code:
/system/[COLOR="Red"][B][I]recovery-from-boot[/I][/B][/COLOR]
Thanks I will give this a try. I may hold off for now I read there was a possible update coming. I would guess you would need the stock recovery to get the update to work.
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
ezdi said:
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
Click to expand...
Click to collapse
Two weeks at best, considering it's the 4.4.3, which is probably the last update we'll get from Moto, unless a miracle occurs and we're given the 4.5 or 5.0, which shouldn't land until at least 5 months after it's release (if it does release next week).
I can't believe they're already planning another update. Sitting on jb we were all pretty sure that the kk update would be the last
Sent from my DROID RAZR M using Tapatalk
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
GnatGoSplat said:
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
Click to expand...
Click to collapse
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Sent from my DROID RAZR M using Tapatalk
thewraith420 said:
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Click to expand...
Click to collapse
Yeah, I'm hoping the update is because there were bugs that were too big to ignore, but Verizon forcing them to patch the exploit is probably more likely. Definitely a shame to close it on a 2yr old phone. IMO, we need some kind of consumer protection law that forces VZ and AT&T to allow BL unlocks once a device reaches EOL. It would even be better for the environment as it does keep devices relevant for much longer and less likely to end up in a toxic Chinese burn pile.
I feel like the reason we got the exploit back was a Moto dev saw the device is reaching EOL and decided it wouldn't hurt to help the community by putting the exploit back in, because it would almost have to have been deliberate.
Well it's actually lucky that 4.4.4 didn't patch towelroot, so root, I THINK, will stay, but for the bootloader unlock, it's better now than wait with Verizon.