Hi to all,
I don't post here often, but this time I think that I really need your help and because of that, it will be an long post. :cool:
I read all treads before I do anything, but seems that I still don't get it good especially because it's a second time in a row that I got an software brick. :rolleyes::rolleyes:
I own an international N7000 (volt group B) and it was more then 30 (thirty) times flashed in last seven months with a lot of custom kernels (mostly overclocked) and also with lot of different stock and custom ROM's, and there was no any major problem till I came back to stock TWR JB ROM.
I live in the Netherlands and I couldn't wait relaese of the Netherlands original stock JB ROM (but it also shouldn't matter, correct me if I'm wrong) and I flashed the first for Europe available JB ROM and that was an German stock JB ROM. Before of that I tested also Hong Kong JB ROM but I have removed it after a few days of testing.
This time I came from a CM 10.0 and NirvanaCore N6 and before everything, I wanted to get all right (even it wasn't necessary). I flashed back a rooted GB ROM from the tread of Dr. Ketan to be for shore that I have all good done. Then I have wiped from CWM cache partiton, than factory reset and then in advanced I wiped a dalvik cache.
Than I went to Mount and Storage and there I have formated: preload, system, data and cache. After that I cleand once again dalvik cache and then flashed with PC Odin 3.07 a stock JB German ROM.
And of course it was all perfect as always.
Then I have used a XXLSZ-OXA (fixed for bootloop)<< 07.03.2013 - PhilZ-cwm6 v4.87.6 with CWM 6.0.2.8 based recovery >> to obtain a root and that was it.
I restored all my 550 apps with Titanium BackUp too. Of course I used it for a few days to "settle it down" but I was dissapointed with it's performance.
I tried to flash a few scripts because I've read that there is no problem at all to flash "V6 supercharger" on N7000. I installed Busy Box Pro 1.20.02 and free script manager and applied "V6 supercharger" script from Script Manager to ROM but it didn't succsed 100% but 50% so there was something that I missed how to manage but the most of tweaks really already worked well and the performance and smoothnes of stock JB ROM came near to overclocked N6 with CM 10.0.
I flashed then also "Air View fix scripts" to preload and to system from CWM and I got it to work also in galery and by video preview. So I had relatively fully working TWR JB ROM with no lags and airview as it should be.
Than my baterry went low and I left it on Samsung AC charger to charge it.
I checked it few times in few hours if it charge, and the last time I checked it was after it reached about 92%. I went out and came back in two hours and I thought it schould be fully charged now. :)
But when I looked at it I saw that both touch buttons (home button and back button) were lited on, constantly, what it wasn't a good sign :( .
Of course a Note was stuck and with no response, dus the only way was to remove the battery to restart it.
Actually, it was a first time that my Note went fully off without any current and completely swiched off. Before that it was only few times restarted but not fully swiched off.
Next time when I put battery back Note could not start up any more. That was a first soft-brick in my life. :cyclops:
I didn't ordered a USB JIG but I send it to Samsung Repair Centar and they just reflashed it in meanwhile with a new Netherlads LSZ JB ROM and they send it back to me, even all my files was still there on the main phone memory togheter with philz rooted kernel and all other rooted kernels and scripts. :D
But again it wasn't much better and with the same poor performaces, so again I decided to root it, but now it was already new XXLSZ-OXA (fixed for bootloop) << 13.03.2013 - PhilZ-cwm6 v4.88.2 with CWM 6.0.2.9 based recovery >> kernel and I just flashed it when I saw that the new kernel was already up there (<< 17.03.2013 - PhilZ-cwm6 v4.89.4 with CWM 6.0.2.9 based recovery >>) I have download it but I didn't have time to flash it.
I made a nandroid back up (and a holo backup too) and again decided to try to speed it up a little bit, but now with a few other scripts.
This time I didn't flash "Air View fix" scripts and I choose also not to flash "V6 Supercharger" but for "4cyl_Turbo_engine_150_shot_v0.2.3" and " CrossBreeder -3.15.13-Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock" script and again it gain in speed. Also I restored about 550 apps on my 64Gb microSd with Titanium BackUp.
Everything was fine untill the battery went down.
Before it reached 1% I ordered to android to swich off the device and it went fully good.
When I tried to charge it with a USB cable via USB 3.0 port it didn't started. Then I tried to charge it with an original Note AC charger but the result was the same. So it seems to be again soft-bricked.
Last friday I took a phone to a local Samsung Repair center and I said to them that I have faild with Software update. They said that I don't have to worry about it, because there is newest software update on the Samsung server which is just released, but I have to wait for about an hour to be downloaded and it's an update which is still not available via KIES but only for Samsung stuff. :cowboy:
So I beleved him and I sat down to wait and the guy came after a 45 minuts to tell me that he doesn't know what is going on, because the phone can't be recognised and asked me if I want to send it immediatly to main Samsung Service, but because I already ordered a USB JIG I wanted to try it before I send it to them to reflash it again.
The battery was complitely empty so I found a place where I can fully charge it and when I came at home I tried the USB JIG revival methode to get it in Download mode but it also faild.
Someone offered to me for 25 euros to reflash it with RIFF JTAG Box but I'll send it first to Samsung to see what they will do.
Now I ask all wise and experienced users and developers to tell me where it went wrong ?
1) Is that Philz kernel and which kernel should I precisaly choose next time for the Netherlands LSZ JB ROM or should I try SpeedMod N7000 Jelly Bean [K5-2 CWM CIFS ROOT / NO-ROOT] kernel ?
2) Are the scripts responsable for bricks, which maybe interfere with wrong partitions or somthing like that ?
3) Or is it AirView Fix script (In the first brick) ?
It's also remarkable that after powering phone down it won't boot anymore, in both cases.
What do you guys think about "V6 Supercharger" and about the newest " 4cyl Turbo engine v0.2.9_r1 w/ 200 shot NOS | Stable" mods, and what about " CrossBreeder -3.15.13-Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock" mod?
It's all about TWR and I ask all this because there are people which want to stick with a stock TWR JB ROM and maybe it can help to them too...
If you still read this, thanks for your patience and I hope to see your reactions and to read your answers soon... :)
Thanks in advance.
I don't post here often, but this time I think that I really need your help and because of that, it will be an long post. :cool:
I read all treads before I do anything, but seems that I still don't get it good especially because it's a second time in a row that I got an software brick. :rolleyes::rolleyes:
I own an international N7000 (volt group B) and it was more then 30 (thirty) times flashed in last seven months with a lot of custom kernels (mostly overclocked) and also with lot of different stock and custom ROM's, and there was no any major problem till I came back to stock TWR JB ROM.
I live in the Netherlands and I couldn't wait relaese of the Netherlands original stock JB ROM (but it also shouldn't matter, correct me if I'm wrong) and I flashed the first for Europe available JB ROM and that was an German stock JB ROM. Before of that I tested also Hong Kong JB ROM but I have removed it after a few days of testing.
This time I came from a CM 10.0 and NirvanaCore N6 and before everything, I wanted to get all right (even it wasn't necessary). I flashed back a rooted GB ROM from the tread of Dr. Ketan to be for shore that I have all good done. Then I have wiped from CWM cache partiton, than factory reset and then in advanced I wiped a dalvik cache.
Than I went to Mount and Storage and there I have formated: preload, system, data and cache. After that I cleand once again dalvik cache and then flashed with PC Odin 3.07 a stock JB German ROM.
And of course it was all perfect as always.
Then I have used a XXLSZ-OXA (fixed for bootloop)<< 07.03.2013 - PhilZ-cwm6 v4.87.6 with CWM 6.0.2.8 based recovery >> to obtain a root and that was it.
I restored all my 550 apps with Titanium BackUp too. Of course I used it for a few days to "settle it down" but I was dissapointed with it's performance.
I tried to flash a few scripts because I've read that there is no problem at all to flash "V6 supercharger" on N7000. I installed Busy Box Pro 1.20.02 and free script manager and applied "V6 supercharger" script from Script Manager to ROM but it didn't succsed 100% but 50% so there was something that I missed how to manage but the most of tweaks really already worked well and the performance and smoothnes of stock JB ROM came near to overclocked N6 with CM 10.0.
I flashed then also "Air View fix scripts" to preload and to system from CWM and I got it to work also in galery and by video preview. So I had relatively fully working TWR JB ROM with no lags and airview as it should be.
Than my baterry went low and I left it on Samsung AC charger to charge it.
I checked it few times in few hours if it charge, and the last time I checked it was after it reached about 92%. I went out and came back in two hours and I thought it schould be fully charged now. :)
But when I looked at it I saw that both touch buttons (home button and back button) were lited on, constantly, what it wasn't a good sign :( .
Of course a Note was stuck and with no response, dus the only way was to remove the battery to restart it.
Actually, it was a first time that my Note went fully off without any current and completely swiched off. Before that it was only few times restarted but not fully swiched off.
Next time when I put battery back Note could not start up any more. That was a first soft-brick in my life. :cyclops:
I didn't ordered a USB JIG but I send it to Samsung Repair Centar and they just reflashed it in meanwhile with a new Netherlads LSZ JB ROM and they send it back to me, even all my files was still there on the main phone memory togheter with philz rooted kernel and all other rooted kernels and scripts. :D
But again it wasn't much better and with the same poor performaces, so again I decided to root it, but now it was already new XXLSZ-OXA (fixed for bootloop) << 13.03.2013 - PhilZ-cwm6 v4.88.2 with CWM 6.0.2.9 based recovery >> kernel and I just flashed it when I saw that the new kernel was already up there (<< 17.03.2013 - PhilZ-cwm6 v4.89.4 with CWM 6.0.2.9 based recovery >>) I have download it but I didn't have time to flash it.
I made a nandroid back up (and a holo backup too) and again decided to try to speed it up a little bit, but now with a few other scripts.
This time I didn't flash "Air View fix" scripts and I choose also not to flash "V6 Supercharger" but for "4cyl_Turbo_engine_150_shot_v0.2.3" and " CrossBreeder -3.15.13-Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock" script and again it gain in speed. Also I restored about 550 apps on my 64Gb microSd with Titanium BackUp.
Everything was fine untill the battery went down.
Before it reached 1% I ordered to android to swich off the device and it went fully good.
When I tried to charge it with a USB cable via USB 3.0 port it didn't started. Then I tried to charge it with an original Note AC charger but the result was the same. So it seems to be again soft-bricked.
Last friday I took a phone to a local Samsung Repair center and I said to them that I have faild with Software update. They said that I don't have to worry about it, because there is newest software update on the Samsung server which is just released, but I have to wait for about an hour to be downloaded and it's an update which is still not available via KIES but only for Samsung stuff. :cowboy:
So I beleved him and I sat down to wait and the guy came after a 45 minuts to tell me that he doesn't know what is going on, because the phone can't be recognised and asked me if I want to send it immediatly to main Samsung Service, but because I already ordered a USB JIG I wanted to try it before I send it to them to reflash it again.
The battery was complitely empty so I found a place where I can fully charge it and when I came at home I tried the USB JIG revival methode to get it in Download mode but it also faild.
Someone offered to me for 25 euros to reflash it with RIFF JTAG Box but I'll send it first to Samsung to see what they will do.
Now I ask all wise and experienced users and developers to tell me where it went wrong ?
1) Is that Philz kernel and which kernel should I precisaly choose next time for the Netherlands LSZ JB ROM or should I try SpeedMod N7000 Jelly Bean [K5-2 CWM CIFS ROOT / NO-ROOT] kernel ?
2) Are the scripts responsable for bricks, which maybe interfere with wrong partitions or somthing like that ?
3) Or is it AirView Fix script (In the first brick) ?
It's also remarkable that after powering phone down it won't boot anymore, in both cases.
What do you guys think about "V6 Supercharger" and about the newest " 4cyl Turbo engine v0.2.9_r1 w/ 200 shot NOS | Stable" mods, and what about " CrossBreeder -3.15.13-Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock" mod?
It's all about TWR and I ask all this because there are people which want to stick with a stock TWR JB ROM and maybe it can help to them too...
If you still read this, thanks for your patience and I hope to see your reactions and to read your answers soon... :)
Thanks in advance.