Hello guys i'm very new to SGS2 T-989 ...and recently got this 2 year old t-mobile sgh t989 ...and it worked fine for few day..till i trid cm11 as first custom rom on it..it too worked well until i used camera...it rebooted itself ...i thought it was because cm11 is nightly ..so i tried carbon rom ...it worked quit fine for a while......for some reson it to started rebooting after a while ..lastly i tried cm10.2 stable ...it worked quite good i updated with cm updater then after it worked good and affter a while it too strted rebooting ...i thaught of power button failure and replaced it too....and finally flashed stock JB 4.1.2 rom ...it works quite well even till now..but the problem is that i cant install custom roms on it ...any help would be honey in my throught...does any one have the issue...???.....................finally got to tell i'm new to this mobile not for customization of roms ..i tried every thing wipe/data/F.Reset/Delvik/System...and even trie super/dark wipe script too.....hmm the matter is unable to install custom roms/////
What recovery are you using? (latest is 2.8.1.0) get it here! Flashable .zip HereWich Gapps? . . . Stock 4.1.2 have some firmware upgrades so maybe you're good to go now if not you might want to try installing stock via Odin (kill any Kies process before using Odin). Find stock rom Here! You will need to register to dwl. Ooh and dont use darkside wipes scripts as they are outdated, you can/will brick your phone. Just wipe system, data, cache, dalvik and .android_secure
I'm using cwm 6.0.4.3 ...and I flashed stock rom the latest ...I have root and cwm backup too...stock rom works completely perfect ....prblm is with custom roms..
Keep a copy of cmw and your backups just in case and try flashing using twrp. Also read this thread , "Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin."
I've used odin 3.0.7 to falsh stock t989 latest jb 4.1 ...stock rom works 100%....problem is with 4.2+ roms
Ok was just to be sure its not that.. did you try flashing with twrp??
Also what scheduler/governor are you using? I use sio/samsung (personnal choice) (stable, decent battery life, good performance) found out that some combinaisons crash the phone (reboot)
Just now installed twrp that u mentioned and took a backup....now I will try the cus rom process and tell u the result ...hoping this eleminates my problem...and one more thing...im just using stock rooted rom..had not done any changes with cpu governence...and have a decent battery..
Only problem is with KK and 4.3 Roms
I've changed the rrecovery to twrp latest and tried installing from CM9 worked ,
CM 10.1 even worked [4.2.2] :good: [camera crashes while using flash]
Tried 10.2 had bootloops.....whats wrong with 4.3+...help :crying:
Glad to hear that
Camera is known to crash when using the flash and battery is low.
About 10.2 idk .. maybe it has to do with CM itself (search in CM threads). Try some other roms/kernels combinaison. as long as you have a backup of a working setup you should be good. Personnaly i really liked hellkat w/diablo kernel (4.4.2) and Beanstalk w/wildkernel (4.4.4) but as they say , your mileage may vary.
K that's very helpful and ..tnx for ur sugession
Related
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
I got a bootloop before when trying to flash JB roms and what I did was restore to original state (using the bad flash recovery technique), and then not rooting it but installing cwm through Odin and dirty flashing the Rom in cwm. Once it flashed I used it for a few to make sure that everything was working correctly. Then I got the goo manager app and got twrp. After that I followed all the steps in the OP (Jedi jelly) and flashed the Rom. Now I'm running Jedi jelly 3.1 perfectly. Hope this method helps.
Sent from my SAMSUNG-SGH-T989 using xda premium
djtreo said:
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
Click to expand...
Click to collapse
are you using darkside scripts to wipe? because they will cause bootloops
skinsfanbdh said:
are you using darkside scripts to wipe? because they will cause bootloops
Click to expand...
Click to collapse
is there any way to reverse the loop that the darkside wipe is causing?
it REALLY sounds like the recovery u are using is TOO OLD. Make sure u are using the latest version of twrp (2.3.3) to flash all jellybean roms.
TWRP is backwards compatible and touch capable, so if you're worried about flashing GB or ICS ROMs it'll do the trick just fine
it is however a requirement for flashing all 4.1 ROMs.
Basic install instructions:
make sure u have root
download goo manager from play
open > menu > install open script recovery
agree to everything, but make sure t989 is in the downloaded image name
reboot to recovery u should see twrp
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Wipe
Data
Cache
Delvik Cache
and Factory Reset.
Make sure you're flashing the correct GApps for android 4.2.x
Flashing a kernel has nothing to do with a status 7 error.
A status 7 error points to a outdated recovery or bootloader.
You should get ANY errors.
If you hate flashing why do it??
I honestly don't get that...
If you're here to make your phone to look "cool" you're in the wrong place.
Galaxy S3 / AoCP / V4A / Turbocharged
duoblade said:
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Click to expand...
Click to collapse
I would get TWRP recovery.. wipe dalvik / factory reset. and re-flash your rom.. I'm on Rogers as well and the status 7 error means that your recovery / bootloader is outdated.
So start by getting the most recent TWRP. I got it from goo.
btw: if you don't like custom rom, i suggest going to the sammobile site and getting your factory firmware. Use Odin to reflash back to stock. That should solve your hiatus towards custom roms...
correction
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
duoblade said:
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
Click to expand...
Click to collapse
sure but its fine custom Roms can be a Pain in the A$$ thats why am running stock rooted stable, great battery life, fast like custom roms, everything is perfect give a try with stock rooted no issues or problems like custom roms
Synergy Rom 4.1.2 w/ Ziggy Kernel using ATT Galaxy S3
HAPPY ROOTIN :cyclops:
Hey guys=)
So yesterday i installed (after an EFS Backup) a 4.3 Custom Rom (JoelDroid) on my Galaxy NOte 2 N7100. It was on a rooted 4.1.2.
The rom booted everythign looked fine. I also wiped Data/factory resetted my device before i install the rom. But when i have to configure it the first time, it always crashed. So i made a full wipe and flashed the rom again (Philz touch btw the newst version). But the same thing again.
So i decided to flash a new ROM. Full reset, resetted caches and so on and the same problem again. My device boots up correctly but after 1minute or so it freezes completly. Cant press any buttons and so on.
The last try for me was to install a CM 10.2 (Asylum) version. This one is working properly. Had 1 or 2 crashes, but now its working fine.
But i dont want to lose the stock features.
Can anybody help me pls? What did i wrong? what do i have to do to get a proper functional MI6 4.3 rom on my N7100?
Thank you very much
Greets Marco
Have tried any other 4.3 rom? Steps u are following are absolutely correct btw..
If u using philz then u should choose the option "clean install befire a new rom" and manually format system,data,cahe and preload..this is a clean install.
Sent from my AweSoMe ?♥Note2♥?
Thanks for your reply!
Yes i used the option clean for New installation and i used 2 other 4.3 Roms too AS i mentioned. But at least i know now that my procedure was correct. Should i try another Rom? Or should i flash back to stock 4.2.2 (if its possible) via Odin?
Sent from my GT-N7100 using xda app-developers app
ok it looks like that the Asylum CM 10.2 is also not working. Crashes after some time too (every 1-2 hours) :/ really need help guys!
EDIT:
Ok i installed Stock 4.1.2 ROM via ODIN and now everything's working fine again. I think i will stick to this for some time now (have a prerooted version so root still there)
ive installed the multi rom manager for the sprintm8 ..after reading up on everything..its the latest test version pose to help with hanging up when booting secondary roms..i still freeze up bout everyother time trying to boot from the manager app to secondary rom..i tried flashing updated firmware from hboot ..the updated firmware was the one updated in aug..hope that was the latest..still have issiue..i have bad boyz sense as base rom with elementalx as kernal with patch..have pacman as secondary..everytime ive attempted to make changes like the kitkat sd card fix..or install xposed framwork..ive had to wipe data and start over cause after rebooting would just go black screen..thinking i bricked it..also tried flashing liquid smooth as third rom..did fine..but no mobile data or wifi worked..im sticking to aosp roms cause ive read they all mostly work although id love to have another sence based rom as well..but the ones i tried never booted..read how its possible to alter the zip then repack..but sounds to advanced for me..question is do i need to flash anotherr kernal in my aosp roms to get it all working..i know the base rom gets the elementalx kernal with patch....but do i need another kernal for other roms to get everything working..and why am i freezeing dureing booting up from multirom manager into the aosp secondary roms?
I've been trying for over a month to get wicked rom installed on my n3 n900t . I'm rooted bootloader unlocked with twrp installed. I've had no issue installing any other rom on this phone I'm currently running alliance 5.0 and resurrection remix 6.0.1 and they work great but I would like to see what wicked is like. ( what it does when trying to install ) OK I have the wicked rom saved to my SD card with 4.4.2 gapps I'll restore my phone to alliance rom which is 4.4.2 and is says in the install it needs to be a 4.4.2 bootloader to install wicked, I'll go into twrp do a full wipe data, delvic,system, wipe it out then install the ROM and gapps package and it'll start to do its thing then get to where it says aramullz xda ( something? ) the progress bar will stop and it'll self boot itself out of twrp and go back to alliance rom and which will be messed up due to doing a full wipe. I like to figure things out on my own that's the fun part but this one's got me. Thanks for any advice.
Did you use terminal or Samsung Phone Info app to verify the bootloader in the phone?
I installed compullsion kernel 4.4.2 before and that failed, tried installing it while flashing the rom and gapps that failed, tried the other older versions of wicked v5 and v4 and v1 they all act exactly the same. I even wiped the whole phone completely cause I got Pissed due to failure ( lol ) flashed a fresh AP in Odin and tried everything again and still failed. I'm in the process of trying to convert the zip file to a tar md5 but having issues that Odin won't except the files cause the ( tar archived ) and I did flash the 4.4.2 bootloader as well. I'm beginning to think wicked doesn't like me.
My bootloader info should be 4.4.2
fastjohnson said:
this the info now which is useless because I'm on alliance 5.0 rom so it originally came from 4.4.2 chainfire zip.
Click to expand...
Click to collapse
Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?
audit13 said:
Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?
Click to expand...
Click to collapse
No still nothing I've tried everything I even wiped the entire phone installed the B4 Odin files AP and BL and CSC then flash chain fires autoroot file and twrp. The phone was basically stock 4.4.2. I tried all 3 wicked zips V1 V4 V5 and they all reacted the same way. And I already grabbed these files from different locations to make sure I didn't possibly get a bad batch. I've got every rom to flash on this no problem. Pacman, RR, alliance, slimroms, any cyan rom, I've come to terms no wicked for me. Lol
Lol, finally got wicked installed via flashfire. Twrp wouldn't do it. Super happy really fast rom.
What versions of twrp did you try? Just curious.
Using the newest 3.0.2 I think. Btw wicked rom so far is the most stable coolest rom I've experienced so far. I forsee it as my daily.
I have seen reports of some people having issues with 3.0 and higher so I stick with 2.87 for my devices.
No I actually didn't catch that. Besides that it refusing to install the wicked rom I haven't seen very many other issues. Well sometimes when im restoring a rom in twrp when it boots itll sometimes not in stall a lot of Google Play stuff and the UI will crash and I'll have to restore it again. I actually like the look and the button placement better in the version your using.