Installing GB ROM - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Is it common to take about 25 minutes and still not be able to complete the installation of GB Rom using PC Odin..?
I am trying to install KL3_KL1 GB Rom and the PC Odin is stuck at Factory fs for 25 mins ...
unplugged the cable, removed the battery and restarted the process .. still the same no matter what I do...
I am at the moment following steps form dr.Ketan's threads.. but the process seems to take a little too long and am unable to get into recovery mode.. Its only download mode and never going past the factoryfs.img situation in PC Odin..
I was on Stock ICS ROM Indian version before i started the process with PC Odin.
My goal is to get into Criskelo ROM for now.
Any help of suggestions to get me out of the situation please..

Have you ever did factory reset or wipe on stock ICS?
this is bad sign, and highly suggestive of super brick emmc bug. if you cnfirm wiping on stock ICS then it must be that only.

sob sob ... may be i did ...
should i just handover my phone to Samsung service center now ??

Yes, just check your flash counter is zero
Sent from my GT-N7000 using xda premium

yep.. That one is set to Zero.. Will Samsung just re-install software or replace device in this case ?
I have a nandroid backup taken 2 days back. Can i use that backup on the new phone to get back all my settings ??I primarily need contacts that i do not want to loose.

I believe it's a Motherboard replacement that you will be given, I doubt there will be anything you can pull from the old phone..

I luckily copied the nandroid backup onto my PC along with the md5 checksum... Would that help me ?
what is the process to restore from Nandroid backup
Recovery --> restore --> show the target ? is that it ?

Coolkriss said:
I luckily copied the nandroid backup onto my PC along with the md5 checksum... Would that help me ?
what is the process to restore from Nandroid backup
Recovery --> restore --> show the target ? is that it ?
Click to expand...
Click to collapse
No, never try it. You wont be able to restore anything. Just send to repair center and have a new mobo replacement if still under warranty.
Then after get your devices back and check again how to do nand restore. ( please read or ask before do any nand restore).
Good luck, mate.
Sent from my GT-N7000 using xda premium

As per above post - just wait until they send the device back repaired -
In the meantime read, read, read on how to go about these things otherwise you risk another brick..
To be honest, I'd just start a fresh when the new phone comes back..

Thanks guys .. Thanks for all the prompt responses. I just hope they dont take long time to get me the repaired or new phone.
I will just let my gmail account do the sync.

CJSlim79 said:
As per above post - just wait until they send the device back repaired -
In the meantime read, read, read on how to go about these things otherwise you risk another brick..
To be honest, I'd just start a fresh when the new phone comes back..
Click to expand...
Click to collapse
You are right, actually i do believe for those who get bricked with their devices must be a experienced flasher. Those of them ( included myself) surely only read how to unroot the new devices but never read other thread such as ...how to ugrade rom...general section...problem.....
But i think after these brickbug dilemma, a lot of xda member like me and you sure will read ...read and read the whole forum before do any rooting and flashing no matter jump to which brand of devices......
Sent from my GT-N7000 using xda premium

Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium

dr.ketan said:
Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
You're right mate, If the instructions are followed then I can't recall a single issue..
I've used your instructions (after extensive reading) and also had a lot of support from azzledazzle (Who was kind enough to walk me through my first downgrade).
I've had Android for a few years now since ditching the iPhone's and on HTC I used to flash anything and everything and just nandroid if anything went wrong. I think the issue here is that there is an issue, a bug with the eMMC, and people don't bother to research their NEW device, they approach with "I've flashed Android before" attitiude and this is where we end up...
It took me a while, and as I say alot of research before i started dabbling with the Note.... And as I am sure AD will confirm, I asked every n00b question under the sun of him about the process.. Yeah, I was a n00b and I am still learning... I asked the questions, nobody laughed and my Note is still purring...
I guess people either don't wanna feel stupid by asking (Old saying: No such thing as a stupid question!) or they are confident they "Know" how to do it because they have done so on other Android devices...
The guys on this forum are a wealth of knowledge and maybe it's just me, But I like to learn...
Hopefully, I maintain my head and don't mess it up in the near future and I am considering testing NoteCore V7 STD... but still not comfortable with the cleaning scripts etc - So i will read more, ask more and learn more... and hopefully continue to use my Note .. more...

dr.ketan said:
Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I know and this was perfectly my mistake ..
I have flashed a lot of times and i actually remember know about the eMMC bug.. the only thing is that i did not check if i had that bug ..
Situation for me today.. I started the process and got an email that i had to respond immediately from my office..
In this process, I forgot if i did a reboot into recovery after flashing the Abyss Kernal .. that is when i just went ahead with the wipe cache/dalvik and data ...
This was my lazy A$$ to blame ..
but for anyone doing a flashing .. please concentrate on what you are doing and just dont rush ahead ...
and ofcourse read, read & read before you proceed with any steps...

