Related
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Prior to receiving my GS2 from T-Mobile I did research on how to Root, Flash ROMs, you know, all the cool things Android phones can do, and I mean A LOT of research. When I finally did recieve my phone the first thing I did was root it, which worked flawlessly - at which point I thought "Hey, this isn't so hard I won't have any problems at all!" OH BOY WAS I WRONG.
Here's where everything went wrong: The first ROM I thought I'd install was AOKP Milestone and then I'd try CM10, so I put both .Zip files into my SD card. I backed up to Titanium Backup and to my External SD card through Clockwork mod then I installed AOKP Milestone and made it to the home screen with some force close messages. It was running, but didn't look very stable to me and the whole "Swagger" thing turned me off to it. I went back to Clockwork Mod and the website that I got CM10 from also told me to run DarkSide Wipe before installing the ROM so I did just that. Ran Darkside, installed CM10, then installed Gapps. I then rebooted my phone and CM10 started to load up, but after 10 minutes of just the splash screen I assumed it was stuck in a bootloop. I then restored the backup I made before installing Milestone, but I remember there being an error and it not being successful. It was at this point that Clockwork Mod started being buggy. Starting to panic, I tried a factory reset through CWM. It formatted data no problem, but it would hang at "formatting /cache" until I turned off the phone. So I panicked some more and formatted system, emmc, data. (Not a smart idea, I know.) but it would hang when I tried formatting the cache again. And its been stuck in a bootloop ever since.
I read somewhere that you could use Odin to revert your phone to make it completely stock by flashing a kernel. I thought my prayers were answered! I was finally going to just start over and forget this ever happened! No. My computer won't even recognize my phone is plugged into it. (Yes, I have all drivers up to date. Yes, I am using Samsung Micro USB, and Yes, I have Keis installed.) Since my computer won't recognize my Phone, Odin won't.
* I can access Clockwork mod, and Download mode, but my computer won't recognize my phone when plugged in.*
I know it's a lot to read but I have tried so many things I'm just so discouraged about this whole thing. I know I'm a noob so please explain your answers like I'm 5. I don't understand most Android modding slang.
Thank you.
What version of CWM are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
6Seven said:
What version of CWM are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
v6.0.1.9 Touch
If you have an external sd card, load a rom on to it from your computer and then get your phone into recovery mode and choose to install from external sd card. See if that works. Also sometimes a cache wipe can take a while. Also don't panic and start doing things you know nothing about. I would recommend and ice based rom then figure how to get twrp recovery then move on to cm10. . If you can get past this, I can help you. Pm me
badaphooko01 said:
If you have an external sd card, load a rom on to it from your computer and then get your phone into recovery mode and choose to install from external sd card. See if that works. Also sometimes a cache wipe can take a while. Also don't panic and start doing things you know nothing about. I would recommend and ice based rom then figure how to get twrp recovery then move on to cm10. . If you can get past this, I can help you. Pm me
Click to expand...
Click to collapse
Ok, I will see if I can get an ICS ROM onto my Micro SD. If it works I will PM you. Thank you.
I'm still open to more suggestions!
EDIT: The funny thing is, when my phone is in CWM my computer recognizes it and I can mount USB storage, but won't recognize it while in download mode. Weird.
don't use superwipe with cwm 6+. it will break your recovery and cause a bootloop.
also it seems that a lot of people have problems with cwm 6.0.1.9 and it seems like it doesn't wipe properly so i would recommend latest twrp or sk8terwitskil's cwm. i think that's what happened with aokp and why you were having so much fcs.
merrygocow said:
don't use superwipe with cwm 6+. it will break your recovery and cause a bootloop.
also it seems that a lot of people have problems with cwm 6.0.1.9 and it seems like it doesn't wipe properly so i would recommend latest twrp or sk8terwitskil's cwm. i think that's what happened with aokp and why you were having so much fcs.
Click to expand...
Click to collapse
Duly noted. Thank you for the info, really helps.
also have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1513359
have you tried removing your battery and see if that will help your computer recognize your phone? i don't know if it will work or not but try. :laugh:
merrygocow said:
also have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1513359
have you tried removing your battery and see if that will help your computer recognize your phone? i don't know if it will work or not but try. :laugh:
Click to expand...
Click to collapse
Yes, that is what I was referring to here:
I read somewhere that you could use Odin to revert your phone to make it completely stock by flashing a kernel. I thought my prayers were answered! I was finally going to just start over and forget this ever happened! No. My computer won't even recognize my phone is plugged into it. (Yes, I have all drivers up to date. Yes, I am using Samsung Micro USB, and Yes, I have Keis installed.) Since my computer won't recognize my Phone, Odin won't.
Click to expand...
Click to collapse
Battery pull didn't work either. :/
UPDATE: I've tried installing 3 different ICS ROMs from the external SD via CWM but they all seem to freeze 3/4 through the install. After about 5 mins of being frozen the phone reboots and the bootloop just comes back. Once again I have nowhere to go. I'm lost.
If anyone has more suggestions, please share!
i don't know where i read it but i just remember now that someone said kies and odin are incompatible. so maybe that's why odin couldn't detect your phone? kies might have been running in the bg.
so i would uninstall kies and driver. restart comp. then download and install just the driver from samsung website. then put the phone into download mode and connect to pc. see if that will help.
if not, i don't know lol. usually i would suggest flashing to twrp but i don't know how well that's gonna go over a broken recovery.
I would suggest flashing TWRP recovery 2.3.3 and try and flash a ROM again after....CWM has gone downhill in my opinion.
Here is the TWRP thread http://forum.xda-developers.com/showthread.php?t=1768742
Or download GooManager app and install that way
And do not use any cache wipe scripts with this.
Sent from my SGH-T989 using xda premium
You need to have computer install odin driver while you're in download mode before odin works. Try this wipe cache, wipe dalvik, wipe data/factory reset, format system, format cache and format system. Then flash new rom in recovery.
Sent from my SGH-T989 using Tapatalk
RESOLVED!
Funny thing is, I just plugged in my phone to a computer running Windows 7 and Odin recognized it! I guess my XP at home doesn't like phones. From there I flashed a stock kernel and VIOLA! Phone is out of the box new! Now I'm very weary about installing a ROM again.. I don't want to go through that ever again. Maybe i'll do some more research before I molest the software's insides.
Thank you everyone for your contributions!
Try recovery from sk8erwitskil, it's the only one that seems to work w/ my Hercules. I had similar problems to what you were experiencing and it's the only recovery that worked for some reason. I am on a GNex now so take that for what it's worth. I'll pull out the Herc. tonight when I get home to update to the CM10 latest nightly, it's been a while.
I recently learned to flash,
So I used TWRPV to flash coz i cant access the recovery mode becoz of rooting.
1.Flashed Slim Bean. Worked perfectly.
2.Try to flash jellybam. Got flashin failed.
3. Reflshed Slim Bean.
4. Tried to flash Miui rom. Again got error, after googling i found that i have to delete two lines from the script in miui rom with note++
I did that but not worked, then i myself checked the slimbean script, and deleted some more lines from miui script and flashed, still not worked.
5. I did same to jellybam. Then one of jellybam rom worked.
6. Now after reboot some times note 2 switch off itself when in pocket or in table. Or sometime while charging with big battery on screen with stuck tiny round circle. I have to remove the battery to switch on.
and i can't turn on bluetooth also USB not working. In pc device manager when i connect phone to pc via usb it shows CDC COMMUNICATION INTERFACE (7 times), and Com neon Suspend (1 Times)
7. Now using slimbean but problem is still there.
Any idea what happened to my n7100, is my phones efs corrupted, or soft/hard bricked,
I don't have any backups.
Can anybody please help me. I posted it here coz I can't find the same problem anywhere. There arevsimilars but they are different.
And bad English coz I'm Apatani.
Sorry for that.
My note 3 was SICK from some times (from 7 Months)
Some said it was EFS corruption. my problem was occurred because I flashed my N7100 with MIUI rom built for Galaxy S3.
My Bluetooth was not turning ON (Blank in bluetooth adress), Usb not workin with PC, turning of or Freeze while phone sleeps or auto lock.
Tried many things Flashed different Modem or Kernels, Flashed all of the custom roms available for N7100, Flashed Stock from SamMobile site.
and Lost hope... then I continued my daily life with my N7100 (using Red EYE sleep disabler)
But now today I already using Ditto Note 3 v.3.0 (Used v.1.0,v.2.0,)
today Flashed Ditto Note 3 v.3.1.1 with aroma
Selected everything in Aroma Inataller (Including Updated Modem)
then in First Boot my N7100 Freezed while i was entering my Wifi Pin First Device Setup
Waithed for more then 1/2 hour but still Freezed...
then i rebooted it with removing my N7100 Batteries
then again Boot and it Widened my eyes, my mouth was open, and i was Smilin...
My N7100 Bluetooth was turning ON, my USB is connecting to PC without any secret code for UART mode, my Phablets screen turned off, I waited for around half Hour and then i Pushed my Home Button and it respond and turned on the Screen.
Firstly your very brave to do this or your too Rich to afford a new device if you brick it .
Now firstly Please dont make any changes to the existing Rom that you have downloaded seeing other Rom scripts ,
Now before flashing any rom go trough the OP to understand what OP has mentioned about flashing.
Dont Refer to Google refer to ROM OP OR THREAD any question you have post it there so you will get quick response.
aukhahaven said:
Firstly your very brave to do this or your too Rich to afford a new device if you brick it .
Now firstly Please dont make any changes to the existing Rom that you have downloaded seeing other Rom scripts ,
Now before flashing any rom go trough the OP to understand what OP has mentioned about flashing.
Dont Refer to Google refer to ROM OP OR THREAD any question you have post it there so you will get quick response.
Click to expand...
Click to collapse
Thanks...
But I'm confused, what should I do now...
And I don't have that much money to afford another device like this one...
Is there any fix or solution for this problem...
bullooka said:
Thanks...
But I'm confused, what should I do now...
And I don't have that much money to afford another device like this one...
Is there any fix or solution for this problem...
Click to expand...
Click to collapse
Well since your phn is acting weird better flash stock rom via odin and see if the prob persist if all is fine then gv a fresh start flashing recovery and stuff and use philz recovery for flashing if it acts weird than just make the flash counter 0 and take it to service center for precise details go though ketan thread
bullooka said:
Thanks...
But I'm confused, what should I do now...
And I don't have that much money to afford another device like this one...
Is there any fix or solution for this problem...
Click to expand...
Click to collapse
Download Stock ROM,
Flash it it Via Mobile Odin or PC ondin,
Once flash completes Boot into recovery and do a Factory Reset+User data ,this will wipe everything on your device memory .
and then tell which rom you want to flash ill guide on how to do it.
aukhan said:
Download Stock ROM,
Flash it it Via Mobile Odin or PC ondin,
Once flash completes Boot into recovery and do a Factory Reset+User data ,this will wipe everything on your device memory .
and then tell which rom you want to flash ill guide on how to do it.
Click to expand...
Click to collapse
Okay.
I'll inform u when i'am ready...
In my place broadband or network is not that good, to download stock ROM it will take some time.
And thanks for helping me.
bullooka said:
Okay.
I'll inform u when i'am ready...
In my place broadband or network is not that good, to download stock ROM it will take some time.
And thanks for helping me.
Click to expand...
Click to collapse
no problem any time
aukhan said:
no problem any t
Click to expand...
Click to collapse
Actually, I think I found out what exactly happened to my note 2.
The ROM I tried to flash was for s3 (MIUIv5 I9300 Note 2 Edition 3.6.21 by @muchopoli83)
This ROM was flashed after removing the two lines from updater script, the assert lines.
But after flashing my phone didn't started so I changed the ROM.
So, what should I do. Is stock ROM still important.
If yes can u please give me the link.
I found one with pit file in xda but that link is not working
And some guys with similar problems are talking that every stock ROMs are not working for problems like this.
bullooka said:
Actually, I think I found out what exactly happened to my note 2.
The ROM I tried to flash was for s3 (MIUIv5 I9300 Note 2 Edition 3.6.21 by @muchopoli83)
This ROM was flashed after removing the two lines from updater script, the assert lines.
But after flashing my phone didn't started so I changed the ROM.
So, what should I do. Is stock ROM still important.
If yes can u please give me the link.
I found one with pit file in xda but that link is not working
And some guys with similar problems are talking that every stock ROMs are not working for problems like this.
Click to expand...
Click to collapse
You could be in serious trouble since youve flashed s3 Rom just keep your fingers crossed thinking that its not corrupted your EFS folder
what Model is your device N7100 or n7105 which 1 >?
aukhan said:
You could be in serious trouble since youve flashed s3 Rom just keep your fingers crossed thinking that its not corrupted your EFS folder
what Model is your device N7100 or n7105 which 1 >?
Click to expand...
Click to collapse
My device model is N7100,
and today I found out that my Bluetooth is also not working, I can't switch it on.
shhbz said:
Well since your phn is acting weird better flash stock rom via odin and see if the prob persist if all is fine then gv a fresh start flashing recovery and stuff and use philz recovery for flashing if it acts weird than just make the flash counter 0 and take it to service center for precise details go though ketan thread
Click to expand...
Click to collapse
Actually I accidentally flashed the wrong ROM . S3 I9300 ROM in my Note 2 N7100.
Is there any other ways to fix this
aukhan said:
You could be in serious trouble since youve flashed s3 Rom just keep your fingers crossed thinking that its not corrupted your EFS folder
what Model is your device N7100 or n7105 which 1 >?
Click to expand...
Click to collapse
My model is N7100.
Can you tell me what happened to my note2, efs damage or soft/hard bricked
And what should I do.
Please tell me.:crying:
Still got the problem
Still got the problem and cant find any solution
anybody any idea
Simply go to recovery wipe everything including format_system,
then choose any rom from N7100 development thread as your suitability .
and flash in recovery as per instructions given in OP
Then tell here what happened
looks like efs croupt no worries just flash stock rom from odin then root it with cf-root method
use triangle away to remove the flash counter and then reboot unroot from su app and ur good to go to service center
just tell them i updated this phone to latest from ota and it failed iam when it restarted there was no cellular
bullooka said:
Still got the problem and cant find any solution
anybody any idea
Click to expand...
Click to collapse
Do you have GSM network?
Flash Stock ROM via PC Odin v3.09 and use re-partition and Nand erase all with PIT file, Freset Autoreboot.
After flash complete everything must be ok.
I had the same problem few weeks ago. I also tried to flash alot of ROMs but same problem exist. found a solution to this problem yesterday this is what I did
1. Download leaked 4.3 it will take time because the file is 1.2gb
http://forum.xda-developers.com/showthread.php?t=2499794
2. After download flash it via Odin in pda. Make sure auto reboot and f.Reset time only have check.
3. If the flash fails, it's ok but make sure it already flashed the radio and modem.
4. Reboot again in download mode then flash Philz recovery
5. Reboot in recovery mode then flash slimbean rom or any rom you prefer.
6. Install gapps
7. Wipe cache and dalvik
8. Reboot and your ok now
I'm in slimrom build 2 now. Bluetooth is ok and no more reboot when phone sleeps after few seconds.
Hope this helps.
Sent from my GT-N7100 using xda app-developers app
taticuio said:
Do you have GSM network?
Flash Stock ROM via PC Odin v3.09 and use re-partition and Nand erase all with PIT file, Freset Autoreboot.
After flash complete everything must be ok.
Click to expand...
Click to collapse
Got the GSM, WIFI is also OK but bluetooth,USB and reboot on sleep. but what re-partition and Nand erase work for and what is PIT file and where should i get it
any help
Still got the problem
Ok i'll try the leaked version and thanks for reply
bullooka said:
Got the GSM, WIFI is also OK but bluetooth,USB and reboot on sleep. but what re-partition and Nand erase work for and what is PIT file and where should i get it
any help
Click to expand...
Click to collapse
Never try to touch or else you'll get a big problem.
Sent from my GT-N7100 using xda app-developers app
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
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