Related
Hey guys, check it out. I just figured out how to get into clockwork recovery, and assuming and going about flashing a rom just like I would on my evo, I go ahead and download a rom for the epic, flash it, and it works fine. So it loads up like normal after a flash n reboot, and it kept saying no service... so I was like... uh... weird.. so I booted back into clockwork and tried nand back to the backup I did before flashing anything, of course... but I started getting an error saying it couldn't open recovery.log and now it freezes restoring at saying "lost+found" .... so I pull the batter, and now it just automatically revolts to clockwork all the time, and trying to boot the system normally... I'm not using CWM 3+.. rather the older 2.xx ... any ideas?
It's hard to understand your writing. I think the best thing you can do is use Odin to flash back to stock and start over. You didn't say what version of android you were on but if it's dk28 did you flash the modem?
What rom did you flash? I take it you were on stock di18 before?
Flashing a rom based on one of the leaked froyo builds without also flashing a modem could cause the initial problem.
And nandroid doesn't backup or restore the kernel, so using that to restore still leaves you with the kernel of the rom you flashed before, which can cause problems across build versions.
You're best bet is to odin back to di18 and start again.
musclehead84 said:
It's hard to understand your writing. I think the best thing you can do is use Odin to flash back to stock and start over. You didn't say what version of android you were on but if it's dk28 did you flash the modem?
Click to expand...
Click to collapse
Thanks a bunch, I know I re-read my post and was like.. man I wasnt descriptive at all... LOL, but I checked out this Odin, and TBH i have NO idea what all this stuff is for the Epic, only doing it to fix the booboo I did on my g/f's phone I have the Evo so its totally different stuff almost... Anyways im back to stock, now I need to read up before screwing around again .
i didnt see anyone having this problem but got my gn and unlocked it yest, i came fr evo3d and we used to wiping everything n cache n dalvik so i tried to flash my first rom and im getting error " error in /sdcard/toro_aokp_b8.zip(status7) installation aborted assert failed:getprop(ro.product.device==toroII
i thought it was that rom but i tried flashing another rom and getting same message , if someone can help i appreciate it, i came fr the evo3d left sprint after 11yrs and woow what a difference in network, awesome network but im spoiled with rooting my ogevo n evo3d lol i love this phone hope i can fix this issue
Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?
RTContent said:
Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?
Click to expand...
Click to collapse
k first rom i tried AOSP 4.0.3ANDROID OPEN KANG PROJECT-TORO BUILD8 so i wiped data factory reset and cache n dalvik and flashed the rom, it looks like it starts to flash but aborts with the message above, then i restored my nan backup rebooted and went back to cwm to reflash the second time around i only wipe data factory reset cuz thats what the op says to do on his thread so i only wipe data factory n flash the rom still same error, so i went to try another rom GUMMYNEX 0.2.3 and i did the same process with both im following the steps their stating in the op in have cwm
From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?
RTContent said:
From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?
Click to expand...
Click to collapse
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve
Flip35 said:
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve
Click to expand...
Click to collapse
sure you are using the lastest CWM???
sure you are rooted??
did you try downloading the files from another puter??
i think i might know what the problem is my cwm says 5.5.0.2 and im looking here at somebody posted in the development section for a cdma cwm and it says 5.5.0.4 could that be the problem? if so how do i redo my recovery, follow the same steps i did my first one, i downloaded and extracted the files to my c drive and opened cmd and typed the commands, can i do that again while having already cwm to flash the new cwm on top of the old one? if thats the problem
Download rom manager. Then you can flash it while your booted in android.
RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
how ive never flashed cwm using rom manager, u meand download the file of cwm5.5.0.4 putting in the root like i do any rom and go into rom manager and install?
No just download the app Rom Manager. It will download the latest version and flash it with a single click within this app!
RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
wooooord, aight RTcontent good looking out, i guess when u said it looks like it sound it was reading my phone wrong was right, i had a gms cwm, thanx man used rom manager and since i put the new cwm in my root of sdcard when i press install cwm it automatically update it without even booting into recovery but just finished intalling a rom and IT WORKED!!!! UR DA MAN im excited thanx
I have tried to flash a new ROM, but cmw were never able to flash it always being aborted. Yesterday tried to flash Darkside evo 3. Flash super wipe success, flash new baseband good, comes the rom itself aborted package not good. I thought it was just bad messages from cmw.Reboot the phone wouldnt reboot just hung,i tried cache wiped still not reboot, hung again. Any idea why? I just flashed the cmw again so i will try again. In the mean time any idea will be appreaciated
JugMod V 5.0,
2.3.6, 2.3.14
Possible bad download of the rom. Definitely won't boot after a superwipe. Did you make a nandroid?
Sent from my SGH-T989 using xda app-developers app
Yes, i did make a backup. Funny thing is, i am only able to install a new baseband, anything else is fail.
JugMod V 5.0,
2.3.6, 2.3.14
FwaZ said:
Yes, i did make a backup. Funny thing is, i am only able to install a new baseband, anything else is fail.
JugMod V 5.0,
2.3.6, 2.3.14
Click to expand...
Click to collapse
*my opinion*
your running gb, some of the newer roms are ics created, will cause conflict between the 2 hence why the non flash capable. i would recommend to update to ics and try again, make sure u nandro first in the event you wanna revert back to prior os and maybe that will solve your probs. hope this helps
sgs2:chimera bitten/ herculoid stout
3.0. perfection
I had this problem too both on My Vibrant and Galaxy Tab 10.1. I say odin to stock and do a clean install of the rom. that always seemed to fix it for me
Check the md5sum and see if it matches before flashing any rom thats very important.... Or what cwm version u using??? Cause the touch cwm has some issues so i changed to the non touch cwm its more secure
Sent from my SGH-T989 using xda premium
if you want, do what i did, i restored stock ics and cleaned up my phone fully as from factory. started from root to flashing all the stuff all over, now im on a clean sd card( backedup all the external sd on my pc) so i have tons of room to play with. hope this helps
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