Related
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
Full wipe everything just to have a clean gb rom to use afterwards. You don't want to have remains of other roms in there! Just to be sure!
Sent from my GT-N7000 using Tapatalk 2
yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
you can use ODIN to flash stock GB ROM! but there are some reports that even that can cause superbrick! read this:
http://forum.xda-developers.com/showthread.php?t=1653582
you can read this thread how to do it using abyssnote kernel:
http://forum.xda-developers.com/showpost.php?p=24535533&postcount=2
and for some more info read this thread:
http://forum.xda-developers.com/showthread.php?t=1659768
hope this helps and good luck!
btw: I was on i9220ZCLP1 kernel and flashed stock GB ROM with ODIN and everything went fine!
Flash this one for wipe:
http://forum.xda-developers.com/showthread.php?t=1552435
yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
Download pre rooted rom and flash thru pc odin. I came back to gb litening rom twice from lpy and alba 2.1.
This is the way how I downgraded to gb from ics succesfully. It doesn't mean is 100% no risk at all.
Good luck.
Sent from my GT-N7000 using xda premium
i have identical situation , i want to go back to gb via pc odin ( mobile odin pro crashed after choice of any file )
this rom is good for this operation?
3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)
and after gb restored , full wipe? Or the rom itself full wipe?
or maybe wait for new ics?
netoperek said:
i have identical situation , i want to go back to gb via pc odin ( mobile odin pro crashed after choice of any file )
this rom is good for this operation?
3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)
and after gb restored , full wipe? Or the rom itself full wipe?
or maybe wait for new ics?
Click to expand...
Click to collapse
Full wipe with Odin.
Sent from my GT-N7000 using Tapatalk 2
yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
I will give u more detail how I did it thru pc odin.
1) Download pre rooted rom from bodivas thread. After downloaded please unzip it and simply put at your desktop.
2) Backup sms, contact or others stuff ( optional).
3 Boot your devices into download mode.
4) Open pc odin.
5) Connect your devices to pc usb port with mini usb cable
6) After your devices connected with your pc ( if connected you will able to see yellow colour box at the left upper side from your pc odin). Click pda button and choose the rom tar file u hv put at your pc desktop.
7. After choosen the right rom. Wait for 15 second. Then press start.( - DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....)
8) if everything go well, your devices will auto reboot. DONE.
Remarks.
...............
- After rebooted if hv fc prob, pls don't panic. Just pull out the battery and boot into the " stock recovery mode" and do full wipe.
Warning
................
- DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....
Good luck.
Sent from my GT-N7000 using xda premium
lee yun khong said:
I will give u more detail how I did it thru pc odin.
1) Download pre rooted rom from bodivas thread. After downloaded please unzip it and simply put at your desktop.
2) Backup sms, contact or others stuff ( optional).
3 Boot your devices into download mode.
4) Open pc odin.
5) Connect your devices to pc usb port with mini usb cable
6) After your devices connected with your pc ( if connected you will able to see yellow colour box at the left upper side from your pc odin). Click pda button and choose the rom tar file u hv put at your pc desktop.
7. After choosen the right rom. Wait for 15 second. Then press start.( - DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....)
8) if everything go well, your devices will auto reboot. DONE.
Remarks.
...............
- After rebooted if hv fc prob, pls don't panic. Just pull out the battery and boot into the " stock recovery mode" and do full wipe.
Warning
................
- DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....
Good luck.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
____________________________________________________
Thanks for the guide. I have one question. Is there a way to test if my eMMC is ALREADY DAMAGED? I read that if the EMMC is damaged that's the reason that flashing with PC Odin causes superbrick.
yllivia said:
____________________________________________________
Thanks for the guide. I have one question. Is there a way to test if my eMMC is ALREADY DAMAGED? I read that if the EMMC is damaged that's the reason that flashing with PC Odin causes superbrick.
Click to expand...
Click to collapse
Sorry no ideal. But based to the info and the detail you given. The emmc damaged should not exists at your devices. Since you never use the cf-lpy cwm. I'm not the pro..but my opinion could be the common answer.
Sent from my GT-N7000 using xda premium
lee yun khong said:
Sorry no ideal. But based to the info and the detail you given. The emmc damaged should not exists at your devices. Since you never use the cf-lpy cwm. I'm not the pro..but my opinion could be the common answer.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
+1
No way you have emmc!
Sent from my GT-N7000 using Tapatalk 2
rom from this thread ?:
http://forum.xda-developers.com/showthread.php?t=1535025
and use only one file no 3?
netoperek said:
rom from this thread ?:
http://forum.xda-developers.com/showthread.php?t=1535025
and use only one file no 3?
Click to expand...
Click to collapse
I think you have to flash 3 files.
Sent from my GT-N7000 using Tapatalk 2
netoperek said:
i have identical situation , i want to go back to gb via pc odin ( mobile odin pro crashed after choice of any file )
this rom is good for this operation?
3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)
and after gb restored , full wipe? Or the rom itself full wipe?
or maybe wait for new ics?
Click to expand...
Click to collapse
If you feel panic with the bricked problem might appear while flashing back to gb. Please don't try ..it was horrible...your heartbeat sure will keep increase fast and faster...believe me..I hv tried twice....
If you feel comfort with the current ics and without any major bug, just keep using it and enjoy while the dev looking for the solution and waiting for kernel sources code realease.
Just keep in mind DUN USE THE CWM.
OR YOU CAN USE TITANIUM BACKUP AND FREEZE THE CWM FOR ANY ACCIDENTALY WRONG PRESS.
Sent from my GT-N7000 using xda premium
Thanks lee
everything working on my note, no significant bugs
so i thing i stay on ics (for the moment), my heart is delicate
Help please. This is the history of my flashing btw...
I had a rooted Gingerbread with CF root kernel KKA. When ICS came out i rushed and Flashed a cf root lpy zimage (kernel only) via Recovery ( i know it was stupid.. ) So i got stuck and i could only come up to CWM. I used the CWM to BACK UP MY DATA (this was before i even flashed the ICS rom). From there i used PC odin to flash kka gingerbread rom. Flashed it without problem. Then i flashed ICS LPY rom together with LPY kernel via Mobile Odin and i clicked wipe data. Everything went well. I haven't used CWM. Now i am affraid that i could have bad EMMC. Should i stay on ICS or should i flash stock GB rom again?
starnoise said:
Help please. This is the history of my flashing btw...
I had a rooted Gingerbread with CF root kernel KKA. When ICS came out i rushed and Flashed a cf root lpy zimage (kernel only) via Recovery ( i know it was stupid.. ) So i got stuck and i could only come up to CWM. I used the CWM to BACK UP MY DATA (this was before i even flashed the ICS rom). From there i used PC odin to flash kka gingerbread rom. Flashed it without problem. Then i flashed ICS LPY rom together with LPY kernel via Mobile Odin and i clicked wipe data. Everything went well. I haven't used CWM. Now i am affraid that i could have bad EMMC. Should i stay on ICS or should i flash stock GB rom again?
Click to expand...
Click to collapse
your emmc is fine, don't worry! if your phone works than you've done nothing wrong!
If ICS fits your needs you can stay on it, but DO NOT use CWM!!
starnoise said:
Help please. This is the history of my flashing btw...
I had a rooted Gingerbread with CF root kernel KKA. When ICS came out i rushed and Flashed a cf root lpy zimage (kernel only) via Recovery ( i know it was stupid.. ) So i got stuck and i could only come up to CWM. I used the CWM to BACK UP MY DATA (this was before i even flashed the ICS rom). From there i used PC odin to flash kka gingerbread rom. Flashed it without problem. Then i flashed ICS LPY rom together with LPY kernel via Mobile Odin and i clicked wipe data. Everything went well. I haven't used CWM. Now i am affraid that i could have bad EMMC. Should i stay on ICS or should i flash stock GB rom again?
Click to expand...
Click to collapse
I had answered your question thru email. Stick with your current ICS rom will be the best option and choices. Since I do believe no one at the forum able to give you 100% accurately exactly what happen with your emmc. Just enjoy your ics.
Please don't simply flash any gb rooted kernel so that able use the cwm again and go back to gb. Please read the instruction carefully.
PERSONNAL OPINION: I'm always prefer flash stock or pre rooted gb rom thru pc odin beside flash axxx4.2kernel to perform full wipe.
Good luck bro..
Sent from my GT-N7000 using xda premium
lee yun khong said:
I had answered your question thru email. Stick with your current ICS rom will be the best option and choices. Since I do believe no one at the forum able to give you 100% accurately exactly what happen with your emmc. Just enjoy your ics.
Please don't simply flash any gb rooted kernel so that able use the cwm again and go back to gb. Please read the instruction carefully.
PERSONNAL OPINION: I'm always prefer flash stock or pre rooted gb rom thru pc odin beside flash axxx4.2kernel to perform full wipe.
Good luck bro..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Need help ,,
I am on stock LPY unrooted and came to LPY from GB LC2 unrooted as well.....but if memory serves then i remember that just after updating to LPY i had gone into recovery mode (stock recovery mode) and cleared the cache....does i mean that i stand a chance for the eMMC issue and that i shudn't be going back to GB unrooted LC2 and wait for the devs to fix this?
gurnishdhillon said:
Need help ,,
I am on stock LPY unrooted and came to LPY from GB LC2 unrooted as well.....but if memory serves then i remember that just after updating to LPY i had gone into recovery mode (stock recovery mode) and cleared the cache....does i mean that i stand a chance for the eMMC issue and that i shudn't be going back to GB unrooted LC2 and wait for the devs to fix this?
Click to expand...
Click to collapse
Well according to the devs here you should be good. But noone can guarantee you are 100%. I decided to wait till the issue gets resolved even though i haven't used recovery at all. I am taking my chances on ICS. But again staying on ICS isn't safe either I am quoting CHainfire here..
"Originally Posted by Chainfire
Ok so it still isn't really clear if the problem is still present in LPY, or if the issue is "left-over" due to previous ROMs.
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)"
So whichever choice you make... good luck.
yllivia said:
Well according to the devs here you should be good. But noone can guarantee you are 100%. I decided to wait till the issue gets resolved even though i haven't used recovery at all. I am taking my chances on ICS. But again staying on ICS isn't safe either I am quoting CHainfire here..
"Originally Posted by Chainfire
Ok so it still isn't really clear if the problem is still present in LPY, or if the issue is "left-over" due to previous ROMs.
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)"
So whichever choice you make... good luck.
Click to expand...
Click to collapse
Yup, is true. Beside you need to stay away from cwm, you should be aware when doing the large file transfer.
Stick with Lpy, do not touch cwm at all, try to avoid do any large files transfer.
Relax bro...u should be fine...just follow what the instruction given by the dev. Since no one really know exactly what happen.
Sent from my GT-N7000 using xda premium
Hey guys,
I hope you can help me. I am aware of the ICS Kernel Bricking bug, and the faulty chip with the faulty firmware, as described on the xda portal, and I read all the stickies. Nevertheless I want to ask you for your opinion on this matter, to prevent turning my note into a brick
So thats what happend last night:
I was on LPY for about 1 month (since released) with root, stock kernel. Before I was on GB DarkyRom 3.3. Everything went normal until I made 2 changes the last hours:
1. I modified the build.prop with this tutorial:
http://forum.xda-developers.com/showthread.php?t=1687156
2. I installed Super Video (like popup player on the galaxy s3) and had several freezes when I started to watch 2 videos. So I took out the battery like 4 times.
Phone booted normally. So I locked the screen, and went to a party.
Then I realized that within 2 Hours the battery got from 50% to 15%. I was too busy to look at betterbatterystats, so I just rebooted the phone with the stock Power Menu.
Now my phone won't boot anymore. It stucks on "Samsung Galaxy Note N-7000" Screen.
As I said, I have not wiped, or do anything with cwm or 3e recovery. However, I can get into DL mode and 3e recovery.
What can I do now? Flash LPF? Reflash LPY?
I read somewhere by someone, that it could be, that even without wiping, the phone can get brick at anytime... Did that happend to me?
I haven't tried to flash anything else, because I wanted to share this with you and get your opinion.
Thanks in advance
k!DDa
So now donot try anything.I suppose you were in darkyrom 3.3 re.If so,you should have known about the counter.So flash it and you will be fine.I again say it will increase counter if you use 3.3 re.
If you don't want the counter,flash a stock gb rom/stock-rooted gb rom.I prefer 3.3 re because it is a wipe rom
Hi vijai2011,
thanks for your answer but I was on darkyrom BEFORE I switched to LPY (that was just a side note^^)
> the last month, including today, I am on LPY, which isn't booting anymore.
k!DDa said:
Hi vijai2011,
thanks for your answer but I was on darkyrom BEFORE I switched to LPY (that was just a side note^^)
> the last month, including today, I am on LPY, which isn't booting anymore.
Click to expand...
Click to collapse
thats not a problem.you can try.
wow you're fast^^
okay but isn't it possible to revive my note? e.g. just flashing a non wipe ICS version via PC ODIN (I do not care about the counter or triangle)
like criskelos ICS No wipe http://forum.xda-developers.com/showthread.php?t=1609252
the inability to boot you describe sounds like something a corrupted build.prop might cause so it's probably nothing to worry about. you'll need to restore your build.prop somehow, probably by flashing something in Odin
ok thanks, I will try. but one good and one bad thing:
I saved the original build.prop before
But on the internal SD card and not my external ^^
If you want to be absolute sure Flash a stock ICS (a full wipe version) rom from pc odin. If all goes well there is no brickissue for you. Then you root using Dr Ketans method.
Sent from my GT-N7000 using xda premium
k!DDa said:
wow you're fast^^
okay but isn't it possible to revive my note? e.g. just flashing a non wipe ICS version via PC ODIN (I do not care about the counter or triangle)
like criskelos ICS No wipe http://forum.xda-developers.com/showthread.php?t=1609252
Click to expand...
Click to collapse
No problem.As I said already its better to go for a wipe rom because of the repartition thing...
one last qustion,
I decided to reflash LPY. But it has only an tar.md5 file. I cannot use MobileOdin. Can I just put it in PDA at PC Odin? (Rename it before to .tar?)
The last 20 firmwares I flashed hadn't that extension.
k!DDa said:
one last qustion,
I decided to reflash LPY. But it has only an tar.md5 file. I cannot use MobileOdin. Can I just put it in PDA at PC Odin? (Rename it before to .tar?)
The last 20 firmwares I flashed hadn't that extension.
Click to expand...
Click to collapse
yes that will work fine, but don't rename it. it works as .tar.md5
yes put the md5 in the pda section and flash with pc odin as normal
Thanks guys my phone is booting again
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
strangermyself said:
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
First you should t have flash abyss through odin since now you are not rooted and do t have the warranty too, the counter of flashes increased to 1 (look at the download mode small text), for rooting you can use chainfire's tool (in the cf-root kernel thread look for it in devolepment section) next get a stock rooted kernel and flash using the tool (read instructions).
For now use pc odin 1.87 and get a firmware 2.3.6 use the pc odin select the file on PDA and flash it, make sure phone is charged 100% and press start, if it doesn't work then uninstall drivers, reboot machine, reinstall them and kill kies process if present in task manager and then goto download mode connect USB and open pc odin wait for the port to be ready aka green and select file then start.... you should be fine its a soft brick afterall.
Sent from my GT-N7000 using Tapatalk 2
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
strangermyself said:
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
Click to expand...
Click to collapse
When connected to charger make sure phone is off the battery meter will show as soon as you connect, case it doesnt leave it for like 3 hours is fine... next about that ROM redownload. The package cleanup you temp directories in PC and try again if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
REVERSiN said:
... if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
strangermyself said:
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Whiskeyjack4855 said:
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Click to expand...
Click to collapse
Dude its a GB rom not superbrick bug in it and he didn't mention LPY yet.
Sent from my GT-N7000 using Tapatalk 2
strangermyself said:
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
Click to expand...
Click to collapse
Sorry for tea doubled post its a dumb app X's
You wipe using the CWM file in the Iss root section, and a normal recovery wipe would do too (aka restore defaults)
Sent from my GT-N7000 using Tapatalk 2
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
strangermyself said:
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
Click to expand...
Click to collapse
If you have the stock recovery, restore default wipes everything.
If you have stock re every and want CWM temporary just to wipe goto n7000 devolepment and check how to root by dr.ketan and get files there
If you have CWM then wipe data, wipe cache, wipe dalvik.... and try. Old download another firmware like kk5.... something else not the new LC1 LX1 releases.... (Latest GB) get an old one to get root easly
Sent from my GT-N7000 using Tapatalk 2
Hi everybody, I’m a newcomer to the world of Android and Samsung Note SG-N7000 and I strongly need you expert help.
Yesterday I have rooted my phone running GB 2.3.6 LA6 (non-root, non-wipe) after doing a fair share of reading (I thought), but I used a wrong way. I.o. following Dr.Ketan’s advice and downgrading to an early rootable version of GB, I have followed the method described in How to Root your Galaxy Note GT-N7000 - PC tools&Others - UC FORUM - Powered by Discuz! At http://forum.ucweb.com/forum.php?mod=viewthread&tid=27123 thinking that it is a new faster and simpler method. But I was wrong.
Although everything went OK and I had root and a functional CWM v5.8 plus AbyssNotekernel42CWTouchOriginalLogo, I also got the yellow triangle and the counter set to 1. Later on I have discovered that CWM was not working correctly and also the screen was displaying “null” for each key typed on the keyboard.
To repair the things I have applied the semiautomatic rooting method described in OneClickRoot – ONLINE by Glevitan (many thanks to him) at http://forum.xda-developers.com/showthread.php?t=1783733 downgrading to GB2.3.5 LA4 with Odin to the 2.6.35.7....KJ1 kernel plus manual flashing of the CF kernel with CWM Manager v5.0.
Everything seems to work fine except that I still have the yellow triangle + the “null” result typing problem. I have wiped the phone and I have tryied out another 2 GB kernel, i.e the latest Abyss and Speed Mode, with the same results. Now I am back on the CF kernel with GB 2.3.5 KJ1.
This is the point where I need your expert help on how to cure the 2 above mentioned problems.
Also I have tried to flash with CWM the complete stock GB ROM 2.3.6 LA6 COA from the ext. SD card, but the installation was aborted from the beginning ("Can’t open" file on SD card). The ROM file is <GT-N7000_COA_N7000XXLA6_N7000OXXLA1_N7000XXLA4.zip> which has inside the archive 2 zipped files <N7000XXLA6_N7000OXXLA1_N7000XXLA4_HOME.tar.md5> and <SS_DL.dll>.
I suspect that there is something related to the format of the ROM archived files and I have no idea what the extension .md5 is for. I know that this is about checksum, but I have no idea on how to work with it, i.e was the download correct or not and how to get further to the .tar or zimage file. Kindly asking for your answers.
What kind of file do I need to place on the ext sd card, I thought it is a zip file for CWM and a .tar file on the PC for Odin. Am I wrong?
What do I need to do please in this stage in order to get to a fully functional rooted GB ROM with functional keyboard, no triangle plus the counter set to zero?
Any support will be highly appreciated. Thank you!
Big Fella
that sunds like the austalian rom, I myself have been trying to do that, yet u dont open the zip in cwm you open to extract the .tar file on your pc then flash through odin, be sure to put it in the pda section,
when you do this can you reply back and let me know if you can get past the 'factory fs' part in odin, thats where i am stuck
also when you flash the abyss ro your flash counter will go up, if you want to get rid of this let me know
Sent from my Transformer Prime TF201 using XDA premium HD
Devices - 64Gb Asus Transformer Prime rooted .28 Stock ROM
32Gb Asus Transformer completely stock
HTC Sensation XL running 4.0.3 with Musketeer ROM Sense 4.0
Samsung Galaxy S Running 4.0.3
HTC HD2 Leo, overclocked 1.4GHz 1 Gb RAM 4.0.3 tytung ROM, long live the LEO legend
For Traingle Problem use Traingle Away by Chain fire.
Now you have to flash a rooted gb rom (tar file)
Open odin.
Start your phone in Download mode.
Connect your phone to pc and wait for a minute for odin to detect it
Select file under pda tab which you have downloaded
Start flashing. Don't change any option.
Sent from my GT-N7000 using XDA Premium App
axelTP2 said:
Hi everybody, I’m a newcomer to the world of Android and Samsung Note SG-N7000 and I strongly need you expert help.
Yesterday I have rooted my phone running GB 2.3.6 LA6 (non-root, non-wipe) after doing a fair share of reading (I thought), but I used a wrong way. I.o. following Dr.Ketan’s advice and downgrading to an early rootable version of GB, I have followed the method described in How to Root your Galaxy Note GT-N7000 - PC tools&Others - UC FORUM - Powered by Discuz! At http://forum.ucweb.com/forum.php?mod=viewthread&tid=27123 thinking that it is a new faster and simpler method. But I was wrong.
Although everything went OK and I had root and a functional CWM v5.8 plus AbyssNotekernel42CWTouchOriginalLogo, I also got the yellow triangle and the counter set to 1. Later on I have discovered that CWM was not working correctly and also the screen was displaying “null” for each key typed on the keyboard.
To repair the things I have applied the semiautomatic rooting method described in OneClickRoot – ONLINE by Glevitan (many thanks to him) at http://forum.xda-developers.com/showthread.php?t=1783733 downgrading to GB2.3.5 LA4 with Odin to the 2.6.35.7....KJ1 kernel plus manual flashing of the CF kernel with CWM Manager v5.0.
Everything seems to work fine except that I still have the yellow triangle + the “null” result typing problem. I have wiped the phone and I have tryied out another 2 GB kernel, i.e the latest Abyss and Speed Mode, with the same results. Now I am back on the CF kernel with GB 2.3.5 KJ1.
This is the point where I need your expert help on how to cure the 2 above mentioned problems.
Also I have tried to flash with CWM the complete stock GB ROM 2.3.6 LA6 COA from the ext. SD card, but the installation was aborted from the beginning ("Can’t open" file on SD card). The ROM file is <GT-N7000_COA_N7000XXLA6_N7000OXXLA1_N7000XXLA4.zip> which has inside the archive 2 zipped files <N7000XXLA6_N7000OXXLA1_N7000XXLA4_HOME.tar.md5> and <SS_DL.dll>.
I suspect that there is something related to the format of the ROM archived files and I have no idea what the extension .md5 is for. I know that this is about checksum, but I have no idea on how to work with it, i.e was the download correct or not and how to get further to the .tar or zimage file. Kindly asking for your answers.
What kind of file do I need to place on the ext sd card, I thought it is a zip file for CWM and a .tar file on the PC for Odin. Am I wrong?
What do I need to do please in this stage in order to get to a fully functional rooted GB ROM with functional keyboard, no triangle plus the counter set to zero?
Any support will be highly appreciated. Thank you!
Click to expand...
Click to collapse
Hey, thanks for using the tool...glad it works. To fix the null issue You will have to flash a Firmware with the CSC file with mobile odin.
The yellow triangle Is solved with the triangle away app by chainfire....or using a jig.
@OP
What i understand is
You are on now
CF kernel with GB 2.3.5 KJ1.
you want solution for two problem
Keyboard null
Triangle + raise counter
OK
just follow this
-Reboot in recovery
-Wipe cache and data
-Download and flash any ICS ROM with PC odin
-Root it
-Use triangle away appl to reset counter
Hope at end you won't have any issue
links needed
To flash N root ICS ROM -http://forum.xda-developers.com/showthread.php?t=1424997
For triangle away - http://forum.xda-developers.com/showthread.php?p=22463153#post22463153
How to use triangle
Download and install triangle v1.70 from link above
open it, it will ask to download flasher file, allow it to download
Now select to reset countre, it will reboot in recovery N will do job.
Thank you everybody for taking the time to answer me.
I have solved my problem by using PC Odin for flashing a 3 file GB stock rom XXLC1 OXA Open Europe, which finally has brought me back to normal. Then I have flashed further the single file GT-N7000_COA_N7000XXLA6_N7000OXXLA1_N7000XXLA4.zip getting me back to the original LA6 stoc rom.
I have no idea on why this zip file did not work from the beginning, but for sure I was doing somethng wrong.
The Keyboard null was cured while flashing he new CSC file I guess.
The yellow triangle disappeared due to the stock rom flashing, while for the binary counter I have used the usb jig and the 10 steps procedure.
Now I need to root by going the correct way of Dr.Ketan, i.e. by downgrading first, no shortcuts.....
Many many THANKS again to eveybody giving me these precious advices.....
I was running the ultimate rom and I tried to download a new kernel. Yup, soft brick my phone. The question is when I get Odin 1.85, where do I find the pda and phone file for odin? Thanks for any help to restore my phone to normal.
What's the new kernel? Do you have access to recovery mode? If yes then just flash the philz xxlsc kernel back and then the phone should boot.
From samfirmware.com you can download the stock roms which can be flashed via odin. Or check a thread named all stock roms at one place by Dr. Ketan in the original development section
I flashed philz 3.99 and I can't get back into recovery. Argh!
Philz xxlsc 3.99 is compatible with ultimate.. Try to get into recovery mode again. Remove usb cable if it is connected. Also try one after removing and inserting battery
I still can't get into recovery mode yet. It's taking a long time for the files to download to the cpu too.
something wrong with Philz xxlsc 3.99 it will not brick the phone just flash back the older versionn
if still can't turn it on just flash a new rom or if u have a previous backup just restore it.
alvinhaw said:
something wrong with Philz xxlsc 3.99 it will not brick the phone just flash back the older versionn
if still can't turn it on just flash a new rom or if u have a previous backup just restore it.
Click to expand...
Click to collapse
I have got my phone up and working last night but flashing a new kernel BUT I have the yellow triangle. I read about getting a USB JIG but I really don't care about the yellow triangle. I will have this phone for awhile so I'm in no rush. So, if that yellow triangle just means a flash counter and everything else is working, I don't care. thanks for all the advice and hope to contribute one day.
If you really need to get rid of the triangle search xda for chainfires free triangle away apk (hint...it costs money on play store)
Sent from my GT-N7000000000 using Tapastalker 2