Failed to root Galaxy S8 + 955F Exynos International - Samsung Galaxy S8+ Questions & Answers

So i followed this video: https://www.youtube.com/watch?v=yqhdq_A47DY&feature=youtu.be
I did exactly everything he does in the video, but i always ended up with the same error upon booting.
It would say something like "verification failed. unable to restart your device. the integrity verification has failed.you need to reset your device to factory default settings."
I tried the method multiple times but the same error shows up.
Any idea what could it be? Thank you!:good:

Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.

Hello andresg97,
have you tried to follow the instructions as shown in the TWRP Thread?
At least you should be able to boot into recovery, from there you can install TWRP and the the only thing you need to get a working phone back is a ROM, the Renovate ROM works fine for me.
The Tools and ROM I mentioned:
TWRP Thread: https://forum.xda-developers.com/galaxy-s8/development/recovery-twrp-galaxy-s8-exynos-t3595102
TWRP instructions for Installation: https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Renovate ROMThread: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040

M3ph15t said:
Hello andresg97,
have you tried to follow the instructions as shown in the TWRP Thread?
At least you should be able to boot into recovery, from there you can install TWRP and the the only thing you need to get a working phone back is a ROM, the Renovate ROM works fine for me.
The Tools and ROM I mentioned:
TWRP Thread: https://forum.xda-developers.com/galaxy-s8/development/recovery-twrp-galaxy-s8-exynos-t3595102
TWRP instructions for Installation: https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Renovate ROMThread: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
Click to expand...
Click to collapse
Thank you! It works fine, thank you very much!
To everyone else who had similar problems , FOLLOW THE GUIDE this guy is linking, it works perfectly, i followed two youtubers before asking here, one made me end up with a boot loop, and the other one made me end up with the error upon boot.

KingFoltest said:
Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.
Click to expand...
Click to collapse
I have to say I am somewhat surprised at your post. It does not reflect the general attitude that is usually so prevalent in this forum. I wonder why you even posted. All you did was condemn the guy for having tried something without offering anything supportive beyond your comment - "congratulations for having a brick." It would have been better if you just kept your thoughts to yourself if you don't plan on offering anything constructive.
Bricking a samsung device is actually pretty hard to do - and most issues can be overcome. Obviously some bricks are real bricks - but usually via Odin, there is a way to at least return the phone to full stock before either giving up or trying again.
Sorry, I don't mean to harp on you - but I just get frustrated when I see such negativity without any offer of help or support. Hope you never end up in a similar situation - and if you do, I hope whoever reads your post treats you better than you treated the OP.

andresg97 said:
Thank you! It works fine, thank you very much!
To everyone else who had similar problems , FOLLOW THE GUIDE this guy is linking, it works perfectly, i followed two youtubers before asking here, one made me end up with a boot loop, and the other one made me end up with the error upon boot.
Click to expand...
Click to collapse
I'm glad I could help, have fun with your phone

mocsab said:
I have to say I am somewhat surprised at your post. It does not reflect the general attitude that is usually so prevalent in this forum. I wonder why you even posted. All you did was condemn the guy for having tried something without offering anything supportive beyond your comment - "congratulations for having a brick." It would have been better if you just kept your thoughts to yourself if you don't plan on offering anything constructive.
Bricking a samsung device is actually pretty hard to do - and most issues can be overcome. Obviously some bricks are real bricks - but usually via Odin, there is a way to at least return the phone to full stock before either giving up or trying again.
Sorry, I don't mean to harp on you - but I just get frustrated when I see such negativity without any offer of help or support. Hope you never end up in a similar situation - and if you do, I hope whoever reads your post treats you better than you treated the OP.
Click to expand...
Click to collapse
I understand.. I must be furious at that moment how somebody could possibly do something to a brand new phone. I am sorry though, will keep my opinions to myself, if they aren't constructive.

KingFoltest said:
Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.
Click to expand...
Click to collapse
The only thing he shouldn't of done was follow a youtubers guide on rooting, all they do is read xda and make a video of it, should of came here first and asked questions, next time he'll know.

