Related
Hey guys. So i've been beating my head against the wall here, trying to search ( yes as in using google and the xda search ) for a solution.
I keep trying to flash stock based samsung roms, they would flash, but when i try to open the camera, it opens but it freezes and then comes back saying camera failed. So I wait about 10 minutes, and the camera works...but only for about a minute, then it freezes and then never opens again.
I've tried flashing all of faux123 kernels, only one worked ( 006-MDX ) but the camera still has issues and I can't seem to find any other kernels compatible with the I337M.
Anyways, I've now tried flashing a I337M firmware based custom rom and it boots but now there it just wont boot up at all, just gets to the samsung logo and sits there, I've tried flashing other kernels but nothing will help. I'm going to have to Odin back to stock, but I'm wondering what Kernels are ok to use with the I337M so that this doesn't happen to me again in the future.
Any help and I'll have my thanks finger ready
EDIT: Ok, so after some poking around, it seems that T-Mobile kernels work well with the I337M. Can anyone confirm this for me before I bork my device again? (currently doing an odin back to stock and re-rooting... =(
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
TheSmokingAndroid said:
Hey guys. So i've been beating my head against the wall here, trying to search ( yes as in using google and the xda search ) for a solution.
I keep trying to flash stock based samsung roms, they would flash, but when i try to open the camera, it opens but it freezes and then comes back saying camera failed. So I wait about 10 minutes, and the camera works...but only for about a minute, then it freezes and then never opens again.
I've tried flashing all of faux123 kernels, only one worked ( 006-MDX ) but the camera still has issues and I can't seem to find any other kernels compatible with the I337M.
Anyways, I've now tried flashing a I337M firmware based custom rom and it boots but now there it just wont boot up at all, just gets to the samsung logo and sits there, I've tried flashing other kernels but nothing will help. I'm going to have to Odin back to stock, but I'm wondering what Kernels are ok to use with the I337M so that this doesn't happen to me again in the future.
Any help and I'll have my thanks finger ready
EDIT: Ok, so after some poking around, it seems that T-Mobile kernels work well with the I337M. Can anyone confirm this for me before I bork my device again? (currently doing an odin back to stock and re-rooting... =(
Click to expand...
Click to collapse
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
blyndfyre said:
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
Click to expand...
Click to collapse
Ya, I've done the whole adam kernel in the past, updated the camera firmware, everything was fine, but this time around, the firmware didn't need updating, at least i don't think so, considering the camera app launches, but sits at a black screen and then gives me a message that camera failed. it never tries to update the firmware like it did in the past. thanks though =)
TheAxman said:
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
Click to expand...
Click to collapse
Ya, I have been trying the correct firmwares for my device and nothing seems to fix it, thanks though
TheAxman said:
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
Click to expand...
Click to collapse
Most of the AT&T kernels are Loki :s... with a custom recovery that auto Loki I don't understand why to Loki a Rom... besides making it only for AT&T :s
I have a stock kernel that I backed up with twrp... the rest are T-Mobile
Sent from my i337M
blyndfyre said:
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
Click to expand...
Click to collapse
Wait, on the unlocked bootloader devices, you mean the other carriers kernels is ok to flash? man, I seriously wish our att was unlocked, this is good to know thanks.
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
TheSmokingAndroid said:
Ya, I've done the whole adam kernel in the past, updated the camera firmware, everything was fine, but this time around, the firmware didn't need updating, at least i don't think so, considering the camera app launches, but sits at a black screen and then gives me a message that camera failed. it never tries to update the firmware like it did in the past. thanks though =)
Ya, I have been trying the correct firmwares for my device and nothing seems to fix it, thanks though
Click to expand...
Click to collapse
I stand corrected, your device from the post earlier says you can use other kernels. what a concept.
TheAxman said:
Wait, on the unlocked bootloader devices, you mean the other carriers kernels is ok to flash? man, I seriously wish our att was unlocked, this is good to know thanks.
Click to expand...
Click to collapse
Yeah us SGH-I337M users can use other device ROM's and Kenels. (Doubt not the 9500 because of hardware differences)
We pay for our unlocked bootloader in outrageous plans from our mobile providers though!
im in winnipeg here on the i337m rogers and have no problem with the kernal in my signature
blyndfyre said:
Yeah us SGH-I337M users can use other device ROM's and Kenels. (Doubt not the 9500 because of hardware differences)
We pay for our unlocked bootloader in outrageous plans from out mobile providers though!
Click to expand...
Click to collapse
I can imagine, I still have a g3 that is in working order with a sim, and it is cool to see the loader unlocked. although on the g4, as long as I can flash a rom, I do not care how it works. I am a happy camper right now.
Thanks for clearing up the kernel question I had, can use that info when helping others. Thanks.
TheAxman said:
I can imagine, I still have a g3 that is in working order with a sim, and it is cool to see the loader unlocked. although on the g4, as long as I can flash a rom, I do not care how it works. I am a happy camper right now.
Thanks for clearing up the kernel question I had, can use that info when helping others. Thanks.
Click to expand...
Click to collapse
I guess with LOKI you are still set, the biggest drawback with the locked bootloader is probably slower device reboots, as you see the custom screen?
Your welcome about the kernel question I always see you helping others. Fell free to toss me a thanks.
blyndfyre said:
I guess with LOKI you are still set, the biggest drawback with the locked bootloader is probably slower device reboots, as you see the custom screen?
Your welcome about the kernel question I always see you helping others. Fell free to toss me a thanks.
Click to expand...
Click to collapse
I have no problem on the thanks, but I have none left today, you and another killed em up...I will catch you though.
Thanks, here, and 1 a coming.
Could somebody please share a link to download Rogers/Fido stock kernel (rooted or not rooted) for i337M please ?
Thanks!
fmark said:
Could somebody please share a link to download Rogers/Fido stock kernel (rooted or not rooted) for i337M please ?
Thanks!
Click to expand...
Click to collapse
Thread containing Canadian SGH-i337m stock firmware and kernels:
http://forum.xda-developers.com/showthread.php?t=2269304
Link to Rogers kernel:
http://hotfile.com/dl/215149326/c15...GH-I337M-RWC-I337MVLUAMDJ-1366643831.tar.html
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.
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
krazie1 said:
This is a thread to see if anyone has ideas on porting CWM or TWRP to our device? Any ideas of getting a custom recovery on this phone is welcomed. We have Root for the At&t/Verizon variants, custom recovery would be topping to the cake.
Click to expand...
Click to collapse
Dont we need an unlocked bootloader first?
chrisexv6 said:
Dont we need an unlocked bootloader first?
Click to expand...
Click to collapse
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
EDIT: I thought about it and your right, you always have to unlock the bootloader before you install the Custom Recovery.
krazie1 said:
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
Click to expand...
Click to collapse
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
kexec is required to flash a kernel.
Safestrap is a way to flash somewhat custom ROMs (without kexec you need to use stock kernel) without recovery installed but it needs to be adapted to each specific phone. Right now I think they are working on a version that will work with the S4, not sure how attractive the G2 is (or will be).
krazie1 said:
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2443165 <---- these guys are the ones who worked most of the magic for Optimus G (and Pro?).
You guys first need Root to do anything (which i believe you have). Then you need a Custom Recovery. Installing a Custom Recovery can be accomplished via a workaround or by unlocking the bootloader. A workaround like loki by djrbliss on the Galaxy S4 which isn't an unlock but more so a bypass or like Safestrap by Hashcode.
Here is the man djrbliss.
http://forum.xda-developers.com/showthread.php?t=2358871
https://twitter.com/djrbliss
Is there any news on this? I cant even find a good place to look for info about this phone yet.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Darkestred said:
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Click to expand...
Click to collapse
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
WACOMalt said:
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
Click to expand...
Click to collapse
I found it. server is chat.freenode.net room is lg-g2. Not very much going on in there at the moment.
i completely agree with the said explanation. but I'm having difficulties with my device i.e. LG G2 (D802).
I'm rooted with custom recovery TWRP and unable to install most of AOSP roms based on 4.4 KitKat. New Custom roms are coming up very frequently now for this device but so far I'm able to flash ParanoidAndroid Rom and modifited stock rom... Apart from this I always gets error while flashing the rom.
Most of the time Error comes up saying 'Status 7 Error' and 'unable to execute update binary'.
I did google on this subject and tried everything i found but the problem still exist.
I never had these problem flashing LG Stock or Android 4.3 based roms. Need advise on this subject. By the way any help on unlocking the bootloader????
thanks:good:
krazie1 said:
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
Click to expand...
Click to collapse
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
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.