Related
Hi all, I was on AKOP's milestone ROM before trying to flash their newest one. I did not do anything to the kernel or anything by the way.
I'm using ClockworkMod Recovery v6.0.2.7 and I rebooted into recovery and flashed super dark side wipe and then JB-MR1 and then gapps.
I went through the entire start up process with inputting your information and then finally I got into the actual home screen. I clicked around to see how the UI looked and then decided to reboot through the menu.
It was in the rebooting animation icon for at least 30 min before I decided to pull the battery. I want to wipe and start again but my cwm recovery isn't installing anything.
EDIT: The phone still works as I can boot into the phone and use it. I'm trying to reboot now: power button hold>reboot, but its taking ages still...need help on this reboot thanks
Any help here?
EDIT 2: Pretty much phone is "functional" but any method of trying to reboot or reboot into recovery fails
Thanks all!
Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?
8Fishes said:
Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?
Click to expand...
Click to collapse
Checked the Md5 with an app and it matches up perfectly with akop's main website.
I'm running 6.0.2.8 cwm. Is it even possible that its cwm? I used the same version to flash AKOPs new ROM.
and im flashing gapps-jb-20121212-signed.zip
Does it have anything to do with my kernel?
You aren't supposed to use super wipe with cwm 6. That is probably your problem.
meekrawb said:
You aren't supposed to use super wipe with cwm 6. That is probably your problem.
Click to expand...
Click to collapse
Thanks so much for pinpointing the problem! Is there a fix to this?
And is this the recommended method of flashing? (Taken from http://forum.xda-developers.com/showthread.php?t=1926754):
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle for 5-10 minutes if flashing TW ROMs, this step is unnecessary for AOSP based ROMs.
11. (Optional) if flashing a new radio flash AFTER the ROM has been initially booted for the first time. No wipes are necessary when flashing a new radio but it HAS to be flashed after the ROM is loaded and settled in. Flashing a radio first and then a ROM has caused issues like the phone not even recognizing there is a network for it. ( phone remains in emergency mode )
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery
Ostyrion said:
Thanks so much for pinpointing the problem! Is there a fix to this?
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery
Click to expand...
Click to collapse
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.
meekrawb said:
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.
Click to expand...
Click to collapse
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?
Ostyrion said:
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?
Click to expand...
Click to collapse
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.
meekrawb said:
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.
Click to expand...
Click to collapse
I'm trying to read through the thread you gave me but its kinda cluttered and its hard finding exactly where to start...pointers?
From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.
meekrawb said:
From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.
Click to expand...
Click to collapse
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Edit: Downloaded a root checker. Looks like I need to reroot. Thank you again SOOOOO much!!!
Ostyrion said:
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Click to expand...
Click to collapse
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.
meekrawb said:
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.
Click to expand...
Click to collapse
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!
Ostyrion said:
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!
Click to expand...
Click to collapse
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).
meekrawb said:
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).
Click to expand...
Click to collapse
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?
Ostyrion said:
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?
Click to expand...
Click to collapse
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.
meekrawb said:
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.
Click to expand...
Click to collapse
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?
Ostyrion said:
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?
Click to expand...
Click to collapse
Why do you need root? You should be able to just flash the newer cwm zip.
Here is a superuser zip that I used successfully on my t989:
meekrawb said:
Here is a superuser zip that I used successfully on my t989:
Click to expand...
Click to collapse
Thanks for the file!
I downloaded cwm from this site:
http://www.clockworkmod.com/rommanager
but it comes as an img file...and I dont seem to be able to flash that from recovery
Hey guys,
I noticed no one talked about this issue on forums or in an article, so I decided to post my solution that it worked for me. I will try to explain as much as I can. I also wanna say that I am not a developer. Before I start.
I AM NOT RESPONSIBLE ON YOUR DEVICE OR ANYTHING HAPPEN TO IT WHAT SO EVER. IF ANYTHING HAPPEN TO YOUR DEVICE, ITS YOUR OWN RESPONSIBILITY
Read all the way to the end
This is for Samsung Galaxy Note 2 T-Mobile (SGH-T889). I didnt try it on other variants but I believe it should work. Anyway, this method is for stock ROM only. I no longer support custom ROMs. If you wanna try it with a custom ROM then good luck. I hope it works for you.
Here is what I did:
1. Make sure you have Stock ROM 4.1.2 (UVBMD1). If you dont then go here http://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
2. Root your device. I used ChainFire method. Here is a "How to" http://honai-android.blogspot.com/2013/06/how-to-root-galaxy-note-2-t-mobile-sgh.html
3. Try to connect. If it didnt work then download Triangle Away from "Play Store".
4. Go into Triangle Away to reset the flash counter.
5. Try to connect now. It should work for sure ^_^
Optional:
If you want Custom Recovery then:
6. Install the Custom Recovery you want. I tried TWRP
7. Use Triangle Away to reset the flash counter.
8. Try to connect. It should work
If anyone have a question please let me know. I will be more than glad to help you guys.
If I helped you please Press Thanks and Good Luck :fingers-crossed:
Note: I noticed when I go to TWRP. The dongle don't work again. So, I use Triangle Away one more time and things works back perfectly.
Did this work with a custom kernel? In my experience it must be stock. I'd ve happy to find out I am wrong.
Sent from my GNote2 using Tapatalk 2
Here is my info I hope it will help everyone.
Sent from my SGH-T889 using xda app-developers app
k3v0 said:
Did this work with a custom kernel? In my experience it must be stock. I'd ve happy to find out I am wrong.
Sent from my GNote2 using Tapatalk 2
Click to expand...
Click to collapse
I didnt think about it previously. It seems you were right. It is the stock kernel. So right now i am wandering if I can flash a custom kernel. So my phone will be like this:
Custom ROM (Jedi Master 13)
Custom Kernel
Stock boot img
Is it possible?
By the way, what can you do with a custom kernel beside increasing the cpu from 1600 to 1920? btw I am just asking because I really didnt do that much research on kernel yet. Plus, Note 2 is my first android phone :cyclops:
jamalkhaffaf said:
I didnt think about it previously. It seems you were right. It is the stock kernel. So right now i am wandering if I can flash a custom kernel. So my phone will be like this:
Custom ROM (Jedi Master 13)
Custom Kernel
Stock boot img
Is it possible?
By the way, what can you do with a custom kernel beside increasing the cpu from 1600 to 1920? btw I am just asking because I really didnt do that much research on kernel yet. Plus, Note 2 is my first android phone :cyclops:
Click to expand...
Click to collapse
In my experience no, the syscope service verifies the kernel, lack of superuser access, the sysscope binary itself, among other things. I tried a stock kernel with only init.d support added and that failed.
I have custom recovery (TWRP) and SuperSU. Triangle Away works wonders with flashing and SuperSU. There is a "sysscope blaster" module for the xposed framework that can help with more heavily modded custom ROMs. Both didn't help when I ran a custom kernel on an otherwise stock ROM.
I wanted a custom kernel primarily for init.d support to plug the data leak in my firewall app. I was also interested in overclocking and undervolting. Init.d support I manage through a workaround, so in my case I am only without OC/UV. SetCPU even on the stock kernel is a fair alternative here.
Same here I had an iPhone 3GS before this.
Sent from my GNote2 using Tapatalk 2
I've also been looking for a way to do all of this and will try your steps. But last time I checked, Jedi Master rom does not have the AllShare Cast utility in it. How did you get the Allshare connection utility into Jedi Master?
---------- Post added at 03:33 PM ---------- Previous post was at 03:27 PM ----------
jamalkhaffaf said:
Hey guys,
Here is what I did:
1. Rooted my stock ROM 4.1.2 using Galaxy note 2 Toolkit 4.1.0 "http://forum.xda-developers.com/showthread.php?t=1923956".
2. Installed Custom Recovery "TWRP"
3. Flashed Custom ROM "Jedi Master 13"
4. Did a Back-up using TWRP to my external SD card (Very Recommended)
5. Download and flashed "Stock boot img" for T-mobile note 2 SGH-T889. To flash the stock boot img, you can use the Toolkit:
a. Enter your phone# (My phone was #72)
b. Enter Root/Unroot option (# 2)
c. Enter #6 to flash the stock ROM related to your phone model#
d. Then follow instructions...
6. Now download and use "Triangle Away" to do its magic. I checked my flash counter and it was "1". Its alright
Click to expand...
Click to collapse
Maybe (probably!) I'm confused, but if you flash JM in step 3, then later flash the stock rom in step c, won't that overwrite your JM installation?
I apologize and wanna thank you for correcting me.
I meant "Stock Boot img"
Sent from my SGH-T889 using xda app-developers app
jamalkhaffaf said:
I apologize and wanna thank you for correcting me.
I meant "Stock Recovery"
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
So step c is flash stock recovery, not stock rom? So when do you flash TWRP in your process?
---------- Post added at 03:52 PM ---------- Previous post was at 03:43 PM ----------
I see you corrected the steps, so thanks for that! Still wondering about how you got the Allshare Cast connection utility into Jedi Master? AFAIK, he removes it. Thanks.
Guys it's stock boot img. It's NOT stock rom neither recovery. I did a mistake. I replay to u on the fly... but I am 100%sure it's stock boot img.
Sent from my SGH-T889 using xda app-developers app
jamalkhaffaf said:
Guys it's stock boot img. It's NOT stock rom neither recovery. I did a mistake. I replay to u on the fly... but I am 100%sure it's stock boot img.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Edit: Never mind on this, just opened toolkit (which I haven't used in a long time) and I see it's right there. Still wondering about Allshare Cast in JM.
No worries, we got it! But one more question, if you don't mind. Where are you getting the stock boot img? Is this a flashable zip from somewhere, or is this done in Odin in the toolkit? Really appreciate all your work!
Success!
Hey, just wanted to report that I went through the steps and installed JM13, and then used toolkit to push the stock boot image. And sure enough, it all works! Turns out I missed AllShare Cast in JM13 before because it wasn't in the toggles. BUT, there is a widget for it that you can drag to a home screen. Tested it out and works great with the dongle. Thanks for posting all this!
Edit: I should add that anyone doing this should know that some of the kernel-related tweaks in JM will not work without it's own Saber kernel installed. So after pushing the stock boot image, which overwrites Saber and restores the stock kernel, Voodoo sound for sure does not work, and probably some of the Jedi cpu tweaks, haven't tried those.
I just came back home to replay ur previous post. I am very glad that it worked for u. I hope this trick will work on all custom roms based on touchwize. If there is a tester out to try my method that will be great.
I also hope this thread become sticky. Because there isn't anyone online that wrote a solution for it.
Thanks
Sent from my SGH-T889 using xda app-developers app
jamalkhaffaf said:
I just came back home to replay ur previous post. I am very glad that it worked for u. I hope this trick will work on all custom roms based on touchwize. If there is a tester out to try my method that will be great.
I also home this thread become sticky. Because there isn't anyone online that wrote a solution for it.
Thanks
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I think the big issue with this working on any custom rom is gonna be the kernel issue. JM is custom but still pretty close to stock. Or at least closer than probably any other rom. So pushing the stock kernel instead of the one the rom dev provided could cause some pretty bad things on some roms that really depend on the kernel.
The best part of this trick is to have rooted ROM and AllShare cast dongle. It's much better than stock ROM not rooted. So now u can enjoy root features which everyone needs and a big screen with ur phone desktop.
Sent from my SGH-T889 using xda app-developers app
jamalkhaffaf said:
Hey guys
Here is what I did:
1. Rooted my stock ROM 4.1.2 using Galaxy note 2 Toolkit 4.1.0 "http://forum.xda-developers.com/showthread.php?t=1923956".
2. Installed Custom Recovery "TWRP"
3. Flashed Custom ROM "Jedi Master 13"
4. Did a Back-up using TWRP to my external SD card (Very Recommended)
5. Download and flashed "Stock boot img" for T-mobile note 2 SGH-T889. To flash the stock boot img, you can use the Toolkit:
a. Enter your phone# (My phone was #72)
b. Enter Root/Unroot option (# 2)
c. Enter #6 to flash the stock boot img related to your phone model#
d. Then follow instructions...
6. Now download and use "Triangle Away" to do its magic. I checked my flash counter and it was "1". Its alright
I booted to system and followed instruction on the AllShare cast dongle. it connected to my AllShare cast dongle like a charm. It wasn't lagging or anything like that. It worked perfectly fine with instant reflection of my screen. I tested it with Games, Netflix, Movies.....
I hope it works for you guys and also hope my explanation was sufficient. If you have any questions please let me know, I will try to answer them. And if it worked for you with a different custom ROM please let me know as well.
Thumbs up please and Good Luck :fingers-crossed:
Note: I noticed that when I go to TWRP. The dongle don't work again. So, I use Triangle Away one more time and things works back perfectly.
Click to expand...
Click to collapse
Thank you very much for your kind and sharing it with us.
I just bought the Allshare Cast Dongle, and I'm having a real problem with this dang thing. I went from iphone3 to GN2, so I'm very noob on rooting stuff, so please bare with me.
I follwed the youtube video to root my device to TRWP custom rom/recovery, but it wont work with Allshare Cast Dongle since it is a custom rom. I did some research and people said I have to use Triangle Away to reset the binary counter to 0, so i did that, but my binary counter was still at 1! It still didnt work with Allshare Cast Dongle.
Then I used Triangle Away again to reset the binary counter, and then went into Odin Download Mode to flash the Stock Recovery. The dang Allshare Cast Dongle still didnt work!
I did remove some bloatwares before, so I'm not sure if this has to do with it.
Is there anyway you or someone can help me solve this problem?
Also, whats the difference between stock recovery and stock boot,
and could you give me the link to the Stock boot file?
I have T-mobile GN2 and I really dont want to unroot and do the factory reset... I have alot of stuff on my phone.
Thank you very much
mygalaxynote2 said:
Thank you very much for your kind and sharing it with us.
I just bought the Allshare Cast Dongle, and I'm having a real problem with this dang thing. I went from iphone3 to GN2, so I'm very noob on rooting stuff, so please bare with me.
I follwed the youtube video to root my device to TRWP custom rom/recovery, but it wont work with Allshare Cast Dongle since it is a custom rom. I did some research and people said I have to use Triangle Away to reset the binary counter to 0, so i did that, but my binary counter was still at 1! It still didnt work with Allshare Cast Dongle.
Then I used Triangle Away again to reset the binary counter, and then went into Odin Download Mode to flash the Stock Recovery. The dang Allshare Cast Dongle still didnt work!
I did remove some bloatwares before, so I'm not sure if this has to do with it.
Is there anyway you or someone can help me solve this problem?
Also, whats the difference between stock recovery and stock boot,
and could you give me the link to the Stock boot file?
I have T-mobile GN2 and I really dont want to unroot and do the factory reset... I have alot of stuff on my phone.
Thank you very much
Click to expand...
Click to collapse
According to your description you did one mistake in your steps.
You need to flash Stock BOOT img and keep the Custom Recovery. The Custom Recovery is very useful tool. You can flash Custom ROMs, Themes, or any .zip file.
After you flashing stock boot img, then you will use Triangle Away. As I mentioned in my OP, even if you still have the counter on 1, it doesn't matter.
After you boot into the system just go ahead and connect to Allshare Cast Dongle.
I hope it will work for you. Anyway let me know if you have any problem.
Good Luck
jamalkhaffaf said:
According to your description you did one mistake in your steps.
You need to flash Stock BOOT img and keep the Custom Recovery. The Custom Recovery is very useful tool. You can flash Custom ROMs, Themes, or any .zip file.
After you flashing stock boot img, then you will use Triangle Away. As I mentioned in my OP, even if you still have the counter on 1, it doesn't matter.
After you boot into the system just go ahead and connect to Allshare Cast Dongle.
I hope it will work for you. Anyway let me know if you have any problem.
Good Luck
Click to expand...
Click to collapse
Thank you for replying.
is it possible that you give me the link to Tmobile SGH-T889 stock Boot img?
Also, since I have already flashed the stock recovery, is it going to be a problem when flashing Stock Boot img with Odin?
After I flashed the stock recovery, my phone status still says modified, so I'm not sure if I'm on stock or custom recovery now.
You said you flashed stock boot img on top of your Jedi Master 13,
Do you know if it is safe for me to flash the Jedi Master 13 first and then flash the stock boot img?
thanks alot
mygalaxynote2 said:
Thank you for replying.
is it possible that you give me the link to Tmobile SGH-T889 stock Boot img?
Also, since I have already flashed the stock recovery, is it going to be a problem when flashing Stock Boot img with Odin?
After I flashed the stock recovery, my phone status still says modified, so I'm not sure if I'm on stock or custom recovery now.
You said you flashed stock boot img on top of your Jedi Master 13,
Do you know if it is safe for me to flash the Jedi Master 13 first and then flash the stock boot img?
thanks alot
Click to expand...
Click to collapse
First I am still not responsible to anything happen to your device. but here is the way that I would do it on my own device:
1. Flash Custom Recovery TWRP. to make it easier for you to flash a custom ROM (Jedi Master 13).
2. Flash Jedi Master 13
4. Flash Stock Boot Img. as for the file, Galaxy note 2 Toolkit will download those files for you. Follow the instructions on the toolkit and you should be able to flash the Stock Boot img.
5. use the Triangle Away. it doesnt matter if the flash counter=1 nor Modified. The reason we are using Triangle Away because it "resets binaries".
6. After that connect to your Dongle
Note: After doing all the steps. if you went to the Custom Recovery in the future for any reason, you will have to use Triangle Away again. I noticed when every-time i go to custom recover to do something, I wont be able to connect to AllShare cast dongle. So use Triangle away to reset your binaries and you should be fine.
let me know if worked for you or if you have any other questions. I am glad to help
jamalkhaffaf said:
First I am still not responsible to anything happen to your device. but here is the way that I would do it on my own device:
1. Flash Custom Recovery TWRP. to make it easier for you to flash a custom ROM (Jedi Master 13).
2. Flash Jedi Master 13
4. Flash Stock Boot Img. as for the file, Galaxy note 2 Toolkit will download those files for you. Follow the instructions on the toolkit and you should be able to flash the Stock Boot img.
5. use the Triangle Away. it doesnt matter if the flash counter=1 nor Modified. The reason we are using Triangle Away because it "resets binaries".
6. After that connect to your Dongle
Note: After doing all the steps. if you went to the Custom Recovery in the future for any reason, you will have to use Triangle Away again. I noticed when every-time i go to custom recover to do something, I wont be able to connect to AllShare cast dongle. So use Triangle away to reset your binaries and you should be fine.
let me know if worked for you or if you have any other questions. I am glad to help
Click to expand...
Click to collapse
Thank you very much for the details step by step instructions.
I've flashed stock recovery before, but I do not think my phone is on stock recovery because I have removed some bloatwares after I rooted, so i believe Samsung did not allow me to switch back to stock recovery unless I do the factory reset, and then flash stock firmware.
However, I'm not sure if that was the case since I dont know how to check my phone to see if it's still on custom or stock recovery
After I flashed the stock recovery, my phone still boots up and works just like I had before.
I think I just need to flash the Jedi Madter 13 without having to flash TWRP custom recovery again.
As far as Stock Boot .img, I dont see any option that says Stock Boot .img anywhere on gn2 toolkit, I only saw
option#3: Flash insecure Boot image Only, for adb access.. is this the right option on GN2 toolkit menu?
I'm sorry to ask you so many questions, but I just want to make sure I know what I'm doing because I cant really afford another GN2
Thanks alot for your patience helping me.
mygalaxynote2 said:
Thank you very much for the details step by step instructions.
I've flashed stock recovery before, but I do not think my phone is on stock recovery because I have removed some bloatwares after I rooted, so i believe Samsung did not allow me to switch back to stock recovery unless I do the factory reset, and then flash stock firmware.
However, I'm not sure if that was the case since I dont know how to check my phone to see if it's still on custom or stock recovery
After I flashed the stock recovery, my phone still boots up and works just like I had before.
I think I just need to flash the Jedi Madter 13 without having to flash TWRP custom recovery again.
As far as Stock Boot .img, I dont see any option that says Stock Boot .img anywhere on gn2 toolkit, I only saw
option#3: Flash insecure Boot image Only, for adb access.. is this the right option on GN2 toolkit menu?
I'm sorry to ask you so many questions, but I just want to make sure I know what I'm doing because I cant really afford another GN2
Thanks alot for your patience helping me.
Click to expand...
Click to collapse
Sorry for the late respond, I have a lot of work these day. Anyway, in order to solve your issue. you need to go back to the way your phone was on the first day you got it. Which means, everything stock. Then go to my OP and start from there.
This might help you to go back to everything Stock.
NOTE: this link is for International Model. It should be just fine for T-Mobile version but make sure you download the RIGHT FIRMWARE for
T-Mobile model (SGH-T889). One more thing, watch the video all the way to end make sure you understand then do it step by step.
http://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Note: Custom Recovery is used to flash custom ROMs and do nand back-up, also some other useful things. So, I strongly recommend that you keep custom recovery.
I really hope this will help you. I guarantee if you went back to stock and follow the steps then your phone should be connected to the dongle.
Good luck:fingers-crossed:
If you bumped into problems let me know as well. happy to help
Hello members,i have a problem . I bought a samsung galaxy tab 3 7.0 wifi (SM-T210) last week and i have rooted it + installed cwm and after i flash anything(custom lock screen or custom rom) the tablet gets soft bricked and the rom dont boot anymore,it enters automaticaly in cwm. So how can i fix it?
d0vada said:
Hello members,i have a problem . I bought a samsung galaxy tab 3 7.0 wifi (SM-T210) last week and i have rooted it + installed cwm and after i flash anything(custom lock screen or custom rom) the tablet gets soft bricked and the rom dont boot anymore,it enters automaticaly in cwm. So how can i fix it?
Click to expand...
Click to collapse
Which recovery Version you are flashed on your tab?
And which root.zip you are used?
Flash Stockrom and try it again.
bierma32 said:
Which recovery Version you are flashed on your tab?
And which root.zip you are used?
Flash Stockrom and try it again.
Click to expand...
Click to collapse
Im using the latest TWRP recovery 2.7.0.0 and for root i use a zip called universal root armeabi *smth like that*
I allready flashed the stockrom 3 times and i got the same result. also im using the T210XXANC2 firmware.
In CWM, wipe data and factory reset. Then go to Download mode, use Odin and flash your stock rom. That should do it.
paranoidmarvin42 said:
In CWM, wipe data and factory reset. Then go to Download mode, use Odin and flash your stock rom. That should do it.
Click to expand...
Click to collapse
i have rooted stock rom running with latest twrp but if i flash a custom rom it wont boot anymore, it gets softbricked but i dont know why.
d0vada said:
i have rooted stock rom running with latest twrp but if i flash a custom rom it wont boot anymore, it gets softbricked but i dont know why.
Click to expand...
Click to collapse
What ROM are you trying to flash? You must have missed a step. Make sure you read the instructions carefully before doing anything and use a custom rom for your device. Try again. I'm also new to Android and has softbricked my tab a couple of times now.
Go back to stock. Let your device boot completely. Install recovery again. Reboot again.
To make it easier, how about watching a video so you can see how it's done properly? It helped me a lot. http://forum.xda-developers.com/showthread.php?t=2459817
Good luck.
paranoidmarvin42 said:
What ROM are you trying to flash? You must have missed a step. Make sure you read the instructions carefully before doing anything and use a custom rom for your device. Try again. I'm also new to Android and has softbricked my tab a couple of times now.
Go back to stock. Let your device boot completely. Install recovery again. Reboot again.
To make it easier, how about watching a video so you can see how it's done properly? It helped me a lot. http://forum.xda-developers.com/showthread.php?t=2459817
Good luck.
Click to expand...
Click to collapse
I want to flash seal rom. also, thanks for the links, i will check them later.
d0vada said:
I want to flash seal rom. also, thanks for the links, i will check them later.
Click to expand...
Click to collapse
Plesse,dont use TWRP , i prefere CWM or PhilzTouch,why : alot of user are have postet probs when they used TWRP.
Also i prefere after rooting The Blackhawk Kernel.
bierma32 said:
Plesse,dont use TWRP , i prefere CWM or PhilzTouch,why : alot of user are have postet probs when they used TWRP.
Also i prefere after rooting The Blackhawk Kernel.
Click to expand...
Click to collapse
So i have flashed (again) the stock firmware from sammobile,i rooted it,installed cwm 6.0.4.7 and then i flashed SEAL rom v4 and its not working. Its like something that doesnt let custom rom boot on my tab. Sad part is that i cant provide a logcat because the android wont boot.
EDIT: Do i have to unlock the bootloader?
d0vada said:
So i have flashed (again) the stock firmware from sammobile,i rooted it,installed cwm 6.0.4.7 and then i flashed SEAL rom v4 and its not working. Its like something that doesnt let custom rom boot on my tab. Sad part is that i cant provide a logcat because the android wont boot.
EDIT: Do i have to unlock the bootloader?
Click to expand...
Click to collapse
Last Try,
Have you flashed The Blackhawk Kernel?
If not , Boot Into recovery, make a full wipe, flash seal ,Blackhawk Kernel ,full wipe again and reboot.
If this all not help ,post your prob at The Rom Thread.
bierma32 said:
Last Try,
Have you flashed The Blackhawk Kernel?
If not , Boot Into recovery, make a full wipe, flash seal ,Blackhawk Kernel ,full wipe again and reboot.
If this all not help ,post your prob at The Rom Thread.
Click to expand...
Click to collapse
I allready tried 3 roms(seal, 4.2.2 beta 2 and inspire) and all goes to the same result. Also, after installing the cwm i flash first the blackhawk kernel and android boots normally (stock rom with custom kernel) but custom rom with or without custom kernel wont boot.
I had similar problem try flashing seal v3.
Made this from the new 80220f open EUR kdz.
This is the complete LG KK 20f ROM - nothing missing or messed with.
You can flash SuperSU and get root if you wish - your choice.
I provide this assuming you have an understanding of the terminology used below and appreciate that any flashing activity has some risk.
I strongly advise against using any form of restore from previous backups, such as TB or Nandroid.
Once the process is complete, custom recovery will be lost.
Method:
Download both the ROM zip file linked below and SuperSU zip file (if you want root) and copy to your SD card.
You need to be already on Rooted JB, Rooted KK or PURE CM11 with either TWRP 2.6.3.3 or 2.6.3.4 or TWRP 2.7.0.0 (nothing else).
Reboot to TWRP recovery
Wipe: System, Data, Cache. Dalvik (nothing else)
Flash the ROM zip - ignore any "FAIL" warnings.
Wipe Cache and Dalvik (nothing else)
Go to the Mount page in TWRP and select System (leave the other defaults alone)
Flash the SuperSU zip - ignore any "FAIL" warnings
Reboot
Done
Don't use AutoRec to flash TWRP - you will lose Knock code.
Alternatively - if you have flashed TWRP on another KK Stock ROM (using AutoRec), you can full wipe (not SDCard) and flash this directly without going back to JB.
Download from here:
https://drive.google.com/file/d/0B_ESvfVtZzEwaWRaTjRNUEdDOEE/edit?usp=sharing
Credit to Chainfire for the rooting method.
good job. but you don't put the download ?
paglop said:
good job. but you don't put the download ?
Click to expand...
Click to collapse
Link is there....!
why use AutoRec ? the recovery is lost ?
how do i acquire custom recovery once i flash 20f? flashify app?
zekurosu said:
how do i acquire custom recovery once i flash 20f? flashify app?
Click to expand...
Click to collapse
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.
paglop said:
why use AutoRec ? the recovery is lost ?
Click to expand...
Click to collapse
Yes,you will lose your custom recovery if you install this stock rom. But don't care about it.You may use AutoRec and your recovery will be back :good:
Edit : Hmm i think knock code will unusable if we flash TWRP with AutoRec.
Edit 2 : Aarghh i misunderstood. After using AutoRec and we will install any kernel with knock code support.
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.
Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this. If you want to have a pure stock ROM, kernel and all, its easiest to use the alternative method to keep your recovery (at the bottom of the op)
Click to expand...
Click to collapse
If i'm not wrong,the alternative method is not addicted to keep custom recovery. The custom recovery (whatever you have) won't be there after flashing this rom all the way mate.:good:
Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.
Click to expand...
Click to collapse
Precisely!
If someone already has Custom Recovery, and isn't overly bothered about preserving it, then this is potentially quicker and easier that then kdz method. And with easy root. Big plus point.
If you want a completely Stock experience of course.
What we don't know is how much development LG have done with the kernel. So, if one uses Autorec, any benefits of a later LG stock kernel will be lost.
Enjoy!
I am on v20d stock kit kat rooted with ioroot. D802 model. Does this flashabel rom include bootloader? Cause to have a custom recovery, I will have to use autorec app, which will dowgrade my bootloader. So will this rom work if the recovery has been flashed with autorec?
And also flashing this rom means that stock recovery will be flashed too?
I installed this 20f. it corrects problems ratio with slimport on small screen.
Just updated to D80220F. I can confirm that there is a Google Folder pre created. Havent noticed much else yet. will keep you updated.
Whole system feels super fast. Is it just me or is this faster than 802D/802B?
Knock on seems more reliable. Senses it way better and ignores ghost touches better.. Auto brightness seems to be managing brightness better too.
i have twrp 2.7.0.0 custom recovery, and i'm on d802b firmware (kk stock) with dorimanx kernel...
just 1 question to be sure (because i didn't quite get the OP):
- will i lose twrp if i flash this zip? (if yes, how do i get custom recovery back and safely?)
thanks in advance
Not option for ART
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
60nine yes you lose twrp. It is for return to official.
ok, thanks... and how do i get twrp back? is it even possible?
on that matter - can "recovery.bin" from this zip be replaced by custom recovery .bin file?
shriom_manerker said:
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.
Click to expand...
Click to collapse
Can you make a tutorial or write it down how you did it??? Because I wan't stock rom but don't want to lose recovery....
First root, and autorec for instal recovery. But you need a custom kernel .
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
read a little before
ok, so autorec works for 20f... all i wanted to know... (i don't care for knock code, i just want knock on to work)
the OP was a bit confusing - maybe it needs to be updated with a basic FAQ...
if anyone tried to flash this, then used autorec for custom recovery and flashed latest dorimanx 5.7 kernel - please confirm if knock on works (not knock code)
thanks in advance
Not kernel just autorec
Hi em using Samsung AT&T S3 I747(d2att).Kitkat4.4.2 is installed in it and now i wanted to install lollipop on it.i have rooted my device from kingo root & now my device is fully rooted.i have installed TWRP manager and recovery installed is CWM v6.0.4.7.when i boot in to recovery mode is is brand new recovery mode with touch.now i wanted to install lollipop on it.
download.cyanogenmod.org/?device=d2att
i get to this website and know em confuse that what is CyanogenMod Build{may be it is the ROM of lollipop (cm-12.1-20160212-NIGHTLY-d2att.zip (279.61 MB)
sha1: 07b5db3a77d9bcf32ae50919d2dc78b2dc1d5138)}
what is (Cyanogen Recovery) {cm-12.1-20160212-NIGHTLY-d2att-recovery.img
sha1: 1a16e4e453915657a112f152341ad9ff787afe80}
well know what should i do to install the lollipop on my device.whether i flash the recovery image firstly OR this cm-12.1-20160212-NIGHTLY-d2att.zip (279.61 MB)
sha1: 07b5db3a77d9bcf32ae50919d2dc78b2dc1d5138)}
KINDLY HELP ME....!!
There is no need to root a phone before installing a custom recovery such as CWM or TWRP.
I would use TWRP in place of CWM as CWM is no longer being developed.
If you install Cyanogen recovery, it will replace your existing recovery. I find TWRP to be more flexible that Cyanogen recovery.
LP Cyanogen is cm13 and you should use TWRP to install cm13 ROMs. The AT&T s3 i747 is also known as the d2lte and d2att. ROMs designed for either of these two devices will work on your phone (although maybe not 100%). There is no official CM13 ROM for the s3.
@audit13 , just a quick question ; (because am certainly not as up to date with the wonderful s3) but isnt cm13 MM ? or am i wrong:what:
"err on the side of kindness"
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
audit13 said:
There is no need to root a phone before installing a custom recovery such as CWM or TWRP.
I would use TWRP in place of CWM as CWM is no longer being developed.
If you install Cyanogen recovery, it will replace your existing recovery. I find TWRP to be more flexible that Cyanogen recovery.
LP Cyanogen is cm13 and you should use TWRP to install cm13 ROMs. The AT&T s3 i747 is also known as the d2lte and d2att. ROMs designed for either of these two devices will work on your phone (although maybe not 100%). There is no official CM13 ROM for the s3.
Click to expand...
Click to collapse
"err on the side of kindness"
My bad, yes, MM is CM13, LP is cm12.1. Thanks for catching my mistake
I guess I'm spending too much time bouncing between the Nexus 4, Nexus 5, Note 3, s3, and s4 forums!
I came across the different threads about bootloader...i have the bootloader version (I747UCUFNE4).Is that safe to flash the CM-12.1-20160212-NIGHTLY-d2att.zip on my above specified device without bricking my device????
Cm does not touch the bootloader or modem so you should be fine but there is always the chance the something else goes wrong.
audit13 said:
Cm does not touch the bootloader or modem so you should be fine but there is always the chance the something else goes wrong.
Click to expand...
Click to collapse
somethng what??????????
Power failure, corrupted file, phone becomes disconnected during s flash, etc.
how is it that i use CWM touch recovery to flash above said lollipop and its image....?is it ok for me to do so???can i choose both the above said cm-12.1-20160212-NIGHTLY-d2att.zip and cm-12.1-20160212-NIGHTLY-d2att-recovery.img at same time to install lollipop on my d2att??
I am saying CWM touch recovery because TWRP manager hangs installing the latest recovery on my device may b it is because of i use ROM manager firstly to install the latest CWM recovery?
please give the guide of simple steps on this thing......
waiting anxiously for your kind reply.....!!:fingers-crossed:
http://forum.xda-developers.com/showpost.php?p=65292709&postcount=2
Sorry again but can i use CWM touch recovery to flash CM12.1 and gapps from the micro SD card????
above you said that CWM is not works with CM13 but i wanna use CM 12.1.
you should use TWRP to install cm13 ROMs
Click to expand...
Click to collapse
@ audit13
i believe what @audit13 said was CWM is no longer being developed. twrp recovery is preferred by most people because they are still making it better. CWM hasnt an update in years.
also if you currently have cyanogen recovery it will be wiped by flashing either CWM or twrp.
yes you can use CWM to install CM12. but again ; twrp has more options and most people prefer it.
so ..... i personally would use twrp to install anything before i used cwm.
remember to make a backup of current setup just in case something goes wrong so that you can still have a working phone.
"err on the side of kindness"
Thanks for the guidance....because of both of you i able to flash the lollipop on my D2att without damaging or bricking...thanks alot again @audit13 @mrrocketdog :good::good::good::good::good::victory::victory::victory::angel:
@wajihbhat , that is awesome! p.s. love the screensaver.
"err on the side of kindness"