Coolkriss said:
I know and this was perfectly my mistake ..
I have flashed a lot of times and i actually remember know about the eMMC bug.. the only thing is that i did not check if i had that bug ..
Situation for me today.. I started the process and got an email that i had to respond immediately from my office..
In this process, I forgot if i did a reboot into recovery after flashing the Abyss Kernal .. that is when i just went ahead with the wipe cache/dalvik and data ...
This was my lazy A$$ to blame ..
but for anyone doing a flashing .. please concentrate on what you are doing and just dont rush ahead ...
and ofcourse read, read & read before you proceed with any steps...
Click to expand...
Click to collapse
I'm on a wing and a prayer at the mo as before i did any modding i was helping my bro (who lives in another country) and was talking him through it - jumped into Stock recovery and hit wipe cache by mistake...
It can and does happen but I am very diligent now and I've flashed a a good few ROM's and a good few stock recoveries since then so I hope i got away with that stupid mistake...maybe it's the wipe data only that brings forth "The Brick"

Yes..
anyway. I gave my Note to the SSC today .. IT was strange that they said .. DO NOT DO OTA .. you have to come to SSC for any software upgrade.
They initially told me that this is out of warrenty as I did OTA and showed them who the BOSS was .. Instantly they changed the tone and now they say we will do it for now, but the next time bring it to SSC for upgrades ..
They asked me to visit them tomorrow to collect the unit, but i doubt if they can change the Motherboard by tomorrow. Hoping they will..
Will keep you all posted on the status
Thanks a lot for all your guidance guys ...I would not have loved my Note so much if I was not on XDA

Now this has gone bad.. the SSC tells me that the software upgrade is not covered under warranty and is asking me to take back my phone .. They are not ready to repair it ..
Help me here guys ... anyone aware of something that i can scare them with ??

Coolkriss said:
Now this has gone bad.. the SSC tells me that the software upgrade is not covered under warranty and is asking me to take back my phone .. They are not ready to repair it ..
Help me here guys ... anyone aware of something that i can scare them with ??
Click to expand...
Click to collapse
You can advise them of many many instances of this brickbug and provide evidences FROM SAMSUNG confirming that exists and acknowledging that this can be triggered by a simple update / large data move or copy.
This is standard practice for Service Centres, unfortunately they always try to get out of it.. Stand your ground, keep your head and you will be given a repaired / replaced device..
Oh - and answer any questions straightforward - Yes / No, Do not offer information.
Did you root / flash / play around - No
How did this happen - Via KIES
etc
Again - This can be triggered via a standard Factory reset / Wipe from within Settings > Factory Reset on ALL stock ICS kernels...
A little research on these forums will give you enough info...
Good luck
---------- Post added at 02:35 PM ---------- Previous post was at 02:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=1633938

Thanks a lot for the advice.. I am searching if I can find any official Samsung statement anywhere to get this resolved.
I called the head of SCC in my city and spoke to him today. He will check with the center and give me a call tomorrow..
Am just hoping this gets resolved... aaargh ...

Coolkriss said:
Thanks a lot for the advice.. I am searching if I can find any official Samsung statement anywhere to get this resolved.
I called the head of SCC in my city and spoke to him today. He will check with the center and give me a call tomorrow..
Am just hoping this gets resolved... aaargh ...
Click to expand...
Click to collapse
Check the thread I posted..
There's a few Dev's here been in touch with SS over this issue since it was realised and I'm pretty sure you've all you need to basically tell them to replace it, No, Demand it...
Even under the Sale of Goods act - the device should be fit for purpose it is sold for.
Given that even on STOCK Firmware you can brick this device without rooting / modding AT ALL.. indicates this statement is not met. The device has a highly publicised and highly know firmware issue and Samsung were stupid enough to release a software modification (Which they encourage you to download via THEIR software) which enables you, without knowledge to destroy your phone..
It's your fault as you know that it happened (As we know from this forum and more the safe way)
But it is THEIR problem that they have the issue.. Do not take no for an answer, And to be honest - I would have refused to wait for the callback.. I would have advised (As I have previously) that I will hold on the line while they contact whoever they need to because you are eager for resolution of this.
You will get a new/repaired device...

Related

Why ODIN? WHY?!

