Develop Bugs

Stuck After installing CM

Hello all,
I've followed the installation in the CM site
i've installed the latest stable via CWM
and now it keeps showing me the welcome to android "touch tge android to begin" and than it goes to the CM load animation
please help

flashed kernel ?
without right kernel phone wont boot up.

resolved
i used the one in the cm zipped file
but i've used the RC ver and it worked,
maybe i did something wrong the first time, i can't put my finger on it
thanks anyway

Wipe cache and others before flashing

abd_alazeez2002 said:
Wipe cache and others before flashing
Click to expand...
Click to collapse
Beat me to it. I had the same problem when I flashed FXP052 because I rushed and forgot to wipe the data and the delvic. Follow the wiki and you shouldn't have any problems
Sent from my LT15i using xda premium

[Q] Stuck on boot loop

I tried a search but didn't find much of any relevance to my Arc's problem.
My Arc was getting quite laggy so I decided to wipe and put a custom ROM on. I rooted, then unlocked the bootloader and managed to put on CWM using DoomLord's kernel. Everything fine up until here.
Then, mistakenly, I tried to put stable CM7 on without updating the stock ROM. I was still on 3.0 (2.3.3) something. Well, after that it got stuck in a boot loop with the SE and CM7 logos just coming up and restarting.
I then tried the Flashtool with a stock uptodate 4.0 something firmware. It flashed successfully, but it still was stuck in the loop, albeit now without the CM7 logo. I then tried the FTA unbricking tool for repairing the trim area but it still stayed in the boot loop.
What else can I do? Maybe there is a driver problem and that is why even after using Flashtool it still doesn't boot?
I would be very grateful if someone could help me on this.

You have to flash FXP's kernel and not DooMKernel.

But I also tried to flash a stock rom and that didn't work also.
EDIT: I flashed stock ROM again, still didn't boot. Installed DoomLord kernel and then arconium and it still doesn't boot.
EDIT 2: In CWM Recovery if I try to wipe data, it says this:
"E:format_volume: no MTD partition "userdata"
Has anyone got a fix for this?
It would be much appreciated.

can you charge your phone now?

Yep, I can charge the phone.

it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...

gogo415 said:
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
Click to expand...
Click to collapse
No luck with previous firmwares so I'll try to flash the latest .62 stock ROM and then see.
I'll let you know how I get on. Thanks!

Well lads, I managed to get it working by flashing the LT18i firmware (4.0.2.A.0.42_CE). Now I just need to go back to the drawing board and try to get CM7 on there.
Thanks for all the help! I'll update this thread with any experiences.

I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.

ZAnwar said:
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
Click to expand...
Click to collapse
hi, i came up with the same question:
E:format_volume: no MTD partition "userdata"
and my device is moto xt502
could you be so kind to give some details how you fix it
thank you very much

I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully

ilamaan said:
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
Click to expand...
Click to collapse
I followed the instructions too, though they are not so much noob-friendly (and neither are the people on the forums, it seems...). FXP is not responding (actually, they rarely respond to anything, they usually just post when new release is out), other people either don't know how to fix it, because they haven't experienced such issues, or they are just hostile because you're "a an annoying noob". Anyway... first time after trying to flash 64 baseband on 107 or 106 release, I got stuck on logo, then flashed back to .42 and it worked. Now, while updating to 108, I tried to flash the 64 libraries and patch, but it didn't work. Got back to .42, but this time nothing happened. Still stuck on logo. And when I try to restore data, it says:
E:format_volume: no MTD partition "userdata"
Error while formatting /data!
I think I'll go back to stock... love CM, but hate the poor/no help of the developers...

try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done

My thanks goes to you. I was hoping to avoid full wipe, but I don't care anymore, since I brought my phone back to life. I skipped these steps, though:
beranchoi said:
flash baseband 64
flash baseband64libs.zip
Click to expand...
Click to collapse
...because I went to check which baseband my phone was after flashing Global .62, and it said I was on -64, so it was no more necessary. For all of you having trouble with booting, follow the instructions given.
And now back to restoring all those apps

hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?

