After installing the XXLSA Leak from sammobile.com (Thanks!) I immediately got a small update OTA to XXLSB. And after that the OTA update to XXLSC!
Download Links temporarily removed. Have to check content.
Warning: This is not an installable Custom Rom. It gives Rom builders/developers the necessary files for compiling new, nice Custom Roms.
Contents:
factoryfs.img: /system
hidden.img: /preload
zImage
modem.bin
Hints/Errors:
In the zip I named /system as "fsfactory.img". Rename it to "factoryfs.img" if you want to use the android kitchen for buillding your Custom Rom.
If you use dsixda's kitchen and get an error "Bad Magic" with simg2img.exe: the conversion to ext4 for factoryfs.img and cache.img seems to be not necessary - they are already?!. I just tried to rename factoryfs.img to ext_factoryfs.img and could proceed in the script.
I changed a few lines in a script "simg_files_to_working_folder" in the kitchen, so that the above problems and the use of hidden.img works
I hope to see nice and usable Custom Roms soon. Good luck and have fun.
If something is wrong or missing: please tell me, I will update if possible.
Thanks for your patience. ThaiDai
Update: I'm making a deodexed Rom and want to make a small one. If this works and there isn't a Small XXLSC until then I will upload this too.
ThaiDai said:
I will try to make a complete dump from the new XXSLC which I got after installing the new leak XXSLA from sammobile.com today.
After OTA to XXSLB I got XXSLC within 5 minutes.
I just started to make a system dump with adb and now have to make the same for the /preload (and maybe /data?).
And so maybe I can provide a base for other developers to use this for new Custom Roms.
As a start I added 2 snapshots and the build.prop
Update: /system and /preload noch on my local harddisk
Click to expand...
Click to collapse
I think u should not root your device just to keep getting those updates just an idea lol its all your choice thank u so much
Sent from my GT-N7000 using Tapatalk 2
Awesome news -- fun times ahead
Now I pulled the /system, /preload and boot.img and modem.bin
Comparing this with eybees zip-file for LSA I think that should be all files I need for building a CWM installable ROM.
But I think I should sleep a few hours first.
In the /preload folder are 6 bloatware apps (Hugendubel, myTaxi etc.) in a folder DBT\hidden_apps.
And in /preload/symlink/system/app there are 31 apks, so our /system should be more relaxed now.
Maybe you could upload the new modem first?
So we can try it!
Would be cool
Thanks in advance
sent from my G-Note
hara74 said:
Maybe you could upload the new modem first?
So we can try it!
Would be cool
Thanks in advance
sent from my G-Note
Click to expand...
Click to collapse
Im not completely sure if the file and the way I "dd" it in the adb shell is completely correct. And if I'm not sure I not will provide something which can "hurt" devices - that wouldn't be ok.
So wait until morning...
It's ok m8.
Thanks anyway
sent from my G-Note
woow Nice !
Did you get OTA even not in Germany?
Can you tell us if the spen is ok for you ? I'm not able to crop with the spen on lsa dump (media scanning is running).
Envoyé depuis mon N7000
I'm waiting eagerly.
They keep releasing these updated LEAKED versions, Samsung needs to make an OFFICIAL release already!
So eybee1970 was just right.
Sent from my GT-N7000 using xda premium
I think we will all only be truly happy when we are all on LSD...
I wonder what the trigger for getting that update is?
I have a German DBT phone, this leak is a DBT update I'm just not in Germany (am in australia)
Does this mean if we get a hand on sammobiles LSA leak,we would get ota update to all future leaks?:-O
Edit:downloading xxlsa from sammobile now to try out my luck .
Downloading via 3g in my class while professor is yelling around on accountancy
Will report in the evening after flashing via odin.
Sent from my GT-N7000 using xda premium
WoW...!! Graet News,
Thanks for the information.
:laugh:
I flash last night vía odin stock leak LSA and check OTA today and nothing happend, I will try vía Kies tomorrow but hope that Eybee release LSC from dump... there's no difference with odin version
Sent from my GT-N7000 using xda app-developers app
eybee asked me yesterday evening for a dump and offered help. But when I answered he wasn't online anymore. So let's see what we get in the evening or on the coming weekend.
I'm sure I will not be the only one who is getting this OTA update. I'll do my best to generate a usable CWM for the Rom cookers.
I guess they prefer the raw dump, and they will develop and customise accordingly. Perhaps consider posting the Dump as Eybee did previously on the first leak of LS2.
Related
As it says the update for ASUS ICS, but CWM flashable.
*WARNING* If you are rooted, you will need OTA rootkeeper from Market to flash this patch, or flash superuser after rebooting at least once. Currently US and WW ROMs only.
--If someone has an update from another version (CN, etc.) that they want to use, PM me with a link to the file and I can build/edit a script for that too and add it in--
You should be on an odexed stock ROM (rooted of-course) in order for this to work. If you are on a custom ROM, don't bother, it won't work for you. You will need to wait for the dev of your ROM to make a patch or upgrade.
I set this up to only flash the kernal and the patches. Recovery will not be effected. This is confirmed working for me.
The US version -- http://www.mediafire.com/?3aa16qy7sh4t9m4
The WW version -- credit to Lizard -- http://www.mediafire.com/?nw4zgwvl3yug0tw
The TW version -- thanks to wai43 for the files -- http://www.mediafire.com/download.php?cfq6d5lug4q4sd8
I will not be responsible if you brick your tablet. This patch worked fine for me, but may not work for others.
If I'm on stock rooted ics... Should I full wipe? Or just wipe cache and flash over? Thanks
Sent from my Transformer TF101 using Tapatalk
Ep3n3wp said:
If I'm on stock rooted ics... Should I full wipe? Or just wipe cache and flash over? Thanks
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I didn't wipe anything. It worked fine for me. It works just like a normal update. You may need to be sure to have all the factory installed files though. I did the update from a full stock, rooted ROM. Worked great.
You sir are awesome. Worked perfectly.
For those like mE that edited thier system.
1. I flashed ics full over my set up to restore it without losing my settings.
2. Root keeper to keep root.
3. Flashed this update.
4. Used root keeper to restore root.
5. Profit????
tweaked said:
You sir are awesome. Worked perfectly.
For those like mE that edited thier system.
1. I flashed ics full over my set up to restore it without losing my settings.
2. Root keeper to keep root.
3. Flashed this update.
4. Used root keeper to restore root.
5. Profit????
Click to expand...
Click to collapse
Honestly, I don't know if we can profit from this... lol, but thanks is just fine. I've been dabbling in this crap for years, but I had to go back to the drawing board to get that script to work right. I hope that ASUS has their crap together and don't release a bunch of patches over the next few months, that would suck for all the devs. It is supposed to have some benefits, but I've been playing with this for a few hours and haven't seen anything amazing yet... I'm working on some thing based on this and will release soon.
BTW, for those with random reboot issues, I have yet to have experienced that -- since the original update. Anyway, just my 2 cents.
sent from my ASUS Transformer running modded ICS using Tapatalk
Sharpe351 said:
Honestly, I don't know if we can profit from this... lol, but thanks is just fine. I've been dabbling in this crap for years, but I had to go back to the drawing board to get that script to work right. I hope that ASUS has their crap together and don't release a bunch of patches over the next few months, that would suck for all the devs. It is supposed to have some benefits, but I've been playing with this for a few hours and haven't seen anything amazing yet... I'm working on some thing based on this and will release soon.
BTW, for those with random reboot issues, I have yet to have experienced that -- since the original update. Anyway, just my 2 cents.
sent from my ASUS Transformer running modded ICS using Tapatalk
Click to expand...
Click to collapse
I didn't have the reboot error either. I wasn't even going to install the update. But since you made it easy....
Thanks for the uneventful update.
I HAVE experienced RR on ICS; will see what happens.
The poll in the other thread does not lead me to believe that this update fixes all the problems that lead to random reboots.
Anyway, thanks.
Btw, I tried to capture the update blob but after I renamed it, it disappeared from the /cache
I was just curious as to what you did to the update to defang it.
Is removing the recovery enough?
Does it also carry a bootloader update which you also have to remove?
feisty_noodle said:
Thanks for the uneventful update.
I HAVE experienced RR on ICS; will see what happens.
The poll in the other thread does not lead me to believe that this update fixes all the problems that lead to random reboots.
Anyway, thanks.
Btw, I tried to capture the update blob but after I renamed it, it disappeared from the /cache
I was just curious as to what you did to the update to defang it.
Is removing the recovery enough?
Does it also carry a bootloader update which you also have to remove?
Click to expand...
Click to collapse
I packed only the boot.img in the file. All the other junk is gone. From what I saw in the unpacked boot.img, there appears to be minor changes in the files. Quite possibly updates.
sent from my ASUS Transformer running modded ICS using Tapatalk
Can you just add superuser binary and the app plus busybox to the user script? I'm curious how you could go about further de clawing this update for rooted users.. maybe not wipe the system xbin folder just amend it? I'm out of my element...
luna_c666 said:
Can you just add superuser binary and the app plus busybox to the user script? I'm curious how you could go about further de clawing this update for rooted users.. maybe not wipe the system xbin folder just amend it? I'm out of my element...
Click to expand...
Click to collapse
I backed up su with OTA RootKeeper then rebooted into CWR. I flashed the zip, rebooted and let the update "optimize [my] apps". Once that was done I was greeted with my usual homescreen. A toast notification informed me WebKey was granted SuperUser permission, as always happens on bootup.
Surprised, I launched SuperUser and saw a corresponding new entry in the log. I double checked my current version of su, which was found to be current. I'm assuming that a "No newer version of su available" means su (and thus root) wasn't removed during the upgrade.
I next launched OTA RootKeeper which oddly reported my TF101 was no longer rooted. Nonetheless I hit RESTORE and root is back: or rather OTA RootKeeper is happy now.
--L.
Patch good for Non US Firmware?
I have tried to flash this update but I get an asset failure. Could that be due to the fact that I am running stock WW ICS and not the US version?
error
I got the error in the image I tried a couple of options including the microsd.
https://www.sugarsync.com/pf/D7256720_703_699618527
Sorry I cant get the image to show.
Sharpe351 said:
I didn't wipe anything. It worked fine for me. It works just like a normal backup. You may need to be sure to have all the factory installed files though. I did the update from a full stock, rooted ROM. Worked great.
Click to expand...
Click to collapse
Did you do this in CWM or no? I dont have CWM installed dont really care to bc Im not flashing any ROMs until NVflash works on my sbk version
Sent from my Transformer TF101 using Tapatalk
avasman said:
I have tried to flash this update but I get an asset failure. Could that be due to the fact that I am running stock WW ICS and not the US version?
Click to expand...
Click to collapse
you have to be on a US firmware.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
lemonoid said:
Did you do this in CWM or no? I dont have CWM installed dont really care to bc Im not flashing any ROMs until NVflash works on my sbk version
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
this is not a ROM. Its a patch from Asus. Yes, it is cwm flashable.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
carlvk said:
I got the error in the image I tried a couple of options including the microsd.
https://www.sugarsync.com/pf/D7256720_703_699618527
Sorry I cant get the image to show.
Click to expand...
Click to collapse
that is an assert failure. The update isn't happy due to the ROM you're running. if you aren't on a US ROM, it wont update.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
Sharpe351 said:
that is an assert failure. The update isn't happy due to the ROM you're running. if you aren't on a US ROM, it wont update.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
Click to expand...
Click to collapse
Aha, that'll be it I'm on ww.
Thanks for the help.
doesn't work for me (us tf).
sth about asusreader. maybe because i've deleted it and other stock apps...
oifi said:
doesn't work for me (us tf).
sth about asusreader. maybe because i've deleted it and other stock apps...
Click to expand...
Click to collapse
you need to be running a full ROM as stated in the OP.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
Thank You
Sharpe thank you for this zip. I have a US B80 and the stupid update would start to install and then after getting about a 1/4 of the way it would freeze on the android with the exclamation point. Your zip solved that problem and so far no reboots or any weirdness. I do have one question about the update though, how do I stop the tablet from trying to take the OTA(it is persistent).
Thanks
More info and source credits here, thanks to codeworkx https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB.
ATTENTION:
We've contacted Samsung about the problem where performing a mmc erase could hardbrick your phone (i9100, i9100g, n7000, m250 - MAG4FA, VYL00M, and KYL00M with firmware revision 0x19 // T989 and I727 with fw rev 0x12) if it's having a faulty emmc chip.
Read this thread for more informations about it: http://forum.xda-developers.com/showthread.php?t=1644364
They're working as hard as possible on a clean solution which will be ready soon.
Please be patient and try to not flash any leaked kernels or kernels based on sources where MMC_CAP_ERASE is present.
This app http://forum.xda-developers.com/showpost.php?p=27014974&postcount=1 can be used to identify if your phone is affected or not.
CM9 kernels are safe to flash.
Please share!
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Click to expand...
Click to collapse
New Clarifications by Entropy : http://forum.xda-developers.com/showpost.php?p=28416723&postcount=403 - Must Read.
To check whether your phone has the brick bug, download the Got Brickbug app from Chainfire: http://forum.xda-developers.com/showthread.php?t=1693704
Also do read the article on xda for more info.: http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
Nice!
That is a really good news after some time.
Sent from my GT-N7000 using Tapatalk 2
Good news!
Looking forward to see how Samsung solve this nightmare
Sent from my GT-N7000 using xda premium
How many time to fix this Samsung BUG? How maby people need ti brick our 600€? If samsung knows why no first before? Grrrrr...
All hard work its from XDA devs!!!! Thank you devs!!
Enviado desde mi GT-N7000 usando Tapatalk 2
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
nandihno said:
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Teamhacksung dev codeworkx been in touch with Sammy guys so its genuine news...check link in op
Sent from my GT-N7000 using xda premium
at least we now have some hope...hopefully...
So to be clear...
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
ripnetuk said:
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
Click to expand...
Click to collapse
Flashing is not the problem but wiping is
So if they release a new update then simply don't wipe on your ics but wipe only after you install the new update
If however you want to be extra careful like I am
Flash a gb rom via odin then wipe that then flash said ics update via Odin
Sent from my iPad using Tapatalk
While there have been brickage reports using either PC Odin or CWM, there have been none regarding Odin Mobile Pro. So, when I flashed back GB, I used Odin mobile Pro. Everything went smooth.
//troll mode activated
It's just like Microsoft patching windows vista
//troll mode off
This is a true victory for XDA developers!
My deepest respect for all of you guys :thumbup:!!
Are they releasing a fix for brickd phone or a prevention update?
blue_panther9_9 said:
Are they releasing a fix for brickd phone or a prevention update?
Click to expand...
Click to collapse
Prevention.
Sent from my GT-N7000 using xda premium
I really hope this mess will soon be over. Let's hope while they are resolving the brick bug they also take a look at the wakelock thing. Contrary to others I have encountered this problem very rarely (1 time so far). Nonetheless it would be nice to see a solution.
Sent from my Galaxy Note running ICS
Good news but given that we haven't seen ics roll out in all countries, who knows when this will get fixed.
Another thing that bugs me. Is there possibility that Samsung push the solution for this bug and carriers just ignore it and continue with pushing the infected ics?
I guess that all we need is just one good release and everyone can flash it.
Hope to see it soon.
Sent from my Samsung Galaxy Note using XDA app
ripnetuk said:
Can someone confirm the following is correct please?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
Click to expand...
Click to collapse
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
ashoksoft said:
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
Click to expand...
Click to collapse
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Just updated op too
This is great news! Many thanks to entropy and chasmodo and all who've worked on this and sacrificed for us!
Also thanls to those who took it seriously.
Sent from my GT-N7000 using xda premium
I was dumb and flashed a custom rom for GT-N8000, it works however i have some exchange sync issues so want to revert back. I know some cusotom roms for this device will appear soon, but short term does anyone have the odin restore files I could use to get back to stock?
Use the root injected stock version from here:
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1/
Sent from my GT-N8013 using XDA Premium HD app
I already put an N8013 stock kernel/recovery dump somewhere in one of the threads.
At some point I'll work on a complete RTS package - param, recovery, kernel, system.
Entropy512 said:
I already put an N8013 stock kernel/recovery dump somewhere in one of the threads.
At some point I'll work on a complete RTS package - param, recovery, kernel, system.
Click to expand...
Click to collapse
Did u ever end up making the n8013 return to stock page you spoke of a couple years ago, I havent found one yet haha. Thank u
Thanks for the stock rom.
I was going to put this in the JB thread, but that has apparently been locked due to flaming.
As mentioned in other threads on the eMMC "brickbug", Samsung's official patch for this issue is NOT to remove MMC_CAP_ERASE, but to only disable secure erase in the kernel.
See: https://patchwork.kernel.org/patch/1383661/
Now, we've been highly disappointed that Samsung hasn't included this patch in many updates for a variety of devices. However, on analyzing the kernel, it appears it *might* be safe due to having Samsung's official patch.
If you unpack the kernel, and then run "strings" on the unpacked image, you will see the following:
Code:
M8G2FA
MAG4FA
MBG8FA
MCGAFA
VAL00M
VYL00M
KYL00M
VZL00M
e.g. the exact list from the above patch, in the correct order.
So it looks like the XXLS1 JB leak is *probably* safe from the Brickbug - unless Samsung is wrong about nonsecure erase being safe.
+1
Good news for Note Community
I agree..... thanks for taking the time to share your findings with us.
:good:
Good to see some improvements from Samsung! Thanks a lot Entropy.. without your precious help this wouldn't be possible
Many thanks Entropy..
So now we can do full wipe without any fear...??
Sent from my GT-N7000 using xda app-developers app
Brilliant..thanks mate!
Sent from my GT-N7000 using xda premium
thanks for the update.
Its great to see people like you care for the rest
Entropy512 said:
I was going to put this in the JB thread, but that has apparently been locked due to flaming.
As mentioned in other threads on the eMMC "brickbug", Samsung's official patch for this issue is NOT to remove MMC_CAP_ERASE, but to only disable secure erase in the kernel.
See: https://patchwork.kernel.org/patch/1383661/
Now, we've been highly disappointed that Samsung hasn't included this patch in many updates for a variety of devices. However, on analyzing the kernel, it appears it *might* be safe due to having Samsung's official patch.
If you unpack the kernel, and then run "strings" on the unpacked image, you will see the following:
Code:
M8G2FA
MAG4FA
MBG8FA
MCGAFA
VAL00M
VYL00M
KYL00M
VZL00M
e.g. the exact list from the above patch, in the correct order.
So it looks like the XXLS1 JB leak is *probably* safe from the Brickbug - unless Samsung is wrong about nonsecure erase being safe.
Click to expand...
Click to collapse
Well, well.
Samsung finally at last!
Thanks Entropy for the good find.
Lets hope Samsung did a good job !
Now to download that leak.......
I am still wondering about the update. If we have the brick bug in ics how are we able to flash ota jelly bean?? Wont there be chances of bricking while updating our phone to jb.
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
I am still wondering about the update. If we have the brick bug in ics how are we able to flash ota jelly bean?? Wont there be chances of bricking while updating our phone to jb.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
The usual applies... Flashing anything via Odin is safe. Flashing anything from a safe kernel is safe. Flashing something with a "safe" update-binary should be safe even on a dangerous kernel.
I'm not going to guarantee the safety of the XXLS1 kernel, as it's hard to guarantee that it is doing what we think it is, but it is PROBABLY safe as opposed to definitively dangerous like any previous official ICS kernel binary. We won't know unless people take risks unfortunately...
ok using the jb rom i did indeed soft brick has taken 5 hrs to get my note working, i had a custom rooted 404 rom on with hydracore install the jb with cwm and that was it stuck on samsung logo ,so i then tried to flash stock 404 with pc odin and was stuck on flashing fs image,finally got it working with the pit method and by updating bootloader and clear efs, this has kinda scared me as after a cple hrs trying that it would be sent to repair
be aware this worked for me it may not for anyone else
[/COLOR]
anubis1126 said:
ok using the jb rom i did indeed soft brick has taken 5 hrs to get my note working, i had a custom rooted 404 rom on with hydracore install the jb with cwm and that was it stuck on samsung logo ,so i then tried to flash stock 404 with pc odin and was stuck on flashing fs image,finally got it working with the pit method and by updating bootloader and clear efs, this has kinda scared me as after a cple hrs trying that it would be sent to repair
be aware this worked for me it may not for anyone else
Click to expand...
Click to collapse
I was going to write a sarcastic post but... that sucks
This means the Samsung work around did not work.
Either that or you might have repartitioned for no reason.
Did you try a nandroid restore first?
anubis1126 said:
ok using the jb rom i did indeed soft brick has taken 5 hrs to get my note working, i had a custom rooted 404 rom on with hydracore install the jb with cwm and that was it stuck on samsung logo ,so i then tried to flash stock 404 with pc odin and was stuck on flashing factoryfs....
Click to expand...
Click to collapse
So you bricked bricked flashing on Hydracore? I thought that was safe!
shoey63 said:
So you bricked bricked flashing on Hydracore? I thought that was safe!
Click to expand...
Click to collapse
He already flashed the jb leak, overwriting hc with its own kernel in the process. Flashing back to 4.0.4 on the leaked rom caused the soft brick, NOT hc.
Sent from my Asylumized shopping cart.
randomtext said:
He already flashed the jb leak, overwriting hc with its own kernel in the process. Flashing back to 4.0.4 on the leaked rom caused the soft brick, NOT hc.
Sent from my Asylumized shopping cart.
Click to expand...
Click to collapse
He used PC Odin to "flash back". I thought that was safe too!
Anyway odin stuck on factoryfs and needing PIT file method to revive Note is SUPERBRICK, not "softbrick"
Entropy512 said:
The usual applies... Flashing anything via Odin is safe. Flashing anything from a safe kernel is safe. Flashing something with a "safe" update-binary should be safe even on a dangerous kernel.
I'm not going to guarantee the safety of the XXLS1 kernel, as it's hard to guarantee that it is doing what we think it is, but it is PROBABLY safe as opposed to definitively dangerous like any previous official ICS kernel binary. We won't know unless people take risks unfortunately...
Click to expand...
Click to collapse
I've tried it a dozen times and seems to be ok
Ran the check and lost no memory at al
Thanks would be nice for my daring? Stupidity ? Did full wipes etc
Sent from my GT-N7000 using Tapatalk 2
howard bamber said:
I've tried it a dozen times and seems to be ok
Ran the check and lost no memory at al
Thanks would be nice for my daring? Stupidity ? Did full wipes etc
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Actually it's the same as wiping on stock ICS recovery. Well done for trying to verify :thumbup:
what can i say i am a flashaholic flash at least once a week trying varied roms themes etc this time it just happened to me
redone pit file and gained a bit more space
anubis1126 said:
what can i say i am a flashaholic flash at least once a week trying varied roms themes etc this time it just happened to me
redone pit file and gained a bit more space
Click to expand...
Click to collapse
Happened to me too useing stupid Cwm.zip - accidentally hit factory reset and BANG! Superbrick! Thankfully grey retailer replaced it.:thumbup:
Sent from my GT-N7000 using xda app-developers app
HI guys, I'd like to post this here. Here is the latest Odin flash update I pulled from Kies and my device the other day. This is as new as it gets for Samsung Galaxy Camera. You will need Odin3 and the following files
PIT: http://d-h.st/3B3
CSC: http://d-h.st/AVe
MODEM: http://d-h.st/Nbl
PDA: http://d-h.st/U7K
Not much more to say, Hope this gets someone out of a sticky situation.
I wonder if they'll ever remember they made this device and give us another update, not necessarily a version upgrade, but give it some extra functions in the camera app.
Sent from my SM-N9005 using Tapatalk
Adam, many guys paid for the toolkit. We realize you're busy with many projects, but we have no one else to go to to get a sound recovery zip for our cameras. I'm just asking you in a professional manner for your assistance.
JAG50
Sent from my SPH-L710 using Tapatalk
JAG50 said:
Adam, many guys paid for the toolkit. We realize you're busy with many projects, but we have no one else to go to to get a sound recovery zip for our cameras. I'm just asking you in a professional manner for your assistance.
JAG50
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I'm sorry, I don't understand. What do you want? You want me to whip up a CASUAL recovery installer? Or what kind of recovery.zip are you looking for? Generally you install .zips from a recovery, I wouldn't be making a ROM for the camera, but I can help to make it easier to install ROMs.
JAG50 said:
Adam, many guys paid for the toolkit. We realize you're busy with many projects, but we have no one else to go to to get a sound recovery zip for our cameras. I'm just asking you in a professional manner for your assistance.
JAG50
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
This device has received the same support as the Galaxy Note 2. So, if you read about something for GNote2, you will likely see it on this device too.
Thanks for reply. No, I'm not interested in installing ROMs. Just a standard CWR that would allow me to install zipped scripts and stuff to tweak camera. I.E. crossbreeder, etc. I installed recovery on my note 8 and added some scripts to make it run smoother and conserve battery. I've seen some recoveries out there, but there are questionable, but you have established yourself as a serious developer. That's why I asked.
Sent from my SPH-L710 using Tapatalk
does those files fit on gc-110 ?
podcast236 said:
does those files fit on gc-110 ?
Click to expand...
Click to collapse
no. this is for GC100 only.
GC-120
Adam,
I have a GC120 that was rooted and working fine. However not realizing that the bootloader was still locked I flashed a custom rom with mobile odin and did not make a back up prior to doing that. Now it boots directly to Download mode and I can not get it to boot to recovery. I can not find the stock firmware anywhere to try to flash through odin. I was going to try the unbrickable mod but I dont know if I feel comfortable taking the thing apart. Ive tried flashing the OTA updates for the device and still nothing. Any suggestions on how I can get this to work again ?
Any help would be appreciated.
Thank you.
those files still available or no?
Adam... a year ago i downloaded your files and keep it in my harddrive, but last week when i want to use it again, the files corrupted... i can't understand why because i used the same files for 2 times before.
Last night i tried to download your files again... but keep on failing.. my connection really good because i can download 1080 (-+ 1gb) movie everytime. So your files still available to download no? So