It's driving me nuts, and I would like someone to help me understand. I came here with a bricked and completely unrepairable phone, and I have since managed to get a new Note. The completely stubborn side of me went right away flashing ICS ROMS...Okay, that's all good and well...No harm done anyway. But why don't developers include the "base" and root kernel files in their frickin' ROMS?! It's incredibly annoying. Why do I have to go into "ODIN" and download mode to flash some repack, wipe wipe wipe, reboot, flash another base, wipe wipe wipe, reboot, and finally flash a "custom" ROM. I should be able to flash a single .zip file through CWM and be down with it. I'm not bad talking at all, and I greatly appreciate what developers do around here.
For example, MIDNOTE includes ICS kernel and base...one integrated file. EVERYTHING works, and I have full root access. I'm wondering what it will be like when Samsung comes out with an official ICS version, will I have to flash ten different files to use a custom ROM or will developers be able to integrate it into their work? Just a question...not meant to cause trouble in the least...it just erks me the wrong way. And I'm sure others are wondering the same too.
They does it because you dont need to get those annoying yellow triangle and increase those custom binary counters....Would you like having triangles and increase counters?And the ICS roms are too early releases and are still in beta stages.So you need to go with the process.GB roms dont have these problems and are less hectic.Thats why I still stay in GB.Custom ICS roms will be ok when Official ICS is released.
@smalmagal
you are aboulutely right...
its a shame that they dont make it even easier to flash...
i mean please, the only thing that they are doing is:
- Prepare a Rom from scratch
- Provide updates
- Try to fix bugs
- And that in their free time for free
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Pleaseeee mate...
Not everyone is a dev here but at least we should be able to flash a rom...
Cooking takes days and week, flashing in WORST case 1 hour...
Bulut.O said:
@smalmagal
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Click to expand...
Click to collapse
Made my day!!! LOL !! could you please add
d-
e-
f-
ha ha ha ha ha ha hah!!
Bulut.O said:
@smalmagal
you are aboulutely right...
its a shame that they dont make it even easier to flash...
i mean please, the only thing that they are doing is:
- Prepare a Rom from scratch
- Provide updates
- Try to fix bugs
- And that in their free time for free
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Pleaseeee mate...
Not everyone is a dev here but at least we should be able to flash a rom...
Cooking takes days and week, flashing in WORST case 1 hour...
Click to expand...
Click to collapse
Are you serious???????Do you think rom flashing is like installing your favorite app???As I said when Stock ICS is released everything would become easy
Bulut.O said:
@smalmagal
you are aboulutely right...
its a shame that they dont make it even easier to flash...
i mean please, the only thing that they are doing is:
- Prepare a Rom from scratch
- Provide updates
- Try to fix bugs
- And that in their free time for free
why not make a rom that i click on and its installed on my device...
like windows popups...
Click on Link and choose:
a- Save
b- Open
c- Flash to my Phone, make all the settings and text my GF that i love her...
Click to expand...
Click to collapse
vijai2011 said:
Are you serious???????Do you think rom flashing is like installing your favorite app???As I said when Stock ICS is released everything would become easy
Click to expand...
Click to collapse
@vijai2011 you completely missed the point!! Didn't you??
The things said by @Bulut.O is called SARCASM
Read again!! And this time carefully!!
Peace
I'm serious guys! This is the only device I've ever owned where I have to flash a million different files just to get my phone booting...so I'm just trying to understand what's up. And obviously I LOVE the Note or else I wouldn't have bought two.
Developers do this for free...okay, yeah...but they don't have to do it half-assed? If I was going to sell you a car, I'd probably give it to you one piece. I wouldn't make you take all the parts and put them together yourself only in the end to find out that you're missing the engine and have to start all over again. And honestly, that's how I feel around here sometimes.
And the comment about Windows is out of line. I don't use Windows...why does everyone assume Windows? Honestly don't know why more don't use Linux around here. Windows just plan ol' sucks.
Edit: Custom ROMS aren't build from "scratch" by the way...and not everyone around here who posts a ROM is a "developer."
This issue is not because of lazy developers. It is because Samsung is tired of replacing devices under warranty when the terms of said warranty have been broken, and as a result putting extra security measures in place.
Lazy developers would let you get the yellow triangle, and then let you foot the bill for your mistakes while flashing.
beestee said:
This issue is not because of lazy developers. It is because Samsung is tired of replacing devices under warranty when the terms of said warranty have been broken, and as a result putting extra security measures in place.
Lazy developers would let you get the yellow triangle, and then let you foot the bill for your mistakes while flashing.
Click to expand...
Click to collapse
Huh? I'm talking about doing everything from CWM...not from ODIN. So no yellow triangle...and as far as I know, every custom ROM around here is a CWM flashable .zip file...minus the oh so coveted ICS repack...which needs ODIN for some unknown reason to me. So now, I'm not calling myself lazy, or the developers around here for that matter. There's a good reason, I know it...I want to find out. Samsung is a different beast for sure, and this is the first Samsung device I've owned, and I'm trying to avoid bricking again, so I'd like to learn all the procedures and such...and why they're necessary. It's for my piece of mind really.
smalmagal said:
Huh? I'm talking about doing everything from CWM...not from ODIN. So no yellow triangle...and as far as I know, every custom ROM around here is a CWM flashable .zip file...minus the oh so coveted ICS repack...which needs ODIN for some unknown reason to me. So now, I'm not calling myself lazy, or the developers around here for that matter. There's a good reason, I know it...I want to find out. Samsung is a different beast for sure, and this is the first Samsung device I've owned, and I'm trying to avoid bricking again, so I'd like to learn all the procedures and such...and why they're necessary. It's for my piece of mind really.
Click to expand...
Click to collapse
You just answered your own question. The process is long and somewhat complicated because it HAS to be done via recovery. If it were done via download mode in ODIN, it would be much simpler; but it would trip the counter. Using recovery instead of download mode sidesteps this problem, but it introduces others. That is why flashing to/from ICS/GB via recovery is so complicated.
Sent from my GT-N7000 using xda premium
I appreciate you bleeding edge types, but this is why I wait a few weeks AFTER an official rom is released, before I even consider a custom rom.
ICS is still an infant...I'd rather have one that was at least able to drive a car before I install it.
geo.samuel said:
@vijai2011 you completely missed the point!! Didn't you??
The things said by @Bulut.O is called SARCASM
Read again!! And this time carefully!!
Peace
Click to expand...
Click to collapse
Lol....Ok.understood it now.Now generally as said in above post,lazy developers would let you get triangles and increase custom binaries.So they need to make multiple files which makes your phone ready for flashing your favorite firmware.If you probably own a galaxy s series you would know how easy it was to flash firmwares.Thats because sammy did not implement any security measures which Gnote has.Hope you understand
smalmagal said:
every custom ROM around here is a CWM flashable .zip file...minus the oh so coveted ICS repack...which needs ODIN for some unknown reason to me.
Click to expand...
Click to collapse
It's because of the kernel and root. Unlike GB kernels, this one seems to be a bit wonky, and your root permissions get lost easily in CWMR flashing or Nand restoring. Hence the convoluted flashing procedures. Lack of code sources, I suppose.
All of us have to accept this if we want a taste of Roms based on the Chinese leak. No-one is happy with the current state of the affairs, but we manage.
Nobody is forcing you to deal with it. If you can't, stick with GB Roms until the final version of ICS drops.
I have flashed several ICS Roms and only flashed the chainfire repack the very first time when I moved to ICS from gingerbread. I have flashed Criskelo, rocket and midnote just from CWM. Never had a triangle, SOD etc...just full wipe before I flashed and then cleared caches after.