lemon66 said:
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
Click to expand...
Click to collapse
This is the link to the stock 4.0.2.A.0.42.. flash it using flashtool.. http://www.multiupload.com/W3B7BOKUXQ
Everything you need for flashing FXP is on his signature, including bb .64 (to be flashed with flashtool - doesn't erase a thing).. then download FXP (latest is 108) and inside the zip file you'll see boot.img, which contains the special kernel (to be flashed using fastboot, not flashtool).
Also there's no dark screen bug in the latest releases, certainly not in FXP 107 and 108, which I'm using now.

Please help!
beranchoi said:
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
Click to expand...
Click to collapse
Hey, this is my first post on here. I am new to android and just got an arc a few days ago. Even before i got it i was trying to figure out how to mod it. I am reasonably good at computers but a lot of the stuff i read on these forums is beyond me.
I have done my best to root and install CM7 on my arc but i have failed yet again.
I finally got it rooted and was all happy until when i tried to install CM7, all i can get to is the boot screen, but although the little android on the skateboard is very cool, i wish i could get it going!
So because I dont really understand the list of instructions you posted in this quote, i was hoping you could kind of translate into noob-speak. I still dont feel like i completely understand 'flashing'. In your instructions you say to "flash baseband 64" and that is the main point where I am stuck i think. Do you use a certain program (flashtool?) for this? or do it through a terminal window on the PC.
Also links to all the files mentioned would be awesome, its hard to find proper links with multiupload down and that kind of thing. Also with the rate this kind of tech evolves, things get outdated to quickly.
Please help! At the moment i have (i think) successfully returned my arc to the stock firmware using flashtool. Although i did this twice because i re-tried flashing CM7 and failed again. And the second time i couldnt seem to select LTI5i as the device to flash too, but LTI8i is what i used and it appears to have worked. So any help with that little conundrum would also be appreciated!
Cheers for any help given, I am so desperate to get this mod going as i have spent a solid 10+ hours trying already.

your bootloader unlock?right?
which kernel u use right now?

@tehknowitallnoob, I can lead you through the whole flashing process, if you want to, but only on Friday after around 9 pm GMT +1, since I don't have the time to do it earlier.
Sent from my LT15i (Xperia arc) on CM7

Try this:
Reflash back to stock ROM with a flashtool.
Then again flash the cm7 or try cm9
-cheers

[Q] Problems Flashing JellyTime 4.2 R4.

I tried to flash Randomblames 4.2.1 R4 rom and upon rebooting I get stuck in a FC loop with the phone or launcher process. I did clean wipe and I'm also using TWRP 2.3.3.0. I'll check if there is an update to my recovery and post back tomorrow, but for now does anyone have any ideas? I would post this in the development rom section, but I'm not allowed to.

Try 4ext
MasterChrome said:
I tried to flash Randomblames 4.2.1 R4 rom and upon rebooting I get stuck in a FC loop with the phone or launcher process. I did clean wipe and I'm also using TWRP 2.3.3.0. I'll check if there is an update to my recovery and post back tomorrow, but for now does anyone have any ideas? I would post this in the development rom section, but I'm not allowed to.
Click to expand...
Click to collapse
I've been flashing so many times any 4.2 version, thanks to every dev!!!.
I'm always using 4 EXT recovery without any issue, so I recommend to use it.
Try to search 4 EXT Recovery Updater App in the PlayStore and good luck.

Never had a problem with CWM here.
I have flashed around 50 different JB roms - and also older GB ones.

R: [Q] Problems Flashing JellyTime 4.2 R4.
gruntyoldbag said:
Never had a problem with CWM here.
I have flashed around 50 different JB roms - and also older GB ones.
Click to expand...
Click to collapse
Me too... But i'm with 4ext not CWM.
Masterchrome, have you tried to format all partitions (except SD)?
Sent from HTC UzDesireHD

If you have rooted the HD with AAHK ClockWorkMode Recovery is installed. You can use that way. First you can format the SD-card in the Advanced menu. Remove the SD-Card and connect it to the PC. Copy R4 and Gapps to the SD-card, and put the card in the Phone. Start CMR and flash both. I did it that way, no problems!

AOSP roms will NOT run! Driving me crazy...

So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?

I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app

iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.

Do you by chance have a refurbished s2?

The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?

es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app

es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.

Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!

es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?

UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.

es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?

tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...

I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.

DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?

TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/

Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk

yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways

wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.

DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.

Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte

[Q] Bootloops on every rom Note 2 GT-N7105

Hello!
I recently got a Note 2 (GT-N7105)
And for some silly reason wich even disappoints myself i wanted to overclock , well that didn't make sense i know but however i did it! and directly after i installed the required file (I don't remember wich one but it was for 1.8Ghz) after the installing my phone kept showing the boot logo , i tried to use my backup but even after restoring it didnt boot! I cleaned everything wich also cleaned my backup...
I been on it for about 7 hours now trying different roms , kernels , and every file i could find but nothing helps.
I now installed Cyanogenmod using CMW but even that bootloops.
The last thing i could notice is CMW showing me a E: failed to Mount /efs (Invalid argument) Wich makes me worry even more...
I honestly hope there are some good peaple who could help me with this... Finally got a great phone and by stupid mistakes i made it won't work anymore..
I don't care what rom gets on it , Even if its a hello kitty rom u won't hear me complain , If the phone works again i'll be happy!
Not sure if this helps but its a GT-N7105 , i know it had the newest android there was (4. something, i think it was 4.3)
Odin does see the device , My CMW (6.0.4.1) works and Download Mode works.
I hope anybody can help me!
In case you want to help me live wich would be awesome my skype is : chrishendriks92
If it gets fixed i will Offcourse place the solution here.
(The note is not a new one , its used and a few months old , worked 100% before my stupid decisions bricked it)
(so here's a small version)
-Every rom i tried will bootloop , It shows a different boot video/logo everytime tho
-It all happened after i tried a 2.8Ghz Overclock
-i get a EFS error in CMW
-Accidentily i deleted my backup but i don't mind whatever rom gets on it
-Download mode and CMW (6.0.4.1) works

dodemans said:
Hello!
I recently got a Note 2 (GT-N7105)
And for some silly reason wich even disappoints myself i wanted to overclock , well that didn't make sense i know but however i did it! and directly after i installed the required file (I don't remember wich one but it was for 1.8Ghz) after the installing my phone kept showing the boot logo , i tried to use my backup but even after restoring it didnt boot! I cleaned everything wich also cleaned my backup...
I been on it for about 7 hours now trying different roms , kernels , and every file i could find but nothing helps.
I now installed Cyanogenmod using CMW but even that bootloops.
The last thing i could notice is CMW showing me a E: failed to Mount /efs (Invalid argument) Wich makes me worry even more...
I honestly hope there are some good peaple who could help me with this... Finally got a great phone and by stupid mistakes i made it won't work anymore..
I don't care what rom gets on it , Even if its a hello kitty rom u won't hear me complain , If the phone works again i'll be happy!
Not sure if this helps but its a GT-N7105 , i know it had the newest android there was (4. something, i think it was 4.3)
Odin does see the device , My CMW (6.0.4.1) works and Download Mode works.
I hope anybody can help me!
In case you want to help me live wich would be awesome my skype is : chrishendriks92
If it gets fixed i will Offcourse place the solution here.
(The note is not a new one , its used and a few months old , worked 100% before my stupid decisions bricked it)
(so here's a small version)
-Every rom i tried will bootloop , It shows a different boot video/logo everytime tho
-It all happened after i tried a 2.8Ghz Overclock
-i get a EFS error in CMW
-Accidentily i deleted my backup but i don't mind whatever rom gets on it
-Download mode and CMW (6.0.4.1) works
Click to expand...
Click to collapse
Ok, so what I would do.
I would wipe data through CWM.
Download official ROM from sammobile.com and flash it through Odin.
I hope this will help to get the phone booted.
After that we will worry about imei recovery.

dzejju said:
Ok, so what I would do.
I would wipe data through CWM.
Download official ROM from ... and flash it through Odin.
I hope this will help to get the phone booted.
After that we will worry about imei recovery.
Click to expand...
Click to collapse
Thank you for your reply:good:
I'm downloading it , looks like its going to take a while so i'll let you know!

Try mskips toolkit from skipsoft.net. It has a recovery package that should do the trick. There is a thread on it on here but i think it's closed due to Microsoft signature issues
Sent from my GT-N7105 using XDA Premium 4 mobile app

I'm afraid downloading/Flashing the rom didnt work.
ill get the T-Mobile screen , and then the samsung logo where it gets stuck , the install was completed tho so no errors whatsoever
This is a picture link s30.postimg.org/8l0bgrxa8/image.jpg
Would be amazing if you could help me out with this because i can't choose ''Option 2'' right picture , it just won't take it.
I can install teamviewer or whatever programm you want

I have the same problem, I'm on 4.3 version and tried to downgrade to 4.1.1 and went back to 4.3, I formatted the system through twrp with NO OS INSTALLED to be sure it is totally cleaned but all the way, I still experiencing reboot issue.
At first I encountered unfortunately systemui has stopped, done rooting and fixing permission but still no luck.
One more thing, I already flashed pit file.

.
(Update , I tried anything i could but it didnt work out , its going to Samsung Support)

cz4r3n said:
I have the same problem, I'm on 4.3 version and tried to downgrade to 4.1.1 and went back to 4.3, I formatted the system through twrp with NO OS INSTALLED to be sure it is totally cleaned but all the way, I still experiencing reboot issue.
At first I encountered unfortunately systemui has stopped, done rooting and fixing permission but still no luck.
One more thing, I already flashed pit file.
Click to expand...
Click to collapse
Flash right bootloader, then install fresh rom. Should be good to go.

Mufrad said:
Flash right bootloader, then install fresh rom. Should be good to go.
Click to expand...
Click to collapse
the problem persist.I flashed different bootloader already

cz4r3n said:
the problem persist.I flashed different bootloader already
Click to expand...
Click to collapse
You installed a kernel right? To over clock? First flash new bootloader, then flash stock kernel, then again flash stock rom, do not let the device boot up before you have done all three.

--------------------------------------------
_________________________

Mufrad said:
You installed a kernel right? To over clock? First flash new bootloader, then flash stock kernel, then again flash stock rom, do not let the device boot up before you have done all three.
Click to expand...
Click to collapse
I tried Agni pure kernel and followed your instructions but no avail,I think there is problem with the board,because when I wipe, the SuperSu also erased.

cz4r3n said:
I tried Agni pure kernel and followed your instructions but no avail,I think there is problem with the board,because when I wipe, the SuperSu also erased.
Click to expand...
Click to collapse
I said to install stock kernel not custom kernel, and after wipe when you install stock rom you will loose root and also loose all data and apps from previous rom anyway.

Mufrad said:
I said to install stock kernel not custom kernel, and after wipe when you install stock rom you will loose root and also loose all data and apps from previous rom anyway.
Click to expand...
Click to collapse
yup I already did that,I flashed stock kernel from http://opensource.samsung.com/.I know reflashing stock rom will delete everything including root.
What I mean is when Im rooted and tried to wipe the phone, SuperSu also deleted.Im wondering that I have a corrupted emmc, It seems that it is not mounted correctly, although I tried to flash a pit file already.

cz4r3n said:
yup I already did that,I flashed stock kernel from http://opensource.samsung.com/.I know reflashing stock rom will delete everything including root.
What I mean is when Im rooted and tried to wipe the phone, SuperSu also deleted.Im wondering that I have a corrupted emmc, It seems that it is not mounted correctly, although I tried to flash a pit file already.
Click to expand...
Click to collapse
What method did you use to root and inject supersu?

Mufrad said:
What method did you use to root and inject supersu?
Click to expand...
Click to collapse
The so called SAFEROOT
And I even tried the CF ROOT by Chainfire

butmena said:
--------------------------------------------
_________________________
Click to expand...
Click to collapse
? What!
Sent from my GT-N7100 using XDA Premium 4 mobile app