lately, i have been trying to get my N7105 AT&T to upgrade from DN3 v3.1.1 to v5 or higher. im trying to flash using philz custom CWM. first off, making a backup with it of the currently working rom to fall back on.
first time attempting, id go into recovery, having the zip on external SD, wipe to factoy defaults, and then try to flash. the flash will complete, and then i reboot the phone. itll get to the samsung screen, and i left it alone for a good 10 minutes or more, but never gets past it. later i find instructions on flashing using philz here (thread was for N7100, but i figured flashing would] be the same steps).
Current setup (pulled from device info app)
Build: N7105XXUEMK5
Baseband: I317UCUBMK6
Bootloader: I317UCUBMJ4
Are there any special instructions different from the N7100, or do i need to update my specs?
Thanks in advance.
Related
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Info:
Computer OS: Windows 7 Ultimate (64-bit)
Firmware Version: PDA:LH1 /PHONE:LH1 / CSC:LH1 (TMB) - (Ver. 12.07.20.02) (current)
Binary: Samsung Offical (Kernal 3.08 ICS)
Build Number: IMM76D.UVLH1
ROM: Stock T-mobile Android 4.0.4 (before i flashed cyanogenmod9)
Baseband Version: T989UVLH1
Brand: Samsung
Model: SGH-T989 (hercules)
Type: Galaxy S2 X
Carrier: T-Mobile, USA
Country Code: 1 (USA)
Access Point: epc.tmobile.com
Odin3: v3.07
Clockwork Recovery: v5.0.2.7
Root: tmobilegalaxys2rootICS -> CWM-SuperSU-v0.87 (updated can't view newer version right now)
Cyanogenmod9: cm-9.1.0-hercules
Google Apps: gapps-ics-20120317-signed
spikeguy4 said:
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Click to expand...
Click to collapse
Hey! As of I know, you are not using a TOUCH recovery. Sad to say but a lot of ROMs will only work on TOUCH recovery, because they changed something in the Cache wiping that ain't screwing up with device or something (as I understood digging up a little bit).
Here is my advice, go with this for now:
MIRROR
It's v13.1 of Sk8er's recovery. Though I want to tell you, if you try to hardboot into it (what I mean is: hold +/- volume and plug in USB) it probably won't work since it doesn't work for me for a weird reason (I'm on v13.0 so I couldn't say for v13.1).
In EXTRAS you got the cache.wipe and the super.wipe of TDJ.
And another thing I think you should know about this device is HOW TO FLASH CORRECTLY.
Here is the way:
Make a backup (optional)
SUPER WIPE (using TDJ tools)
Factory Reset (wipes data/cache/.....)
Install your rom (without GApps)
Reboot phone.
Wait for let's say 10 minutes (optional as well I don't do it but it's recommended... Just reboot, and when you see no bootloop, go back to recovery for next)
Wipe cache/dalvik (without using TDJ but only from recovery touch)
Install gapps.
Reboot.
if you just update your rom, like going from a nightly to another nightly, no need to follow this. Just wipe cache and dalvik using recovery touch, and you are good going.
Cheers!
I'll try it!
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
spikeguy4 said:
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
Click to expand...
Click to collapse
My friend here is a flawless recovery with 0 issues if you are worried about the one above TWRP 2.2. Also stay on one site for everything and may I suggest xda only. Do not venture off not that the other sites are issues just that you will confuse yourself although rootzwiki is just as good.
There is plenty of How To's here in xda that you do not need to be confused, confusion comes when you start asking others there opinions and take bits and pieces from all of them... Good luck and feel free to pm me if you need any further help... Just please read up before you do anything
These are the exact instructions from CM on how to install their rom: did you follow these instructions
Installing
How to INSTALL from another ROM (DO NOT SKIP ANY STEPS!):
Be sure to back up your current ROM!
Update your radio to the above recommended version if you have not already done so. (See the list below)
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON NON-TOUCH CWM RECOVERY: Install darkside-wipe-cache-only.zip (which fixes bootloop due to bad /cache format)
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
Awesome!
Wow that's exactly what i was looking for! Thank you! I just flashed a stock rom to go back to the start. I'll begin the process over again following these steps. The only issue is that the radio update section in the guild no longer exists. Is it ok to go on without the radio update? Or will this cause issues? If so is there a mirror for them?
SOLVED!
OK! I'm all set now. I had to use the full wipe as well as the cache wipe after install and the bootloop was resolved. The bigger headache was when kies failed at updating the firmware so i had to do an emergency firmware flash. Any way i have clockwork, root with SuperSU, cyanogenmod9.1.0, and the latest google apps! Plus its backed up now! YAY! Now i just have to configure it to how i like and we'll be in business! Thanks for all your help guys! I really appericate it!
Last thing
I still need the radio update since the file no longer exists in your link. Everything is good but I don't have any wifi calling or features of that order. Which are important in keeping my usages down and getting coverage in my house and otherwise bad areas. Where do I get this and would I just install it via CWM? Thanks again!
Hey guys, I was playing around on my phone, and I downloaded something off of 4shared (just a game) and it crashed and made my phone freeze. I then held my power button and waited for it to boot but now im stuck in a bootloop with the stock telus rom... is there anything I can do that wont wipe everything on my phone? Oh and I can get into both CWM recovery and download mode.
I gave it some more time to startup and it pretty much factory reseted my phone. I get that thing to setup my phone after startup. Everytime I turn my phone off it goes back to this screen and my phone restarts. If I surf through the files of my phone, it shows I still have everything but It doesnt show any of my apps or anything.
Hey guys/gals,
I recently bought a Koodo Galaxy s2x. After a few weeks I looked online and saw that there were some JB Roms for my phone. I couldn't resist and tried to flash one after rooting. I didn't have many problems with it, but there were some glitches that started to bug me, so I decided to see about going back to stock (I should have done this first I know). So then after hours(many) of searching, the best I could find was a T-Mobile stock Rom I decided to try and flash it (both times via odin). I also read somewhere that I should use darkside superwipe to clear my cache, so I tried that, but ever since that CWM stopped working on my phone. anytime I tried to do any back up or anything it just froze, and I had to hard boot. Finally I just tried flashing T-Mobile stock ICS, and Odin said "Failed". I decided to just unplug my phone, as I thought I already screwed it up, but after rebooting, the T-mobile Rom worked. I don't understand why it works fine if the Flash Failed. Now, I can no longer connect to kies (I'm hoping official JB will be shipped soon!), and I am wondering if I can somehow return to a stock Koodo Rom, and if it will connect to Kies again, as it previously had. I have looked a lot and have not found anything that I fully understand. I'm not overly experienced, which is why I should not have flashed to begin with. This is the closest thread I have found to help me, but I don't fully understand what all I need to do:
"Haven't seen anyone shared this yet.
Here's the KOODO ICS 4.0.4 stock ROM I used CWM to flash to stock after I tried the custom ROM.
h t t p s : / / sourceforge.net/projects/koo...d.zip/download
I also flashed DARKSIDE.SUPER.WIDE before I flashed this or you can used CWM Recovery 6.0.1.2 to wipe system and cache."
Is it possible for me to get back to stock phone? and still connect to Kies? and then possibly upgrade to JB through Kies if Hercules ends up receiving it?
Thanks for any help you can give me. Here is all my current phone info incase this helps:
Model:
SGH-T989
Android Version:
4.0.3
Baseband version:
T989DTLLG2
Kernel version:
3.0.8-perf-T989UVLE1 -CL508451
[email protected] #1
SMP PREEMPT Sun May 6 15:07:07 KST 2012
Build number:
IML74K.UVLE1
Thanks.
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: https://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
arcsine said:
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: h t t p s ://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
Click to expand...
Click to collapse
That link doesn't work, it says cannot find page. Also, my phone is currently not rooted, does it have to be rooted to flash from recovery? if not what do I do to flash from recovery? I know how to get into recovery, but after that do I use 'apply update from external storage'? Do I have to wipe the cache first?
Thanks.
PS: I just want to be able to get back to stock for now. At least until I learn more about flashing Roms. There is still lots for me to learn, like kernels, radios, Nightly's for official Roms, or even how to properly flash a rom without feeling lost. If I know a way to get back to stock comfortably, It will give me more reason to try some other Roms (once I learn how).
Here is a working link to the stock Koodo ROM: http://sourceforge.net/projects/koodostock/files/KOODO_SGH-T989D_Stock_Signed.zip/download
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted: http://galaxys2root.com/t-mobile-galaxy-s2/how-to-root-icsgb-on-t-mobile-galaxy-s2-sgh-t989/. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
arcsine said:
Here is a working link to the stock Koodo ROM:
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted:. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
Click to expand...
Click to collapse
Thanks a ton... Worked perfectly! I'm hoping it will connect to Kies once again.. I'll let you know if it works.
Unfortunately, I still can't connect to Kies.. It just sits at the Loading status (for like 10-15 mins). But At least I don't have all of the T-mobile apps and stuff anymore!
Reposting as this was posted in wrong section:
Hi
I have been trying to upgrade from CM 10.1 (build 03212013 ) to Paranoid Android 4.4, since I see the new version has BLN support (I'd stuck with the old CM for so long due to this).
Anyways upon trying this I discovered I had to (always ran clear cache, and ran the T989 script super -wipe)
- update my modem to the latest t-mobile - upgraded to the latest which is needed - UVMC6
- was trying to install with CWM 5.8.x - but it would just 'hang' at "installing ZIP" further research indicates I need to upgrade CWM
- Upgraded to CWM 6.0.4.3 per more searching, tried erase flash, just hangs - further research indicates this CWM has a known issue
- used ODIN to goto TWRP 2.7 - flashed, and booted, tried numerous times hangs at "teamwin' screen when trying to boot into recovery
Ended up giving up and Odin flashing back CWM 5.8.1.3 and loading my old CM 10.1 build again
Anyone have any hints why this is so difficult for me?
Need some help if possible please!
thanks
Jonathan
Found work around
Just want to update
I managed to find a work around of sorts. I needed to restore my phone back to CWM 5, and to do that I needed to use ODIN to flash it.
After flashing CWM5 back to the phone, I was able to restore previous ROM (CM mod 10.x), and boot up. After that I used the rommanager to re-install CWM 6.0.4.3, and reboot the phone into recovery.
When in recovery I went to mountand storage, and formatted , /cache, /system and /data. After doing that I choose to install ZIP from SDcard, and selected the Parandoid Android 4.4.x I was trying before. This completed, and installed without any error messages.
Hopefully this helps someone else out.
Thanks,
Jonathan
Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787
Hi,
I will have your thread moved to your device section.
Good luck!
Superbia Thema said:
Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787
Click to expand...
Click to collapse
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.
I downloaded cyanogenmod and gapps from those websites, but I'll flash twrp again to give it another try. Yea I was goanna install android lollipop but the bootloop gets me every time...
Sent from my SM-N900T using XDA Free mobile app
bobbyphoenix said:
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.
Click to expand...
Click to collapse
Welp I went ahead and flash another rom and it worked so I'm guessing I either have the wrong files or something is wrong with my phone. However, dompop works amazingly to thanks for the help!!!
Hey Guys,
Am new to this "flashing" scene, any help towards giving new life to my ageing Galaxy Note II would be grate.
I wanted to give my Note II new life with the Blisspop ROM as i heard great reviews on it.
I installed TWRP and took a Nandroid backup prior to flashing. All went well there.
Rebooted to recovery.
Next I wiped:
1. Dalvik Cache
2. Cache
3. System
4. Data
5. Internal
and tried flashing the ROM (Bliss-v6.2-n7100-OFFICIAL-20160416-0235.), it completed successfully and also flashed GApps and that too was successful. So i was prompted to reboot my phone (N7100) and Bliss started booting (I was so damn excited), it was preparing my apps (90+apps approx, lees than 100 for sure), competed this process and again the "Bliss" boot came up. I thought it might go away in a while but then again and again and again it kept happening.
Anyone here using BlissPop ROM with successful implementation?
Is it mandatory for my N7100 to be rooted to install a ROM..? If yes, is it safe for me to root it now as I have already installed TWRP recovery.
Any help to fix this would be useful guys.
Additional Device Info:
Android Version: 4.4.2
Baseband Version: N7100DDUFND1
Kernel Version: 3.0.31 - 3569041
Build Number: KOT49H.N7100XXUFNL1
black.marque said:
Hey Guys,
Am new to this "flashing" scene, any help towards giving new life to my ageing Galaxy Note II would be grate.
I wanted to give my Note II new life with the Blisspop ROM as i heard great reviews on it.
I installed TWRP and took a Nandroid backup prior to flashing. All went well there.
Next I wiped:
1. Dalvik Cache
2. Cache
3. System
4. Data
5. Internal
and tried flashing the ROM (Bliss-v6.2-n7100-OFFICIAL-20160416-0235.), it completed successfully and also flashed GApps and that too was successful. So i was prompted to reboot my phone (N7100) and Bliss started booting (I was so damn excited), it was preparing my apps (90+apps approx, lees than 100 for sure), competed this process and again the "Bliss" boot came up. I thought it might go away in a while but then again and again and again it kept happening.
Anyone here using BlissPop ROM with successful implementation?
Any help to fix this would be useful guys.
Additional Device Info:
Android Version: 4.4.2
Baseband Version: N7100DDUFND1
Kernel Version: 3.0.31 - 3569041
Build Number: KOT49H.N7100XXUFNL1
Click to expand...
Click to collapse
Damn.. 28 views and not a single hommie ain't bothered to respond..
Do other custom ROMs run properly on the phone?
Root is not required to flash TWRP or a custom ROM. Root is only required if you want admin privileges on the phone.
audit13 said:
Do other custom ROMs run properly on the phone?
Root is not required to flash TWRP or a custom ROM. Root is only required if you want admin privileges on the phone.
Click to expand...
Click to collapse
I have never tried any custom ROMs on my N7100, so I really can't comment on that.
Any solution to this..?
Also which version of TWRP is recommended for N7100..?
Flash philz recovery 6.46. Go to mounts and check if u can mount data , preload , cache etc. If u see the error unable to mount preload or data or cache. Click on format data, preload or cache or whatever that shows the error. Once u are able to mount every partition go and flash the rom. This usually solves 90% of all problems so far.
I recommend starting with TWRP 2.87.