[Q] Super Bricked Gnote Revived But Lost Memory

Hello Dear friends,
This is Alvina Snow, a nooby nooby noob girl, who once liked to play with phones and would make fun of her buddies, carrying the stereo-typed GB versions on thier Note. I am no more interested in flashing Roms and not because i blame developers. They have always been great in thier job and i owe them for their coolest roms, but i blame myself and my hastiness in everything. Cutting the crap, let me come to the point.....
Last night, tired of the mediocre looks of Official ICS, i downloaded Paranoid Android 0.4a along with goodies and following the instructions, I opened Odin to downgrade to GB so i can install PA 0.4a safely. To my surprise, once the GB Rom installed successfully, it got stuck at bootloader, i rebooted it a few times, then i went to recovery and reset factory/ format, wiped cache and rebooted. Note stuck this time on the first screen. :fingers-crossed:
Presuming that Odin install may have been faulty, i redid the Odin method and this time, the install stuck at "factoryfs.rfs". From then on, i tried for hours to make it happen, swapped roms, used kernels, wiped everything... and ultimately i got a nice super brick on my hands. the notorious mobile-cum-triangle-cum-PC sign, asking me to use recovery through kies.
researched XDA all night and finally landed on Dr. Forest's "Easy guide for repartition workaround to fix super-brick Note"
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Did everything as directed. I used "standard 16 GB pit" and stable GB rom to resurrect my Note and we both came to life to my surprise, only to discover that now i have an 8.24 GB emmc space available, instead of previously held 11.4 GB something. :victory:
I have been praying for Dr. Forest and all esteemed developers and i will always be thankful to them. My questions to my learned seniors is that:-
- Is there any method, adopting which the missing 3 GB should be regained?
- Will I ever be able to regain the missing 3GB space?
- Having this notion in mind that now i have caged 3 GB of voracious malfunctioning space in my emmc, should i expect any further stability issues after revival of Note or it should work just fine.
Once again hats off to Dr. Forest and all other developers for thier compassionate assistance for us noobs. My thanks in advance for help. :angel:
-
alvinasnow said:
Hello Dear friends,
This is Alvina Snow, a nooby nooby noob girl, who once liked to play with phones and would make fun of her buddies, carrying the stereo-typed GB versions on thier Note.
Did everything as directed. I used "standard 16 GB pit" and stable GB rom to resurrect my Note and we both came to life to my surprise, only to discover that now i have an 8.24 GB emmc space available, instead of previously held 11.4 GB something. :victory:
I have been praying for Dr. Forest and all esteemed developers and i will always be thankful to them. My questions to my learned seniors is that:-
- Is there any method, adopting which the missing 3 GB should be regained?
- Will I ever be able to regain the missing 3GB space?
- Having this notion in mind that now i have caged 3 GB of voracious malfunctioning space in my emmc, should i expect any further stability issues after revival of Note or it should work just fine.
Once again hats off to Dr. Forest and all other developers for thier compassionate assistance for us noobs. My thanks in advance for help. :angel:
-
Click to expand...
Click to collapse
Thanks for the kind words which is a lovely reward to the people who contribute time and knowledge to the guides to help revive brick G-Note, including me :victory:!
I will try to answer some of the questions:
1- So far there has not been a known method to fix the faulty areas in the partition caused by the buggy ICS kernel yet. There seem to be some encouraging news from some senior developers who are in contact with Samsung developers and it is hope that there may be a Jtag method release. If the method is available then your device can also benefit from it since the re-partition is fully reversible. Let's just hope they can make it.
2- Will the phone be stable or not: for most people it seems to work well and stable. For some people who have a large damaged areas of space in former sdcard region due to the bug, there seem to be some problem of unstable system. In those cases it is likely that there are still some faulty blocks somewhere in cache or data partitions that has not been eliminated yet.
3- If you are comfortable with using adb method you can try again to explore the lost areas and in some cases can regain 1 or 2 GB of space. There is a free app call "eMMC Brickbug Check" from Gplay which can help to scan the whole chip and report the beginning of faulty blocks. Then you can use parted to make partitions in different areas within the lost range (from 281mb to 3322mb) while try to avoid the faulty blocks.
Hope it helps in some ways. cheers.
Thanx a Ton
Ex expected you came to my rescue and encouragement Sir Forest. . Thanx a million for taking time to answer my queries. I hope that Samsung will soon come up with some remedy. As advised by you, i will also try to use the regain method. Though am not sure
Thank you
forest1971 said:
3- If you are comfortable with using adb method you can try again to explore the lost areas and in some cases can regain 1 or 2 GB of space. There is a free app call "eMMC Brickbug Check" from Gplay which can help to scan the whole chip and report the beginning of faulty blocks. Then you can use parted to make partitions in different areas within the lost range (from 281mb to 3322mb) while try to avoid the faulty blocks.
Click to expand...
Click to collapse
Forest Sir, as you advised i used eMMC Brickbug Check", which says that:
Phone Model: Samsung GT-N7000
eMMC Chip
type: VYLOOM
Date: 03/2012
CID:15010056594c30304d19b9c9013c3fdd
FwRev: 0x19
Brick Bug? : YES. Insane Chip
Now when i check memory.. it started checking and showing something similar to seconds counting and the phone restarted after reaching 671 seconds..
Now pardon my noobness, but i am not clear if how am i gonna get help in determing defected areas out of this.
Help please. God Bless You
alvinasnow said:
Forest Sir, as you advised i used eMMC Brickbug Check", which says that:
Phone Model: Samsung GT-N7000
eMMC Chip
type: VYLOOM
Date: 03/2012
CID:15010056594c30304d19b9c9013c3fdd
FwRev: 0x19
Brick Bug? : YES. Insane Chip
Now when i check memory.. it started checking and showing something similar to seconds counting and the phone restarted after reaching 671 seconds..
Now pardon my noobness, but i am not clear if how am i gonna get help in determing defected areas out of this.
Help please. God Bless You
Click to expand...
Click to collapse
No, not yet all. In this case it does not allow to see where the faulty block is.
If you are confident and like to play again with adb then can explore using parted to create new partitions again in different ranges, with part 9 starting from 1174mb, and then move up by 300mb each time until parted is happy with the new area for part 9. with that approach you will probably save more space.
Otherwise, a external sdcard can also compensate more than all the loss of space in the internal sdcard . cheers.
Thank You Sir Forest for ur guidance. I think its time to get me a 32 GB micro sd
Amen !! I only use my internal SD to hold my Mods and ROMs, all the precious stuff is on the external, Just incase.
Plus i have dropbox and google drive to keep my stuff regularly backed up
azzledazzle said:
Amen !! I only use my internal SD to hold my Mods and ROMs, all the precious stuff is on the external, Just incase.
Plus i have dropbox and google drive to keep my stuff regularly backed up
Click to expand...
Click to collapse
Yea Sir, after getting bricked, I know realize its the best way to handle the unseen
Long Live my Seniors... Owe you people very much.:good:
alvinasnow said:
Thank You Sir Forest for ur guidance. I think its time to get me a 32 GB micro sd
Click to expand...
Click to collapse
If you get that 32GB micro-SD, you can use it as your phone's internal SD card with an easy vold.fstab swap. Your reduced capacity internal storage would then become your "external" SD card.
Sent from my GT-I9300 using XDA Premium HD app
Mister_Mxyzptlk said:
If you get that 32GB micro-SD, you can use it as your phone's internal SD card with an easy vold.fstab swap. Your reduced capacity internal storage would then become your "external" SD card.
Click to expand...
Click to collapse
:victory: Ahaa. Another good news after being delved in miseries for a full day. Let's google the Vold.fstab Swap.
Thank you Mister Mxyzptlk
My Options.
Considering my options, I got few questions in my mind...
a. My Note is International version and purchased from KSA, whereas I am in Pakistan now. So can I claim my warranty here with Samsung Service Centres?
b. If yes, I obviously need to reset my binary counter, which is 4 or 5 at the moment. I also need to restore my Note to stock rom and stock kernel. Is there any safe way except Angelo's kernel and USB Jig to reset binary counter? i was looking for "Triangle Away" in the market, but i somehow couldn't find it.
Help my seniors please. If with your help I can go to Samsung and my warranty is validated, all credits with be to you guys for saving me from big troubles. To be honest I had been a poor kinda girl and managed barely to pull off my Note. I can't afford to manage a board replace night now
Hi: I do not have answers to all questions, but for triangleaway.
you can file a free and paid version of your choice:
http://forum.xda-developers.com/showthread.php?p=22463153#post22463153
https://play.google.com/store/search?q=triangleaway&c=apps
cheers,
Thank You Sir, Forest. Hope this would work
Of you've repartitioned the note that will void your warranty I imagine.
What you really need is an untouched superbrick as Samsung won't be able to tell if it has any hits on the binary counter or if its ever been rooted or custom firmwares flashed...
So brick it again if you are able to claim warranty in Pakistan.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Of you've repartitioned the note that will void your warranty I imagine.
What you really need is an untouched superbrick as Samsung won't be able to tell if it has any hits on the binary counter or if its ever been rooted or custom firmwares flashed...
So brick it again if you are able to claim warranty in Pakistan.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
So, bricking its again seems a potentially dangerous job :fingers-crossed: besides what do you suggest, i should tell Samsung guys, how it happened. Coz i believe they are gonna ask me if how come the phone went dead and i have also learnt that they have ways to check binary count, even if the phone is Superbricked. I am in a fix, coz after investing 500$ on a Note, living without a 3GB phone space is pain in the a*s.
Help please
alvinasnow said:
So, bricking its again seems a potentially dangerous job :fingers-crossed: besides what do you suggest, i should tell Samsung guys, how it happened. Coz i believe they are gonna ask me if how come the phone went dead and i have also learnt that they have ways to check binary count, even if the phone is Superbricked. I am in a fix, coz after investing 500$ on a Note, living without a 3GB phone space is pain in the a*s.
Help please
Click to expand...
Click to collapse
The brick has been acknowledged by samsung, they've admitted it can happen on fully stock uprooted firmware update over kies. That's all you say, you were updating through kies, it failed and you're bricked. They can't check binary count under super brick because it's not possible to enter download mode therefor impossible to get any data or connection off the device. Simple.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
The brick has been acknowledged by samsung, they've admitted it can happen on fully stock uprooted firmware update over kies. That's all you say, you were updating through kies, it failed and you're bricked. They can't check binary count under super brick because it's not possible to enter download mode therefor impossible to get any data or connection off the device. Simple.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Well Dear spyderTracks, it confuses me further to think whether i was superbricked at all? coz i could go to recovery and could also go to download mode. as far as i know, u r super bricked if ur phone does not installs any rom and through odin, the rom installation stucks at factoryfs. please correct me if am wrong.
thanx for ur time.
alvinasnow said:
Well Dear spyderTracks, it confuses me further to think whether i was superbricked at all? coz i could go to recovery and could also go to download mode. as far as i know, u r super bricked if ur phone does not installs any rom and through odin, the rom installation stucks at factoryfs. please correct me if am wrong.
thanx for ur time.
Click to expand...
Click to collapse
No, that's correct. Usually it disables download mode also, my apologies.
Sent from my GT-N7000 using xda premium