andresg97 said:
Thank you! It works fine, thank you very much!
To everyone else who had similar problems , FOLLOW THE GUIDE this guy is linking, it works perfectly, i followed two youtubers before asking here, one made me end up with a boot loop, and the other one made me end up with the error upon boot.
Click to expand...
Click to collapse
hello!
I had the same verification problem you had, and followed these steps to solve it.
I have wiped my s8, and flashed as well as initialized TWRP on my phone. Now in TWRP recovery I'm trying to transfer the Renovate flashable zip, but every time I try to transfer the file the transfer fails. Doing it by drag n drop in windows the transfer freezes midway, and then the connection to the pc is cut, and I have to reboot the phone to reestablish it. After that I have a corrupt zip in like 70 % of the actual size.
Doing it by push command in ADB gives me an error saying my device is out of space after transferring around 60-70%, even though there's ~52 gb free space.
Do any of you have any idea why this happens? I'm able to transfer other, smaller files to the phones internal storage. Is there some setting limiting what I can transfer?

mocsab said:
I have to say I am somewhat surprised at your post. It does not reflect the general attitude that is usually so prevalent in this forum. I wonder why you even posted. All you did was condemn the guy for having tried something without offering anything supportive beyond your comment - "congratulations for having a brick." It would have been better if you just kept your thoughts to yourself if you don't plan on offering anything constructive.
Bricking a samsung device is actually pretty hard to do - and most issues can be overcome. Obviously some bricks are real bricks - but usually via Odin, there is a way to at least return the phone to full stock before either giving up or trying again.
Sorry, I don't mean to harp on you - but I just get frustrated when I see such negativity without any offer of help or support. Hope you never end up in a similar situation - and if you do, I hope whoever reads your post treats you better than you treated the OP.
Click to expand...
Click to collapse
I felt exactly the same, and even irritated! Thanks for pointing it out to the guy in such a professional way

KingFoltest said:
Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.
Click to expand...
Click to collapse
You must be fun at parties. You should just leave xda with that attitude. I rooted day 1, no issues.
Sent from my S8+Rooted

Brava27 said:
You must be fun at parties. You should just leave xda with that attitude. I rooted day 1, no issues.
Click to expand...
Click to collapse
Same parties you always arrive late to? Sure thing mate

Does not work for me
M3ph15t said:
Hello andresg97,
have you tried to follow the instructions as shown in the TWRP Thread?
At least you should be able to boot into recovery, from there you can install TWRP and the the only thing you need to get a working phone back is a ROM, the Renovate ROM works fine for me.
The Tools and ROM I mentioned:
TWRP Thread: https://forum.xda-developers.com/galaxy-s8/development/recovery-twrp-galaxy-s8-exynos-t3595102
TWRP instructions for Installation: https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Renovate ROMThread: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
Click to expand...
Click to collapse
Hey! Can u help me please, it does not work for me! My skype is den170602

A little help please?
DKC11 said:
Hey! Can u help me please, it does not work for me! My skype is den170602
Click to expand...
Click to collapse
It doesnt work for me either... My first initial attempted install of twrp gave me a pass but the phone would not boot into twrp. It is stuck at the galaxy S8+ logo... I can boot into download mode and thats all... holding the power bixby and volume up buttons does nothing. I have tried to flash twrp several times now and keep getting a fail in odin. I have also tried flashing a stock rom several times as well but odin fails at that too... followed xda giudes for both procedures and no luck. Any ideas or help would be greatly appreciated... Thank You

Hi all,
I found this thread because I did the exact same thing.
I flashed TWRP via ODIN, and came up with that screen about data not being verified, only option was to click "Erase".
Thankfully, I powered down the phone, booted to Recovery (Samsung), and displayed:
"Appling Multi-CSC-, applied CSC-Code : TEL (Telstra Aus) blah blahblah..
Successfully verify for dmverity hash tree."
Rebooted, and all was ok again..
Nearly passed out from shock though.
I did a Helium backup of my app data, but not the other files on my phone, which I am doing right now!
Still not sure what I did wrong with flashing TWRP though. It flashed fine...

numloxx1978 said:
Hi all,
I found this thread because I did the exact same thing.
I flashed TWRP via ODIN, and came up with that screen about data not being verified, only option was to click "Erase".
Thankfully, I powered down the phone, booted to Recovery (Samsung), and displayed:
"Appling Multi-CSC-, applied CSC-Code : TEL (Telstra Aus) blah blahblah..
Successfully verify for dmverity hash tree."
Rebooted, and all was ok again..
Nearly passed out from shock though.
I did a Helium backup of my app data, but not the other files on my phone, which I am doing right now!
Still not sure what I did wrong with flashing TWRP though. It flashed fine...
Click to expand...
Click to collapse
Sounds like you didn't wipe data or flashing the dm-verity disabler. Look here for more info https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3

