Related
Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.Cheers!
Great! Looks like our bell friends are having good development as well.
Sent from my MB860 using XDA Premium App
NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App
So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?
IUH1991 said:
So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?
Click to expand...
Click to collapse
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
J-Roc said:
NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
You're welcome.
Cheers!
NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....
NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
So solid man, keep up the good work!
nexxusty said:
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....
Click to expand...
Click to collapse
Hi,
I addressed this already in the OP. It's more for use with stock kernels.
Can you compile the motorola kernel source (pick one) and get a binary exact match for the stock Bell kernel?
No offense to the guys working on kernel's here, but I am not really compelled by the added features/bug fixes, and am concerned more about stability, especially when the source seems to be ATT based. Which is fine if you are running an ATT framework "rom/theme" I guess, even better if you have an ATT phone.
Cheers!
NFHimself said:
Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.Cheers!
Click to expand...
Click to collapse
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?
so does this mean it is actually possible to download more ram??
xateeq said:
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?
Click to expand...
Click to collapse
Yes, what you said.
Cheers!
geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Uhm, what?
Cheers!
geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Download more RAM? Umm...did you even read this before you posted it? or do you know absolutely nothing about what RAM is?
geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
So many people don't understand what Ram actually is *sigh*
You're not the first, I see it EVERYWHERE, google it up!
Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App
dnsdenis said:
Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Glad it worked out!
Cheers!
System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?
drolgnir said:
System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?
Click to expand...
Click to collapse
You are in the clear.
Cheers!
So, if I understand this correctly, when I flash this it will auto-fix any ROM, kernel or custom recovery that I install?
There are many confusing articles around about the EMMC brickbug that causes superbricks. I was just looking for answer to a few questions.
1. Has Samsung released a solution yet to fully revive (i.e. revive lost partitions) the device back to normal?
2. Is there an official Samsung solution to get the EMMC bricked devices working again?
3. For people who have revived their devices using the custom PIT method as described by hg42, are people having issues with the phone jamming (needing restarts) despite whatever rom they use? If so, how did you resolve it?
nirpaudyal said:
There are many confusing articles around about the EMMC brickbug that causes superbricks. I was just looking for answer to a few questions.
1. Has Samsung released a solution yet to fully revive (i.e. revive lost partitions) the device back to normal?
2. Is there an official Samsung solution to get the EMMC bricked devices working again?
3. For people who have revived their devices using the custom PIT method as described by hg42, are people having issues with the phone jamming (needing restarts) despite whatever rom they use? If so, how did you resolve it?
Click to expand...
Click to collapse
1.) No.
2.) Yes. Bring it to support - the change the motherboard. Costs? Depending on warranty...
3.) You need a summary of all the articles? No luck for you, I'm afraid. Read, read and when you finished - read again.
There are wonderful roms here with brick-save kernels. Use them or use them not.
And last... Why do you post this in General? Ever heard of Q&A-Section?
trahzebuck said:
1.) No.
2.) Yes. Bring it to support - the change the motherboard. Costs? Depending on warranty...
3.) You need a summary of all the articles? No luck for you, I'm afraid. Read, read and when you finished - read again.
There are wonderful roms here with brick-save kernels. Use them or use them not.
And last... Why do you post this in General? Ever heard of Q&A-Section?
Click to expand...
Click to collapse
Interesting way to answer. But greatly appreciated nevertheless. I do have further questions re your answer to 3, but I feel quite intimidated.
Those are excellent questions re the Emmc bug for the Note.
Let me give you my thoughts. For questions 1 & 2, I'm still waiting for a solution but I highly doubt
Samsung will fix it. For question 3, if you use the pit file to revive your Note, then use Official ICS or JB rom
you will end up getting freezes/lockups and maybe boot loops.
I would recommend using CM10.1 as its more stable to use. In the meantime, I'm enjoying my Note 2
and tinkering around with CM10 on my semi brick Note 1.
pho73 said:
Those are excellent questions re the Emmc bug for the Note.
Let me give you my thoughts. For questions 1 & 2, I'm still waiting for a solution but I highly doubt
Samsung will fix it. For question 3, if you use the pit file to revive your Note, then use Official ICS or JB rom
you will end up getting freezes/lockups and maybe boot loops.
I would recommend using CM10.1 as its more stable to use. In the meantime, I'm enjoying my Note 2
and tinkering around with CM10 on my semi brick Note 1.
Click to expand...
Click to collapse
Thanks for that, at least that was more of a straight answer which allows me to move forward. I hadnt tried the CM10. :good:
After many days of flashing different roms, I finaley got Slim rom 4.2.1 "working" with custom pit method...
It freezes sometimes and downloading from play store is a pain...
And I'm left with only 3GB out of 16GB...
Sent from my LGP880 using xda app-developers app
AW: [Q] Emmc Brick fized?
lemonbarley said:
After many days of flashing different roms, I finaley got Slim rom 4.2.1 "working" with custom pit method...
It freezes sometimes and downloading from play store is a pain...
And I'm left with only 3GB out of 16GB...
Sent from my LGP880 using xda app-developers app
Click to expand...
Click to collapse
Mine was hardbricked too jtag did it. Left 11,7 Gigs. 100% hardbrick stock recovery flash
Posting questions in general section may cause male impotence. xda premium (Closed Beta) GT-N7000 the best phone in the World! Stock Rooted XXLSZ
lemonbarley said:
After many days of flashing different roms, I finaley got Slim rom 4.2.1 "working" with custom pit method...
It freezes sometimes and downloading from play store is a pain...
And I'm left with only 3GB out of 16GB...
Sent from my LGP880 using xda app-developers app
Click to expand...
Click to collapse
I wouldnt call that working at all!
pho73 said:
Those are excellent questions re the Emmc bug for the Note.
Let me give you my thoughts. For questions 1 & 2, I'm still waiting for a solution but I highly doubt
Samsung will fix it. For question 3, if you use the pit file to revive your Note, then use Official ICS or JB rom
you will end up getting freezes/lockups and maybe boot loops.
I would recommend using CM10.1 as its more stable to use. In the meantime, I'm enjoying my Note 2
and tinkering around with CM10 on my semi brick Note 1.
Click to expand...
Click to collapse
Why is it that when we are no longer using the areas of the partition affected, with the PIT method, it is still crashing with various roms?
Which various roms crashing for you? I don't really have a good explanation why it is crashing even using the pit file. I think the partition area affected are pretty much corrupted. I've once got the latest JB working for a very short time until it freezes up many times and its not usable at all.
I would like to go back to JB again if theres actually a fix for the freeze up issue. In the meantime, I'm using CM10.1 and its much more usable as a phone with little issues/hiccups.
nirpaudyal said:
I wouldnt call that working at all!
Click to expand...
Click to collapse
Agreed
Sent from my GT-N7000 using xda app-developers app
For me, moved to NOTE 2. Note 1 freezes every time something is getting memory. for me, there was no solution. If someone else has a better solution than installing Slim ROM (which is the only one that works at all - only until the next freeze), please post it here.
asafki said:
For me, moved to NOTE 2. Note 1 freezes every time something is getting memory. for me, there was no solution. If someone else has a better solution than installing Slim ROM (which is the only one that works at all - only until the next freeze), please post it here.
Click to expand...
Click to collapse
I'm using cm10.1 dated 03032013. Haven't experience any freezes so far.
I agree Note 2 is better in everyway.
pho73 said:
I'm using cm10.1 dated 03032013. Haven't experience any freezes so far.
I agree Note 2 is better in everyway.
Click to expand...
Click to collapse
I used this rom - the only problem is that it didnt read my sd card (original one that came with the note) despite formatting.
Any updates on this topic?
I thought I should bump this post up a bit.
Wondered if there any updates people are aware of?
Thanks
nirpaudyal said:
I thought I should bump this post up a bit.
Wondered if there any updates people are aware of?
Thanks
Click to expand...
Click to collapse
I'm newbie here... i got my note 1 updated to slimbean 4.2.2 build 4.2 this morning, everything works fine until just now that the internal SD card so called emmc cant be mount. Connect to PC also cant see it.
Any help? Thanks in advanced.:crying:
123
Got the same issue as lemonbarley, but less space available.
I noticed improvements once i've deleted the HIDDEN partition and made cache afterwards as exactly 128mb.
I'm newbie here... i got my note 1 updated to slimbean 4.2.2 build 4.2 this morning, everything works fine until just now that the internal SD card so called emmc cant be ]mount. Connect to PC also cant see it.]
Click to expand...
Click to collapse
You mean the fat partition? or the ext one
Just post here any arguable question.... so far was an hell of adventure to fix the samsung.
Sd card
Its strange how these days i spend moving in cicles but today something different happen.
Appears to me that slim rom and anidroid (ics) is a bit different in comparison with paranoid rom (ics lrk)
First two have some compatibility issues. For example, on anidroid, the menu is for galaxy SII, and you cannot choose dpi.
While on slim rom you can do all that, there are screen flickers, like menu distortions, and the camera doesn't zoom at 720p.
The major difference is in how they both partition the space. This was a strange breakthrough today. Moving in cicles until this.
On first two, the phone storage is shared in two (or three) areas. while none seems to be okay on a briked phone. The second, makes the internal sd card as the (external mini sd) main addition to the phone. Why did those two make the internal storage out of the fat32 11 partion UMS. That was terrible.
I used tHis on the latest skrilax nightly and the performance boost its well nothing short of miraculous this is by far not my work but I'll share my find
http://forum.xda-developers.com/showthread.php?p=41462770
Follow the link
Cwm -tested working for me
Sent from my MB886 using Tapatalk 2
Franzferdinan51 said:
I used tHis on the latest skrilax nightly and the performance boost its well nothing short of miraculous this is by far not my work but I'll share my find
http://forum.xda-developers.com/showthread.php?p=41462770
Follow the link
Cwm -tested working for me
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Man, this worked really nice for me, I can now do Temple Run 2 with no lag - Running AOSP
Just so you know, disabling journaling means there may be data loss with unexpected shutdowns (e.g. the key combination to hard power, OS crashes, etc), which can corrupt files, including the OS if it was mounted as r/w (not by default).
I remember back in 2010 when this was big on the Samsung Moment. I was pretty much placebo on that phone. I wouldn't bother.
adamr240 said:
I remember back in 2010 when this was big on the Samsung Moment. I was pretty much placebo on that phone. I wouldn't bother.
Click to expand...
Click to collapse
Same thing on the Defy -- while it helped a tiny bit, wasn't worth doing cause of safety concerns and system data loss\file system corruption. When you can't format your file system, you don't want to corrupt it (locked bootloader problems).
The net always talks about how to Install Android 5 but I wonder whether it would be a good idea to install it in the first place.
Will I get better performance and a better phone? What about app compatibility? I just want a phone with the least bugs and problems.
Thanks
goldendye said:
The net always talks about how to Install Android 5 but I wonder whether it would be a good idea to install it in the first place.
Will I get better performance and a better phone? What about app compatibility? I just want a phone with the least bugs and problems.
Thanks
Click to expand...
Click to collapse
I'd say yes. Try it and see for yourself so you get your own opinion and not only base on what other people say. You can always go back.
I did the upgrade 2 weeks ago. It's worth it. The only compatibility issue i had was with Dungeon Hunter 5. It stopped working but it was probably a good idea to get rid of it anyway. (More slot machine than anything). Other than that, I'm loving it.
Sent from my D5803 using Tapatalk
frason said:
I'd say yes. Try it and see for yourself so you get your own opinion and not only base on what other people say. You can always go back.
Click to expand...
Click to collapse
Is going back to 4 easy?
goldendye said:
Is going back to 4 easy?
Click to expand...
Click to collapse
Yes, you just need to flash a Kitkat file from here; http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
yes
least bug and problems, 4.4.4 is the winner.
I had 5.0 on other devices and it was a joy to come back to 4.4.4 and have a rock steady experience with insane battery life.
yes you can flash back, but like the UK version, I found no online files to do so. and I can make my own, but sod it. I know what 5.0 is and I wasnt impressed at all.
Updated yesterday, performance is the same if not better, battery is the same. You should try
I think I'll play it safe and give it some time to be sure before I update. I don't have the time or the knowledge to flash back to 4.4.4. Thanks everyone!
goldendye said:
I think I'll play it safe and give it some time to be sure before I update. I don't have the time or the knowledge to flash back to 4.4.4. Thanks everyone!
Click to expand...
Click to collapse
It's easy to flash back 4.4.4, however I updated yesterday and from my opinion it is not worth it at all, the interface is more complicated, there are bugs like a memory leak on startup which make it take age to load, xposed do not work well (I had a bootloop, had to reflash the system partition). I think I am going back to KK soon ?
Hey guys! Just wanted to give you all a heads up that CM 13 is out.
LINK: https://download.cyanogenmod.org/?device=h811
Anyone facing any issues while on the ROM?
Can I just flash it if I have cm12.1 already running.
Any other update of bootloader etc needed to get it work? Don't want to get stuck in boot logo etc.
Thanks
indianx said:
Can I just flash it if I have cm12.1 already running.
Any other update of bootloader etc needed to get it work? Don't want to get stuck in boot logo etc.
Thanks
Click to expand...
Click to collapse
No, you'll need to kdz to stock M, ensure Enable OEM Bootloader unlock is checked, and then reboot into bootloader mode to 1) do OEM unlock and 2) boot into TWRP in order to permanently install TWRP. It's pretty simple. I think I spent a grand total of 10-15 minutes setting it up: http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
do i have to do anything coming from a 5.1 rom or can i just flash this over it?
SolaceKane said:
do i have to do anything coming from a 5.1 rom or can i just flash this over it?
Click to expand...
Click to collapse
Same as I posted above. If you're not yet on M, you'll need to flash the M KDZ (or OTA update to M, if you're still on stock), unlock bootloader and re-install TWRP to flash any M ROM.
SolaceKane said:
do i have to do anything coming from a 5.1 rom or can i just flash this over it?
Click to expand...
Click to collapse
Lol, this thread only has one page, and the answer is right above your post.
Sent from my LG-H811 using Tapatalk
SolaceKane said:
do i have to do anything coming from a 5.1 rom or can i just flash this over it?
Click to expand...
Click to collapse
Wow lol you just repeated the same question that was already answered literally above your post. Like you didn't even read. If your on any 5.1 ROM you have to flash the stock mm ota update first before flashing any mm ROM. After flashing the stock mm always make sure OEM unlock is enabled. Unlock your bootloader,flash twrp recovery.
How is the camera on CM? Is is there a hit to quality?
Sent from my LG-H811 using Tapatalk
There is some wanky nature to the ffc when using Snapchat. But I prefer the CM camera to the stock camera.
borgib said:
How is the camera on CM? Is is there a hit to quality?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
As with any non-stock camera app, I'm sure there is a bit of a hit to quality, since they can't access LG's closed-source camera, but honestly, I can't tell a huge quality difference myself. The Snap camera used in CM (as well as Bliss, which I'm currently running with Llama Sweet Kernel with some tweaks - I highly recommend this kernel so far for CM or Bliss, or just about any other AOSP-ish ROM) has taken some big steps forward since CM was first available for the G4. (Full disclosure, some people have had issues with the flash going at the wrong time, causing over/underexposed pics, but I haven't seen it on mine. Others have also reported a bit of a hit to video (some lagginess) but I haven't taken any video yet to confirm or deny.)
schreckles said:
As with any non-stock camera app, I'm sure there is a bit of a hit to quality, since they can't access LG's closed-source camera, but honestly, I can't tell a huge quality difference myself. The Snap camera used in CM (as well as Bliss, which I'm currently running with Llama Sweet Kernel with some tweaks - I highly recommend this kernel so far for CM or Bliss, or just about any other AOSP-ish ROM) has taken some big steps forward since CM was first available for the G4. (Full disclosure, some people have had issues with the flash going at the wrong time, causing over/underexposed pics, but I haven't seen it on mine. Others have also reported a bit of a hit to video (some lagginess) but I haven't taken any video yet to confirm or deny.)
Click to expand...
Click to collapse
Thank you very much for your reply. I suppose I'll stick with a stick ROM. Camera and video quality are very important to me. I take a lot of pictures and videos of my kids.
Sent from my LG-H811 using Tapatalk
borgib said:
Thank you very much for your reply. I suppose I'll stick with a stick ROM. Camera and video quality are very important to me. I take a lot of pictures and videos of my kids.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Honestly, and this is always my advice, I'd say go ahead and try it out. Just do a backup beforehand, and test out the camera first thing after flashing. If it's up to par, great! If not, 5 minutes later you're back to stock. Like I said, I haven't seen any of the issues a few others are reporting so far. Of course it's totally up to you. Just don't want you to deprive yourself of AOSP for something that may not effect you at all.
schreckles said:
Honestly, and this is always my advice, I'd say go ahead and try it out. Just do a backup beforehand, and test out the camera first thing after flashing. If it's up to par, great! If not, 5 minutes later you're back to stock. Like I said, I haven't seen any of the issues a few others are reporting so far. Of course it's totally up to you. Just don't want you to deprive yourself of AOSP for something that may not effect you at all.
Click to expand...
Click to collapse
I definitely have been toying with the idea of it. I'm a huge AOSP fan. I may take your advice sooner or later
Sent from my LG-H811 using Tapatalk
Thank you, DAXX. Let me get my hands clean with this one. Ji,ji,...
TURBO
Anyone got VOLTE successfully working on the latest build? I still get the switch to 3g during a call...
DAXX said:
Hey guys! Just wanted to give you all a heads up that CM 13 is out.
Anyone facing any issues while on the ROM?
Click to expand...
Click to collapse
Hello. I when I click on download, it crashes. I get "unfortunately, the process android.process.media has stopped." So far that is the only app behaving like that. Someone else can confirm this or is just me?. I even reset whole system and same issue.
TURBO
Been rocking it for a bit over a day. It runs beautifully. I've installed open gapps as well. The only issue I have is that video playback will seem to pause for a second while the audio continues, so it'll end up lagged by a second. This happens every time you pause a video too, so it'll become increasingly lagged the more you do it, leaving the audio and video totally de-synced.
Edit: Running the 02/14 nightly. Will update later and see if it gets resolved.
We already have a support thread for our devices at the G4 Int forum. All you need it to do was link that thread in our general discussion forum instead. No developers for CM13 will see this thread at all. Lol
Sent from my LG-H811 using Tapatalk
Im thinking of trying this out and wondering if the video call will be lost. Its tmobiles version of facetime but its suppose to be working on g4 note 5 gs6 edge + etc. And it does with this lastest update so im wondering whats going on.
I forgot to mention hows battery life on the rom?