Galaxy Mini Brick BootLoader

My phone is bricked by ROM manager. My phone can't boot into recovery mode, downloading mode nor normal phone. The phone charges the battery so there is still hope to fix it. I also have a JIG Usb just incase. if you got any questions you need to ask, please ask. I really want my phone back.
Darth343 said:
I also have a JIG Usb
Click to expand...
Click to collapse
see this video
Can someone answer me - WHY are you using ROM manager when it's known that it kills our Galaxy Mini? Is it really that hard to use Odin, or just flash CWM recovery through the stock one?
Guess some people love to learn it the hard way. You have a unrepairable (at least at home) BRICK!
domcale said:
Can someone answer me - WHY are you using ROM manager when it's known that it kills our Galaxy Mini? Is it really that hard to use Odin, or just flash CWM recovery through the stock one?
Guess some people love to learn it the hard way. You have a unrepairable (at least at home) BRICK!
Click to expand...
Click to collapse
Sorry! Just a thought came to my mind can it b there any solution for this evergreen problem? Like newbies r bricking their phone again & again. ( like warning in stickies) . Just thinking! !! That's all.....
Sent from my GT-S5570 using xda app-developers app
You have no reason to be sorry . It's a great idea to put a warning message about ROM Manager in a sticky. However, i once was a total noob too, and i flashed CWM using Odin, it didn't even came to my mind to use ROM Manager.
Reading a couple of different tutorials and educationg yourself before doing anything is the best possible thing someone can do to prevent situations like this.But, like i said, some people have money to waste
lol ... ROM Manager is screwing up everyones phone. Even my friend's mini bricked. He was unlucky that his warranty had got over. He asked the samsung service center and they told him that it would cost $90 for a new motherboard. He uses his galaxy mini as a paper weight now. Rather buy a new phone than buy a motherboard for $90.
If your phone is under warranty, you can get your phone fixed for free in samsung service center( free new motherboard ). Even I bricked my phone when I was a noob with ROM Manager thankfully my warranty was valid that time.
Although I was able to use ROM Manager with no problems.
domcale said:
You have no reason to be sorry . It's a great idea to put a warning message about ROM Manager in a sticky. However, i once was a total noob too, and i flashed CWM using Odin, it didn't even came to my mind to use ROM Manager.
Reading a couple of different tutorials and educationg yourself before doing anything is the best possible thing someone can do to prevent situations like this.But, like i said, some people have money to waste
Click to expand...
Click to collapse
One real problem is that Rom Manager comes by default on most CM7 based roms. So most new users while experimenting might brick their phone by accident.
TheWhisp said:
Although I was able to use ROM Manager with no problems.
Click to expand...
Click to collapse
You were lucky, I guess
anshul sood said:
One real problem is that Rom Manager comes by default on most CM7 based roms. So most new users while experimenting might brick their phone by accident.
Click to expand...
Click to collapse
I agree, but nobody forces them to experiment with something they have no knowledge of. Phones are not toys to play with (to some extent )
A big warning in the general and development section would be enough.
domcale said:
I agree, but nobody forces them to experiment with something they have no knowledge of. Phones are not toys to play with (to some extent )
A big warning in the general and development section would be enough.
Click to expand...
Click to collapse
Most new users don't browse the stickies, just notice the large no. of redundant and useless threads. They just open the thread pertaining to the rom they want and that's that. It would be nice if each Rom had either the rom manager removed or a warning with the download link itself
never say to anyone that rom manager's brick cannot be recovered in home, it can be
the only step is just press volume down home power button but without panicking, panicking is the main reason of can't able to get into download mode
then just flash with odin, dont think it cannot get into dl mode, dl mode is controlled by bootloader and bootloader is not removed by rom manager
Unsuccesfull flash of bootloader hard-bricks our device, so you can't enter DL mode.
You can always give it a shot with a USB JIG* tho. But in most cases, the only thing that helps is JTAG.
*USB JIG - a 301k resistor between the 4th and 5th pin on the microUSB connector.
Tried that.
I've seen that video like about a thousand times. No luck i even went to a repair men today, he said your phone is dead if it can't go in to recovery menu. Is there any other way i can repair my phone? Sorry for late VERY reply
Yes, either use JTAG or send it to the service center.
Brick caused by rom manager is absolute
Nothing can be done
Sent from my GT-S5570 using xda premium
Me to I used it for making backups, but currently, I'm using cm 10 without ROM Manager.
Same problem with me the board was not responding so Samsung service centre changed my board.
Sent from my GT-S5570 using xda premium
If there isn't really anyway, then i'll just buy a new phone.
Darth343 said:
If there isn't really anyway, then i'll just buy a new phone.
Click to expand...
Click to collapse
Sorry you had to learn it the hard way. When you're new in this world it's easy to 'trust' all CM standard apps. Nevertheless: using CM means you're a root user. Your phone is rooted which means you can seriously damage your phone when you don't know what youre doing. That's exactly the reason why your phone is NOT rooted when you buy it, and your garantee is void when you root it yourself!
Some of these apps provide a warning: with great power comes great responsability!
Nevertheless: the first thing i do when i buy a new Android is rooting it! But a general warning is at place: root apps can damage your phone. Especially those to install roms. Even with a proper CWM you can flash a wrong or faulty Rom. The risk of bricking your phone is always there.
So think twice when you buy a new phone and read all about flashing on XDA!