Sjant said:
Sounds like you didn't wipe data or flashing the dm-verity disabler. Look here for more info https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Click to expand...
Click to collapse
I thought that was for new install phones only?
I don't want to wipe my phone, I want to leave all the data on it if possible.

DKC11 said:
Hey! Can u help me please, it does not work for me! My skype is den170602
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
Follow the steps exactly step by step.

Enjoy!
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disablerhttps://build.nethunter.com/android-tools/no-verity-opt-encrypt/ , Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!

Hi all,
Please help me to root my s8+ through TWRP. Every time when I patch this via odin my phone says 'unable to restart your phone. the integrity verification has failed. you need to reset your device to factory default settings. this will erase all your data.'. I have thoroughly read this thread but nothing resolve my issue. I have the exynos model purchased from UK.

Related

[GUIDE] T-Mobile US One S - How to ROOT and flash ROMs

So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Worked great for me
Sent from my HTC VLE_U using xda premium
So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1
androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.
First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help
I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium
yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.
nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.
the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.
I sent you a PM, trying to find a solution.

[q] Help Boot Loop! WIND

I don't know where to post this, I'm coming here all panicked and retarded, so I'm apologizing in advance.
I literally bought my Galaxy S 4G from WIND (Canada) this morning. From what I understood, upgrading the OS was dangerous, all I wanted to do was root... I followed this guide: ht tp ://w ww.gal axyforum s.ne t/forum/off-topic-forum/5053-rooting-tutorial-here-posted-permission-t-mobile-galaxy-s-4g-gingerbread.html (remove spaces)
which I found in a post on these forums. Someone who also was on WIND said it worked fine for them... They were rooted. I foolishly tried it, everything seemed FINE. When I load CWM it can't mount my SD card. I don't know what to do, it's stuck in T-Mobile boot screen loop if I try to exit.. I literally just stopped crying. My dad is going to KILL me if he finds out I ****ed up the new phone I just bought HOURS ago. I don't know what the **** to do, I don't know what's wrong. I need help, please. Anybody know what I can do? I don't care about rooting, I just need my device to work. Please, someone, anyone with any idea, what should I do? I can get back into download mode, and CWM. Is there anything I can do there? There's a recovery guide pinned but it says it's for the T-Mobile version, which I read is the same, can I use that to fix my phone?
This is my first Android device, I've never owned one before. I don't know ****, I shouldn't have tried anything... I just got cocky and made a mistake. I'm usually very good with this kind of stuff. Please someone tell me if there's something I can do to fix this, please!
I'm sorry if I sound stupid, I'm trying not to, I'm just really panicky and stressed right now.
I've tried searching through the forums - I still am searching through them, I'm sorry if I missed a post that can help me.
EDIT: I found someone who is also stuck in a boot loop... He seems to have SD Card issues as well, but doesn't speak English very well, so I don't thing he was able to communicate what his issue was...
Quote:
Originally Posted by GMK63
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode.
Thank you in advance for your Help, for replying and offering to help.
I appriciate it. My phone is Mobillicity carrier just like wind .[/B]
Then, user bhundven replies to him saying:
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki...xy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Is what Bryan is saying my solution? I don't think he understood the SD Card mount issue. Does anyone know how to fix that? I really hope to hear from you guys ASAP before my dad catches on... Please. I really need help. I'll search more in the morning, it's 1 AM here.
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's true, just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Sent from my HTC VLE_U using xda app-developers app
lonoguge said:
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Thanks for the slaps, I needed them!
Yes! I think I am still able to get into download mode, atleast I was able to last night (After the loop issue). Also, I formatted (factory reset option or something?) my settings when I was in CWM last night assuming that would change it back to the way it was, or atleast fix the SD mount problem..I hope this doesn't cause any issues.
What should I do when I'm in download mode?
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's great news! It's nice to hear that someone who's phone was also messed was able to repair it.
lonoguge said:
That's true, *just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. *If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Click to expand...
Click to collapse
Where can I get these drivers? Should I download the latest version of Odin?
I'll try this as soon as I get back from taking my little sister to school.
I just want to say again, this is the SGH-T959W from WIND in Canada. It's apparently the same hardware as the SGS4G from T-Mobile, just different software. I hope this isn't a problem.
Thank you both for replying so soon. After tossing and turning in bed for the last 5 hours, barely getting any sleep, it's such a relief to read these posts!
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
getochkn said:
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!
I really didn't read enough, big mistake, I was just really cocky because I've modded almost every device I own (Wii, PSP, PS3, PS2 various and iDevices [mine, and friends]). Of course, they're all different (Not saying it's all the same thing! ), I just felt very confident because I've never had issues with anything before. At least this is a good learning experience, I've really been put in my pace. I always felt that bricking was something that happened to other people, it doesn't happen to me. I know that sounds stupid, but idk, that's just how I felt. I physically feel sick over this 'whole ordeal (Seriously), I'm such an idiot. >.<'
Thanks for the warning, I won't flash anything! I'm so relieved to hear that there's no permanent damage done, and to be able to speak to someone who's familiar with this specific problem and this specific model of the SGS4G, AND is willing to help me!
Do you know when you'll be able to help me? Of course, take your time, I completely understand that you have other stuff going on, I'm just wondering to see if I can maybe think of some cover up so my dad doesn't find out.
Also, I have a 14 day warranty, is it void now even though the root didn't work? I'm assuming it is.
Edit: Yup, if what jeffsf says is true, it's void.
jeffsf said:
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
Click to expand...
Click to collapse
I'm just very impatient sometimes. I really do enjoy doing this kind of stuff, it's fun for me. I just got really excited and wasn't thinking straight and just went out and tried rooting it. I've wanted an Android for a while now, and have always planned to root it to unlock it's full potential. I've never modded anything else day 1 (and never will again), this is the first time I've done this. I feel terrible about it.
Will do, thanks for helping, jeffsf.
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
hechoen said:
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
Click to expand...
Click to collapse
I feel like they might know. I'm willing to try it as a last resort, I'd like to give getochkn a shot first.
I'll tell my dad what happened after it's fixed. I just can't deal with him stressing me out about it more than I already am.
I will have a package probably tomorrow that will provide as detailed instructions as I can.
getochkn said:
I will have a package probably tomorrow that will provide as detailed instructions as I can.
Click to expand...
Click to collapse
Oh, wow! That's much sooner than I was expecting! Thanks for taking the time to do this for me, it really means a lot. Thank you so much getochkn!
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
getochkn said:
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
BagelBreath said:
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
Click to expand...
Click to collapse
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
getochkn said:
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
Click to expand...
Click to collapse
Thank you for the quick reply!
It worked! I really can't thank you enough! Thanks again for taking the time to do this!
I think it may have said "Uploading Pit" because it said it again this time, but it didn't encounter a problem when it did that.
I know I have 3 choices, the one I would like to choose is ICS. Would mind pointing me in the direction of an ICS ROM that's compatible with my device? I'm afraid to use something that may not work and mess up my phone again.
EDIT: Actually, I think I'll just stick with this. I just installed the twist kernal and the modem, everything works, I'm rooted and have recovery. I'd rather not mess with it until I'm more experienced with droids.
Thanks again everyone, especially you getochkn! I'm so relieved that my phone is working again! My dad didn't notice that I wasn't using the new phone I got, so I didn't have to cover up or anything.

