Related
Hi,
I know there are dozens of threads around about flashing Custom ROMS on the Note, but I have specific requirements to be met before attempting to flash a ROM on my Note. Its not that I'm new to flashing ROMS, its just that since I know that the Note is the "most vulnerable" device when it comes to the emmc bug, I want to be on the safer side. My Note is just around a month old and I dont want to brick it due to any foolishness from my side warranty in India sucks, In simple words, even if I'm eligible for warranty, I would receive my Note in a scratched, scuffed and abused manner though in a "working" condition, God knows for how long after a freaking month or two. Well, thats warranty here in India. So, as my loss is my loss alone, I created this thread to be safe.
Coming back to the topic, I'm running Stock ICS DDLPA on Speedmod Kernel K3-7 and want to move to Paranoid Android 0.5 which I believe is a CM9 based ROM.
1) As I am on ICS (speedmod kernel k3-7), is it safe to flash a Gingerbread ROM via PC ODIN?
2) If the 1st one is a go, I do not want to increase my binary counter while rooting gingerbread or installing Paranoid. I know about TriangleAway but since it requires the CF Kernel, flashing many kernels(on the NOTE) freaks me out at the moment. So I just want to flash the ROM without any increase in binary counter.
3) In the video guide on installing Paranoid Android, I see that the person goes into CWM recovery in the Gingerbread Kernel and flashes the Paranoid ZIP file and GAPPS and then proceeds to Wipe Data\Factory Reset. But once the paranoid android ZIP file is flashed, isnt he on an ICS kernel? Correct me if I'm wrong.
4) I see that Paranoid Android uses the CM9 kernel. Is it guaranteed Safe to Wipe using this kernel? Does it have the MMC_CAP_ERASE disabled like the speedmod kernels?
5) Last, incase if I ever want to revert back to Stock ICS for any reason, is it safe to flash back to Stock ICS using PC Odin while still on the CM9 Kernel or do I need to flash the Stock Gingerbread first over the existing CM9 kernel?
It would be really helpful if my queries are answered in the same manner as I have asked above.
I have gone through all the warnings and guides here in the forum but none of them seems to specifically satisfy my needs. I would have just flashed away but since its a "NOTE" again, I really want to be on the safer side.
Thanks in advance.
Flash Abyss Kernel.
Reboot in Recovery (under advanced) <= important
Flash ROM
Flash Gapps
Full wipe (factory reset, cache + dalvik cache)
Reboot and enjoy.
To come back to Sammy ICS => PC ODIN
****
You're the first guy on this forum wanting to flash something with "specific needs". I wish you all the best. Good luck!
****
paranoid on android - galaxy note n7000
I'm sorry, all the issues which popped up lately regarding the emmc bug as kept me on stock till now. If that nasty bug wasn't there, this thread wouldn't be there in the first place. I've never run on stock on any of my phones and this is the first time that I've stayed this long on stock. Its not that I'm new to flashing or anything. I've been doing that since the Symbian and WinMo 6.5days. Its just that its a "Note" and I wish to avoid a brick anytime soon.
But why not just ask in the ROM thread. I am sorry, but every day someone opens a thread which could - looking at the very specific needs of everyone - just be handled as a post (in your case in PA by imilka) instead of its own thread.
Nevertheless I am glad to see that you informed yourself.
If you felt better, then install one of the per rooted GB Roms.
paranoid on android - galaxy note n7000
satishp said:
1) As I am on ICS (speedmod kernel k3-7), is it safe to flash a Gingerbread ROM via PC ODIN?
2) If the 1st one is a go, I do not want to increase my binary counter while rooting gingerbread or installing Paranoid. I know about TriangleAway but since it requires the CF Kernel, flashing many kernels(on the NOTE) freaks me out at the moment. So I just want to flash the ROM without any increase in binary counter.
3) In the video guide on installing Paranoid Android, I see that the person goes into CWM recovery in the Gingerbread Kernel and flashes the Paranoid ZIP file and GAPPS and then proceeds to Wipe Data\Factory Reset. But once the paranoid android ZIP file is flashed, isnt he on an ICS kernel? Correct me if I'm wrong.
4) I see that Paranoid Android uses the CM9 kernel. Is it guaranteed Safe to Wipe using this kernel? Does it have the MMC_CAP_ERASE disabled like the speedmod kernels?
5) Last, incase if I ever want to revert back to Stock ICS for any reason, is it safe to flash back to Stock ICS using PC Odin while still on the CM9 Kernel or do I need to flash the Stock Gingerbread first over the existing CM9 kernel?
It would be really helpful if my queries are answered in the same manner as I have asked above.
Thanks in advance.
Click to expand...
Click to collapse
1.flashing stock rom with pc odin is safe. Irrespective of rom you are having.
2.flashing stock rom.doesn't raise flash counter.
3. B'coz it now running on cm9 kernel which is safe.
4.yes emmc erase cap driver is.diabled, but.if you talking in terms of 'guaranteed' then even developers also not using this term still on ics
5. my answer 1 hav already answered this.
Sent from my GT-N7000 using xda premium
Trust me I was just as cautious as you are. But as long as you use a safe kernel, reboot recovery and then perform 3 wipes you will be fine.
I'm pretty sure speedmod is a safe kernel. Someone correct me if I'm wrong.
Good luck!! I go through more roms on my phone then I do underwear haha
Sent from my GT-N7000 using xda app-developers app
AA1973 said:
Flash Abyss Kernel.
Reboot in Recovery (under advanced) <= important
Flash ROM
Flash Gapps
Full wipe (factory reset, cache + dalvik cache)
Reboot and enjoy.
To come back to Sammy ICS => PC ODIN
****
You're the first guy on this forum wanting to flash something with "specific needs". I wish you all the best. Good luck!
****
paranoid on android - galaxy note n7000
Click to expand...
Click to collapse
If I flash Abyss Kernel using MobileODIN, I wont be able to boot into my existing ICS ROM as it is a gingerbread based kernel, am I right? Then, how do I confirm I'm on Abyss Kernel while in recovery?
dr.ketan said:
1.flashing stock rom with pc odin is safe. Irrespective of rom you are having.
2.flashing stock rom.doesn't raise flash counter.
3. B'coz it now running on cm9 kernel which is safe.
4.yes emmc erase cap driver is.diabled, but.if you talking in terms of 'guaranteed' then even developers also not using this term still on ics
5. my answer 1 hav already answered this.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for your quick reply. To be frank, I wanted to hear from you as I've seen all your guides.
My question no2 is not about flashing stock rom but will rooting the stock gingerbread with custom recovery raise counter? I do not want to increase the binary count. Would flashing the above mentioned AbyssKernel also do the job?
If you follow my guides to root gingerbread it won't raise counter. In my guide i have never mentioned any procedure which can raise counter.
Just one suggetion, if you want to flash gingerbread as only for switching purpose, then go with prerooted rom(find from my signature) and flash using pc odin. After flashing you will have gb rom +root+cwm
Sent from my GT-N7000 using xda premium
I used this guide, it's so simple and there are all of the steps including rootable GB rom.
http://forum.xda-developers.com/showthread.php?t=1763151
Sent from my GT-N7000 using xda app-developers app
dr.ketan said:
If you follow my guides to root gingerbread it won't raise counter. In my guide i have never mentioned any procedure which can raise counter.
Just one suggetion, if you want to flash gingerbread as only for switching purpose, then go with prerooted rom(find from my signature) and flash using pc odin. After flashing you will have gb rom +root+cwm
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Is there any complications flashing the AbyssKernel instead? Is it safe to flash with MobileODIN? Would it increase binary counter as I'm moving to a Gingerbread based custom kernel from ICS?
satishp said:
.....
1) As I am on ICS (speedmod kernel k3-7), is it safe to flash a Gingerbread ROM via PC ODIN?
Click to expand...
Click to collapse
Yes.
satishp said:
2) If the 1st one is a go, I do not want to increase my binary counter while rooting gingerbread or installing Paranoid. I know about TriangleAway but since it requires the CF Kernel, flashing many kernels(on the NOTE) freaks me out at the moment. So I just want to flash the ROM without any increase in binary counter.
Click to expand...
Click to collapse
If it's completely stock, it won't increase your binary counter, also flashing kernels is 100% safe, even with the emmc bug.
satishp said:
3) In the video guide on installing Paranoid Android, I see that the person goes into CWM recovery in the Gingerbread Kernel and flashes the Paranoid ZIP file and GAPPS and then proceeds to Wipe Data\Factory Reset. But once the paranoid android ZIP file is flashed, isnt he on an ICS kernel? Correct me if I'm wrong.
Click to expand...
Click to collapse
No, unless you reboot right after flashing the rom, you're still on whatever kernel you used to flash, also CM9 kernels are safe.
satishp said:
4) I see that Paranoid Android uses the CM9 kernel. Is it guaranteed Safe to Wipe using this kernel? Does it have the MMC_CAP_ERASE disabled like the speedmod kernels?
Click to expand...
Click to collapse
Yes.
satishp said:
5) Last, incase if I ever want to revert back to Stock ICS for any reason, is it safe to flash back to Stock ICS using PC Odin while still on the CM9 Kernel or do I need to flash the Stock Gingerbread first over the existing CM9 kernel?
Click to expand...
Click to collapse
Yes, but keep in mind stock ICS has the bug, so unless you're using a different kernel on it (SpeedMod, etc), you're not safe.
I dont get ur.question,Y u need to flash abyss kernel?
Sent from my GT-N7000 using xda premium
dr.ketan said:
I dont get ur.question,Y u need to flash abyss kernel?
There's a galaxy note website, not sure I should mention it or not, where the guy uses abyss 4.2 all the time to "safely" flash new ICS roms. He flashes this kernel in recovery and then advance reboots into abyss recovery. Once in recovery he does the dalvik/cache wipes and factory resets before installing an ICS rom. I guess he uses this method as a way to avoid using pc odin to save time.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yes you can use it, abyss kernel is GB kernel.
To test if I had the EMMC bricking bug I just flashed a rom. Hahaha.
Sent from my GT-N7000 using xda app-developers app
Thanks a lot for all your support guys. I'm running Paranoid 0.5. The black clipping\crush is worst on the CM9 kernel and its everywhere. even in the UI. It really bothers me.
Could anyone suggest me a Good kernel with the least clipping and also any "Visually Pleasing" ROM (like MIUI) for the note? Paranoid looks mostly stock as its CM9 based but the tablet mode is just brilliant.on the Note. Its like the best of both worlds.
Anyone else have the issue of it just continuously trying to boot? I'm using the CWM auto-loki that's in the development section.
Reflashed it three more times. Now it freezes @ Samsung battery screen when charging, or if I wait long enough it'll unfreeze. Still loops at Slim Bean startup, what sucks though is that for one thing it mounts as an MTP device so it seems like it's on but just not initializing, another thing is that the original flash I was able to get to the slim bean battery charging screen (but obviously still couldn't turn it on)
Thinking it might be a kernel issue, since I installed ktoonsez's AOSP kernel when I installed it. Any recommendations of a kernel to use? I'm using the CWM recovery that has auto loki so, I could probably use ones made for 9500,9505, etc.
(Pasted this from the Slim Bean thread, haven't gotten an answer in like 5 hours and it's a little urgent xD. I'm on the AT&T S4 of course, any other information I'll be glad to provide. Hopefully this is just a simple fix)
I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app
Spunjah413 said:
I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you on then, just stock?
Stock Kernel.
Sent from my SGH-I337 using xda app-developers app
I installed Slim Bean with Ktoon kernel and it worked fine. Just make sure to wipe system and the caches. It did take a little longer to boot the first time but after that it was all good.
Sent from my SGH-I337 using xda app-developers app
Isn't ktoonsez kernel for a Touchwiz based ROM?
Slim Bean is AOSP, therefore i'm not sure they jive correctly, which would clearly explain the OP's problem.
EDIT: Didn't realize he updated an AOSP based Kernel. In anycase OP, I would still attempt using the stock kernel to see if you problems get fixed.
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.
_Dennis_ said:
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.
Click to expand...
Click to collapse
Thanks for clarification.
LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
I know someone else clarified this already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.
iKat said:
I know someone else clarified htis already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.
Click to expand...
Click to collapse
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data
LostInMyHead said:
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data
Click to expand...
Click to collapse
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;
iKat said:
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;
Click to expand...
Click to collapse
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread
LostInMyHead said:
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread
Click to expand...
Click to collapse
Oh my lord, thank you good sir. Slim Bean is up and working as of right now ^^;. May be a little bit before I apply a custom kernel though o.o
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
bubblebuddyi said:
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
rcklss1 said:
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
bubblebuddyi said:
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
Click to expand...
Click to collapse
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Baldilocks said:
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Click to expand...
Click to collapse
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
bubblebuddyi said:
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
Click to expand...
Click to collapse
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Baldilocks said:
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Click to expand...
Click to collapse
can you link to a stock kernel for the AT&T i337?
xxhorseriderxxx said:
can you link to a stock kernel for the AT&T i337?
Click to expand...
Click to collapse
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
highaltitude said:
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
Click to expand...
Click to collapse
okay, assuming you're using the AT&T variant, I did this:
I got the looping "installing camera firmware" and tried faux an ktoonsez with no luck
I flashed this tmobile stock kernel and the camera firmware updated successfully by going into the camera app.
I then just flashed faux kernel back and everything worked great.
http://forum.xda-developers.com/showthread.php?t=2271976
I use shabbypenguin's auto loki CWM recovery, but you'll have to definitely flash the loki patch after the tmo kernel to make this work.
http://forum.xda-developers.com/showthread.php?t=2291956
hi all , sorry but my english is so bad
i just bought a galaxy s4 att secondhand , this had bassband UCUAMDL . and i checked the lastest version of it is 4.2.2
can i upgrade my phone up to 4.4 ?
and i dont know terminology about "MF3 - MK2 ............."
could you tell me ?
thanks so much :victory::victory::victory:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
HORiZUN said:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
Click to expand...
Click to collapse
thanks so much ,
can you get me links :crying:
but MF3 - MK2 ............. what is it ?
when i flash rom , what i have to notice ?
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
i am in 4.2.2
sonluyen94 said:
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
Click to expand...
Click to collapse
I have the same question. hopefully someone will be able to explain it to us.
MF3 would be the last three digits of your system software version
HORiZUN said:
MF3 would be the last three digits of your system software version
Click to expand...
Click to collapse
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
You don't have MF3, and that's a good thing. You can install a custom recovery. You need to root, install a custom recovery, and then you can start flashing roms.
sonluyen94 said:
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
Click to expand...
Click to collapse
nogods said:
I have the same question. hopefully someone will be able to explain it to us.
Click to expand...
Click to collapse
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
npjohnson said:
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
Click to expand...
Click to collapse
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
sonluyen94 said:
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
Click to expand...
Click to collapse
Most if not all. They're all built from either GPE or CM.
All good advice. Plus when you root and get Twrp recovery installed do a backup thru Twrp (Nandroid) and keep on phone and put a copy on pc. That way you have something to restore if you get in trouble. Also, your bootloader is not unlocked. No Att i337s are. Instead devs use an exploit called Loki-Doki to bypass Sammy's security checks to allow custom roms/kernels etc to flash. You can google Loki Doki and read up on it. If the rom or kernel is not loki'd you will have to flash the zip thru recovery to allow the rom or kernel to flash. You will come across this when flashing International roms and kernels. I don't have link any more so maybe someone else can link it. Keep it on SD card. Like noted read OP carefully and last 20 pages of rom thread. Builds newer than MDL are blocked by Att from using Loki and require SafeStrap. Which you don't need to worry about. Although you can read up on it. Good Luck. [emoji1]
Sent from my iPhone 6 Plus using Tapatalk
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
plasticglock said:
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
Click to expand...
Click to collapse
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
plasticglock said:
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
Click to expand...
Click to collapse
ROM manager didn't work. It said it installed cwm recovery but it didn't. I was able to install the latest TWRP with this ROM Installer and it worked like a charm! I then installed my custom TWRP from there, rebooted recovery, and installed Danvh's Google edition. I'm setting it up right now. I'm so happy to get my phone back. I just hope the odin flash fixed my problems.
To the OP try ROM installer to get your custom recovery going. Also if you like simple and fast AOSP check out Danvh's google edition rom, but stick to 4.4.4 for now. 5.0 is out but its buggy. Here's a link to the custom version of twrp that I use. https://www.dropbox.com/l/iDQQqlzNbyiFbQrMF4XcRc It's already loki'd so you can flash it if you have any problems with the latest build.
hello everybody here !
i've a problem when install GOLDENEYE 53 rom on my S4 AT&T ( SGH-I337 )
when i install the rom from safestrap recovery
in 22% give a error " set_metadata_recursive: some changes failed "
i try to install from 4.4.2 , 4.4.4 , 5.0.1 and still give this error
i just want to deodex my stock rom but i don't know how to deodex .. then i found the GOLDENEYE rom but i can't flash the rom
anyone help me please
I don't know much about safe strap as I'm still on the exploitable MDL bootloader, but make sure you are using the latest safe strap version. I think you have to boot the ROM in slot 1/main ROM slot. You also probably need to wipe system, data, cache partition, and dalvik cache too just like booting ROMs with TWRP recovery. There's also a guide here:
https://forum.xda-developers.com/ga...guide-to-install-custom-rom-i337-att-t3483736
StoneyJSG said:
I don't know much about safe strap as I'm still on the exploitable MDL bootloader, but make sure you are using the latest safe strap version. I think you have to boot the ROM in slot 1/main ROM slot. You also probably need to wipe system, data, cache partition, and dalvik cache too just like booting ROMs with TWRP recovery. There's also a guide here:
https://forum.xda-developers.com/ga...guide-to-install-custom-rom-i337-att-t3483736
Click to expand...
Click to collapse
Thanks 4 replay
i'm using SafeStrap 3.75 ( Last Version )
and when i install i wipe system , data , cache partition and dalvik but it still failed
i've tried from 4.4.2 , 4.4.4 and 5.0.1
what should i do ?
if there are a method to DeOdex the system ( 5.0.1 stock ) tell me
i just wanna use xposed on 5.0.1 .
If I can recall correctly when I flashed the goldeneye rom a couple months ago I used an older version of safestrap... I just looked 3.72. You have to use this one newer ones won't work for some reason I remember reading. The rom runs great I suggest it to anyone who still has an s4 lying around.
paintballa628628 said:
If I can recall correctly when I flashed the goldeneye rom a couple months ago I used an older version of safestrap... I just looked 3.72. You have to use this one newer ones won't work for some reason I remember reading. The rom runs great I suggest it to anyone who still has an s4 lying around.
Click to expand...
Click to collapse
Ah thanks for pointing out he needs an earlier safe strap version, I figured the newest one would work. Of course this is from a guy (me) that is still on the MDL bootloader so I know very little about safe strap. Goldeneye is an awesome ROM, only 2 or 3 things I don't like about it. Other than that it is a very good ROM.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
moutasem_saleh said:
Thanks 4 replay
i'm using SafeStrap 3.75 ( Last Version )
and when i install i wipe system , data , cache partition and dalvik but it still failed
i've tried from 4.4.2 , 4.4.4 and 5.0.1
what should i do ?
if there are a method to DeOdex the system ( 5.0.1 stock ) tell me
i just wanna use xposed on 5.0.1 .
Click to expand...
Click to collapse
There is a way to deodex the stock ROM, but it involves knowing how Android programming languages work, which i do not know. Try doing what paintballa said in the post above and use safe strap 3.72 to boot golden eye Rom.
StoneyJSG said:
Ah thanks for pointing out he needs an earlier safe strap version, I figured the newest one would work. Of course this is from a guy (me) that is still on the MDL bootloader so I know very little about safe strap. Goldeneye is an awesome ROM, only 2 or 3 things I don't like about it. Other than that it is a very good ROM.
Glad you got it working. May I ask what it is you don't like about it?
Click to expand...
Click to collapse
paintballa628628 said:
StoneyJSG said:
Ah thanks for pointing out he needs an earlier safe strap version, I figured the newest one would work. Of course this is from a guy (me) that is still on the MDL bootloader so I know very little about safe strap. Goldeneye is an awesome ROM, only 2 or 3 things I don't like about it. Other than that it is a very good ROM.
Glad you got it working. May I ask what it is you don't like about it?
Click to expand...
Click to collapse
I don't like that when you push the home button to make the screen come on, it stays on for like 1.3 seconds only. You cannot see who a text message is from on the lock screen unless you enable "show preview of message on notifcation status bar". The way call and message logs work (if you set it to say message logs only and then exit out, when you come back it auto resets to "all logs"). The widget tab in the app drawer is gone. Battery life was way better when i was on jellybean 4.2.2 before installing golden eye, of course this just might be how lollipop works. Other than those few things it's a solid ROM and I highly recommend it.
Click to expand...
Click to collapse