Need help to Hard Brick my phone

Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium
DeadSp1d3r said:
Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
+10000000 it's so easy
Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?
Gizmotech said:
Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?
Click to expand...
Click to collapse
if you use rom manager samsung will not find out anything
if you flash other devices rom like acei on ace then it might brick but not for 100% sure but there is lots and lots of change that it will brick since it uses other flash scripts and binarys
Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
Just download a galaxy s3 ROM and kernel...bricked right there.
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok Just tried to load up the firmware file for a Ace Plus on odin 4.38 but it wont accept it and comes back with "out of memory" error on the PC screen. Will try Rom Manager.
Bingo! Bricked it. I take it there's no way that I can attempt to revive it? Also I hope there is no traces of CWM Rom Manager, Superuser or Busybox
I don't know about the traces. But the only way to revive it is JTAG or replacement motherboard.
Sent from my GT-S5830 using xda premium
Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..
PulseDroid said:
Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..
Click to expand...
Click to collapse
Or rename a text file to boot.img and flash it as a ROM. This gives a totally faulty ROM.
Sent from my GT-S5830 using xda premium
Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.
Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.
Click to expand...
Click to collapse
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830
Best way to hardbrick your phone is to use rom manager
I got transformed into a potato while writing this post
athe_s said:
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830
Click to expand...
Click to collapse
I do. That's the good thing about having a screen-name
Updates!!!
Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated.
Click to expand...
Click to collapse
Any updates dude?
Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.
This is nice.... You can brick your phone in the last month of you year warranty and get a new phone/motherboard
Once my friends phone switched off suddenly... Non rooted stock
It happened suddenly and also out of warranty
She had to pay 5k to the Samsung people to get it repaired... And the plus point she got 14GB internal memory with the new motherboard
Her phone was the Samsung galaxy S i9000
it would've been done in free if she had warranty
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck
Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
ohh !!!! so easy !!! install rom manager... 100% sure samsung won't find out what went worng with your ace ...
ysrini said:
Any updates dude?
Click to expand...
Click to collapse
Yes, the phone was repaired. They apparently replaced the motherboard.
an0nym0us_ said:
Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.
Click to expand...
Click to collapse
I would have done it quietly if I didn't need the help. Duh! Besides, I doubt this is the reason why they don't honour warranty. I think it is more to do with that they are greedy corporate companies who would rather save at any cost irrespective of whose fault it is. I mean why should they penalise someone because of something someone else done? After all you are all paying customers. They scam people everyday and no one complains. I guess people only complain when it happens to them. You can buy a new phone and have it go faulty within 2 months. Do you think you can get a new phone under warranty from them? No it will be a refurbished one and doesn't mater how much you scream and shout for a new one, they don't care. A neither do I.
jumbobombo said:
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck
Click to expand...
Click to collapse
No, I think it is the same motherboard. What I don't understand is, whether it is the same motherboard they repaired or a replacement one, as this phone was initially locked to the Three network. I had it unlocked. So a new motherboard would have meant that the phone would be locked again. But when I received it back, it would still accept any sims.