[Q] Help with SGH-T959W only booting into recovery

Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log
bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave

[Q] Lg Ls620 (realm) custom recovery

I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
twtoned said:
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
Click to expand...
Click to collapse
Looking for one as well. I have not found one.
Recovery is actually preinstalled
I found this just tooling around. Use your favorite file browser, I used
Total commander. /system/vender/itson
The zip file is there. Hope this helps. (Rooted LG ls620)
Could you explain in a little better detail on what you mean Enigmatic177... I'm pulling my hair out Hehe
If anyone makes or finds a working recovery please post it.
Itson is a zip file that was installed after last update it has the basics to unlock the boot loader. I unpacked it used Rom toolbox pro rebooted to RECOVERY did regular reboot system upgraded.
A couple if bit mapp errors 11111. Then I basically flashed CWM.
Before you do this the partitions change from ext2-ext4. I'd advise
Backing them up.
LG Realm & exceed 2 TWRP recovery/fastboot files
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
TWRP recovery help L620 LG Realm
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
I think i know what seems to be the problem. I think i might have accidentally replaced the boot img with the twrp recovery img. i did not make a backup before this happened. is there anything i can do to make my phone boot up to its normal image? thanks
Nope. It is officially a paperweight and no one I know of has access to the stock ROM either.
Sent from my LGLS620 using XDA Premium 4 mobile app
Hey
Has anybody found a custom rom?
Finally. Easy as pie
Ok, I downloaded an image (w5c_twrp_bumped.img)
put that img on the root of my sd card
downloaded Rashr from the google play store
opened rashr and tapped 'recovery from storage', navigated to external sd and tapped the image and tapped
ýes please'
flashed it. after the flash the phone rebooted into the twrp recovery.
then just rebooted back into the system
worked perfectly.
im new here im not allowed to post outside links yet, just google "w5c_twrp_bumped.img" should take you to a link for a download of that recovery
i got twrp now as a custom recovery. on my lg realm.
That_One_Person760 said:
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
Click to expand...
Click to collapse
You have the bumped recovery so all i can say if u messed up is to flash a stock rom u can find on google i had to re flash mine a few times messing with root
right on, thanks for the info. I had no problems at all. it all fell in place like i was hoping. The Realm is the easiest device Iv ever rooted, flashed, and messed with. Well, as far as rooting and flashing a custom recovery. dunno bout roms though. Im sure its simple?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
OK, I grabbed and extracted this. I used Flashify to simply flash the recovery (w5c_twrp_bumped.img) and it works like a dream on my LG Realm.
OTOH, trying the same on an Exceed 2 gets me TWRP, but it cannot mount much of anything and the backup fails. After failing, it tells me "No OS found, continue?" I continue and get the message "Appears your device has no Root, install now?' I am absolutely certain I have root, or wouldn't even be able to run Flashify, so I continue and it simply boots into the OS just fine. Perhaps the readme isn't complete, as I see the following file in the extracted folder (resources.zip) with no explanation of why it's there. It "appears" to be a flash-able zip that installs "itson" (whatever THAT is). Note that the Realm has this in the /system/vendor/itson, yet the Exceed 2 doesn't.
Have you actually used this on an Exceed 2? And if so, what am I missing here?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
petermg said:
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
Click to expand...
Click to collapse
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
fathergweedo said:
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
petermg said:
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
Click to expand...
Click to collapse
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
fathergweedo said:
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
Click to expand...
Click to collapse
THANKS!!!! I'll make it a point to flash that to my mom's phone next time I get the chance!

[solved] Bricked Galaxy S6 - Help

THIS IS NOW RESOLVED. PLEASE DO NOT CONTINUE TO POST ON MY THREAD. YOUR CIRCUMSTANCES WILL NOT BE THE SAME AS MINE NORE ARE THEY LIKLEY TO RESOLVE ISSUES YOU HAVE, AS MINE WAS CAUSED BY A VERY SPECIFIC PROBLEM. START YOUR OWN THREADS DONT HIJACK MINE
Good morning XDA Devolopers,
I have used this site for many a year now but today had to sign up to get some help.
I purchased my SM-920F from Ebay, and low and behold, it had been blocked here in the UK, ever the optimist i looked about online and indeed there are several options online, including some services for remote unlocking, i decided it was worth a shot and ordered it, only from there on it goes from bad to worse.
After the unlock i was constantly greeted with Security Errors and Warning, i contacted the company who unlocked it, and was told to re-flash the rom with the same baseband version, after alot of hunting i found a rom from SAM Mobile and away i went, flashed and all seemed to go well i waited and waited, phone stuck on the boot screen. Galaxy S6, powered by Android...
I returned to the unlocking company asking for advice, only to be called a liar and they would never suggest i reflash the rom or firmware.
So now im stuck with a brick, ive tryed all i can think off and all i can research and i just cant make any progress. I did note after the unlock SuperSU had been installed on my phone (i wasnt made aware the unlock required them to root my phone, they tripped knox in the process).
I have a SM-920F origonally on O2 UK, i have tryed flashing there rom with no joy.
Im desperate to have this phone orking, even if its just for calls, my wife is currently at the hospital with our son whos fighting for his life against cancer, and all i get is abuse from here, i dont get paid till the 1st of the month so a new phone is out of the question at present. The unlocking company i used are tools, and to think iw as mighty impressed at the time.
I do have SOME cash, if theres a pro out there who wants to make a few bucks and can remote connect to me to help me solve this it would be much appreciated, i am just now stuck and desperate and badly need the help of the community.
Galaxy S6 920F
64GB Blue
Android 5.1.1
(Rooted by network unlockers)
WIndows 7 Ultimate - Odin (I have just about all of them these days)
Avalable Roms on my Machine (ALL O2 Roms and some other international variants for france and germany)
If anyone out there can help me please, if i could get on my knees and beg i would, im so desperate now to be able to just recieve calls from my wife and the hospital at this **** time for us.
Please please please someone somewhere must be able to help me out
Thanks
M
shir199m said:
Good morning XDA Devolopers,
I have used this site for many a year now but today had to sign up to get some help.
I purchased my SM-920F from Ebay, and low and behold, it had been blocked here in the UK, ever the optimist i looked about online and indeed there are several options online, including some services for remote unlocking, i decided it was worth a shot and ordered it, only from there on it goes from bad to worse.
After the unlock i was constantly greeted with Security Errors and Warning, i contacted the company who unlocked it, and was told to re-flash the rom with the same baseband version, after alot of hunting i found a rom from SAM Mobile and away i went, flashed and all seemed to go well i waited and waited, phone stuck on the boot screen. Galaxy S6, powered by Android...
I returned to the unlocking company asking for advice, only to be called a liar and they would never suggest i reflash the rom or firmware.
So now im stuck with a brick, ive tryed all i can think off and all i can research and i just cant make any progress. I did note after the unlock SuperSU had been installed on my phone (i wasnt made aware the unlock required them to root my phone, they tripped knox in the process).
I have a SM-920F origonally on O2 UK, i have tryed flashing there rom with no joy.
Im desperate to have this phone orking, even if its just for calls, my wife is currently at the hospital with our son whos fighting for his life against cancer, and all i get is abuse from here, i dont get paid till the 1st of the month so a new phone is out of the question at present. The unlocking company i used are tools, and to think iw as mighty impressed at the time.
I do have SOME cash, if theres a pro out there who wants to make a few bucks and can remote connect to me to help me solve this it would be much appreciated, i am just now stuck and desperate and badly need the help of the community.
Galaxy S6 920F
64GB Blue
Android 5.1.1
(Rooted by network unlockers)
WIndows 7 Ultimate - Odin (I have just about all of them these days)
Avalable Roms on my Machine (ALL O2 Roms and some other international variants for france and germany)
If anyone out there can help me please, if i could get on my knees and beg i would, im so desperate now to be able to just recieve calls from my wife and the hospital at this **** time for us.
Please please please someone somewhere must be able to help me out
Thanks
M
Click to expand...
Click to collapse
Turn off your phone, and then turn it on pressing and holding Volume Up, Home, and Power button at the same time until you see a warning. Then press Volume Up to continue, and navigate using volume keys and select wipe cache/factory reset with the Home button, then reboot.
Please note that by doing this all your data will be lost.
Uzair40 said:
Turn off your phone, and then turn it on pressing and holding Volume Up, Home, and Power button at the same time until you see a warning. Then press Volume Up to continue, and navigate using volume keys and select wipe cache/factory reset with the Home button, then reboot.
Please note that by doing this all your data will be lost.
Click to expand...
Click to collapse
Remains Stubbornly stuck on the boot screen.
Samsung Galaxy S6 - Powered By Android.
shir199m said:
Remains Stubbornly stuck on the boot screen.
Samsung Galaxy S6 - Powered By Android.
Click to expand...
Click to collapse
Donwload Phone INFO Samsung, and post screenshots.
Uzair40 said:
Donwload Phone INFO Samsung, and post screenshots.
Click to expand...
Click to collapse
Cant install any apps, phone dont boot.....
shir199m said:
Cant install any apps, phone dont boot.....
Click to expand...
Click to collapse
Try to update via Smart Switch
Uzair40 said:
Try to update via Smart Switch
Click to expand...
Click to collapse
Smart switch flashes with no issues, phone will not boot.
Even after recovery menu > Factory Data Reset & recovery menu > Format Cache
shir199m said:
Smart switch flashes with no issues, phone will not boot.
Even after recovery menu > Factory Data Reset & recovery menu > Format Cache
Click to expand...
Click to collapse
Install TWRP via Odin, and then do a factory reset
Uzair40 said:
Install TWRP via Odin, and then do a factory reset
Click to expand...
Click to collapse
Can you please provide me with a link to a guide of some kind, i dont mind doing that But id like to understand the process before i start it, if you can point me to a decent ish guide (and im aware of the risks TWRP may present)
Many thanks
shir199m said:
Can you please provide me with a link to a guide of some kind, i dont mind doing that But id like to understand the process before i start it, if you can point me to a decent ish guide (and im aware of the risks TWRP may present)
Many thanks
Click to expand...
Click to collapse
Thanks for ya info.
Having installed TWRP i noticed something very intresting, TWRP reports no operating system is installed.
Ive taken a leap of faith and using ODIN am now flashing the Stock 5.1.1 ROM.
Will report back in a few mins.
Okay so TWRP is installed, it reported no operating system.
I reflashed the Stock rom, all went well as expected, phone still refuses to boot.
I have reflashed TWRP and completed a factory reset. Again no dice, still wont boot.
Any further help would be much appreciated.
Thanks
M
shir199m said:
Okay so TWRP is installed, it reported no operating system.
I reflashed the Stock rom, all went well as expected, phone still refuses to boot.
I have reflashed TWRP and completed a factory reset. Again no dice, still wont boot.
Any further help would be much appreciated.
Thanks
M
Click to expand...
Click to collapse
Install a custom ROM.
Uzair40 said:
Install a custom ROM.
Click to expand...
Click to collapse
Yeah now were where i didnt want to be.
Okay ill try that, is there a particular rom you would recommend?
Ill take anything so long as i can make calls, my wifes just walked in the door and gone of like a fricking nuclear warhead
Oh dear god you should hear this haha.
Ill look on google for roms, but if you have any suggestion on a rom ill defer to you
shir199m said:
Yeah now were where i didnt want to be.
Okay ill try that, is there a particular rom you would recommend?
Ill take anything so long as i can make calls, my wifes just walked in the door and gone of like a fricking nuclear warhead
Oh dear god you should hear this haha.
Ill look on google for roms, but if you have any suggestion on a rom ill defer to you
Click to expand...
Click to collapse
OH THAN JESUS CHRIST.
I am not a god believing man, but i am very very very greatfull to the chap who has helped me with this.
I will update the OP Later, with full instructions of how ive done it... (Like once ive confirmed it all works)
shir199m said:
OH THAN JESUS CHRIST.
I am not a god believing man, but i am very very very greatfull to the chap who has helped me with this.
I will update the OP Later, with full instructions of how ive done it... (Like once ive confirmed it all works)
Click to expand...
Click to collapse
There is a ROM called AllianceROM, I've read that it's on of the best for the G920F.
Okay so as promised.
1. Flash Stock 5.1.1 ROM (Phone will not boot after)
2. Flash TWRP with ODIN
3: Reboot into TWRP and mount filesystem via MPT (i had to disable then enable it for my computer to detect it)
4: Copy ROM to phone (As a ZIP)
5: Using TWRP install ZIP
6: Follow Instructions
7: Dalvik / Cache Clear (it asks after the rom is installed)
8: Reboot
9: Wait
10: Wait Some More
11: TADA
Phone has booted and connected to the network, the AllianceROM suggested above will work in very much the same way! same process.
Thats all i did. After a week of gueswork i want to thank the chap who provide me some guidance both here and via PM
Phone is now running and working, i wish i could have stock rom but you cant have it all.
On a side note if you choose to use IMEI Gurus to unlock your phone, i highly suggest you dont, there after sales support are shocking, and they refunded my money even though its not what i wanted, had the provided the help i found here id not have been so stressy with them. There service does work, but they will root your device (which they dont mention in there sales pitch they will trip knox (again not mentioned) and once done you cant actually factory reset the phone with any method. ANd youll be here reading this.
Yes there services work, but guys please make your own informed decisions about there service, would i buy again from them? i doubt it, but needs must and all that.
THanks everyone
This is now resolved. Please do not continue to post on my thread. Your circumstances will not be the same as mine nore are they likley to resolve issues you have, as mine was caused by a very specific problem. Start your own threads dont hijack mine

Categories

Resources