Phone stuck in bootloop

I have the model SM-G920T S6, I was attempting to root my phone and must of used the wrong file and now its stuck in bootloop with "Recovery Is Not Seandroid Enforcing" in red in the upper left corner. I've attempted to put it into recovery mode to flash my ROM...which it wouldn't allow me. I'm not quite sure how to fix this issue, I've been trying some videos I've seen on YouTube with no results. Does anyone know the way to fix this?
Use ODIN "Attached below" Flash the Stock ROM: https://www.androidfilehost.com/?fid=24269982086998283
That will get it back to Stock.. Just select AP
Then use odin to flash recovery..
Edit any recovery other than Stock will give you "Recovery Is Not Seandroid Enforcing", anyone with a custom recovery will have the same notification.. If you need further assistance, feel free to PM me..
Also, you asked a very easy question that you could of done on your own time, we all learned the same way..
XDA is not a place where simple questions get answered trust me on that one..
I managed to get it to work last night after a bit of messing around on Odin. Thank you for the help though, I am new to the whole rooting phones, flashing the ROM, etc. Gradually learning but there are a many of things I don't know how to proficiently do.
Tcrazz said:
I managed to get it to work last night after a bit of messing around on Odin. Thank you for the help though, I am new to the whole rooting phones, flashing the ROM, etc. Gradually learning but there are a many of things I don't know how to proficiently do.
Click to expand...
Click to collapse
Flashing is a very dangerous thing to the uninitiated, before attempting to do something that can make your 700 dollar device into a worthless brick..
It is good to read as much as you can, don't rush the process or you will end up here asking a question that no one will answer..
I know because everytime I ask a question that to me appears to be legit, it ends up being ignored..
Now not everyone will ignore, but a good 98 percent will.. XDA is not a Support site, its a development directed at development..
Zaphodspeaks said:
Flashing is a very dangerous thing to the uninitiated, before attempting to do something that can make your 700 dollar device into a worthless brick..
It is good to read as much as you can, don't rush the process or you will end up here asking a question that no one will answer..
I know because everytime I ask a question that to me appears to be legit, it ends up being ignored..
Now not everyone will ignore, but a good 98 percent will.. XDA is not a Support site, its a development directed at development..
Click to expand...
Click to collapse
Are there any sites that you might suggest that would help me learn a bit more. At the moment I have just been trying to root my phone before attempting anything else.

Categories

Resources