[RECOVERY][GPL] OUDHS CWM-Based Recovery 1.0.3.3 :: 5/3/2013 :: Touch & normal colors
Shabbypenguin, k0nane and the OUD Hit Squad present...
OUDHS CWM-Based Recovery 1.0.3.3 for T-Mo GS4
Shabbypenguin did all of the work required for this - have you fed your devs today?
Read the whole post before continuing!
Hey look, a fully-working recovery! This is an official release of OUDHSR for jftletmo and is unique to this device. Other carriers' devices have their own builds. In large part, this is like other CWM builds you're used to... but with some unique features to come - and of course, touch support (as of 1.0.3.2) I was asked by Shabbypenguin to release this for our device. Thank him for it, not me!
Code:
#include <external/cyanogenmod/std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Instructions
Download Odin 3.07 - see section below.
Download the recovery TAR - see section below.
Extract the contents of odin-307.zip. Do not try to extract files from the .tar.md5.
Run Odin 3.07.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR you downloaded. Leave other fields empty.
Don't panic. Odin may freeze while it checks the MD5 signature of the TAR. This is normal.
Put your device into Download Mode:
Power down fully and disconnect the USB cable.
Hold Volume Down + Power.
You should now be at Download Mode. Connect your device and wait for it to be recognized.
Click Start in Odin.
Wait! When complete, Odin should appear like the following:
That's it! Your device will autoreboot.
FAQ
Q: How do I get into recovery?
A: Power off, and hold Volume Up + Power until you see blue "Recovery booting" text in the corner. Let go when you do, or it might reboot again.
Q: Can I flash this on another US GS4 variant?
A: That's a bad idea. This contains asserts specific to the T-Mo GS4, and ROMs that check to make sure you're flashing on the right device will fail. Besides, you have a version for your device, check its forum.
Q: Did you steal touch from TWRP?
A: No.
Q: I liked the funky text! Can I reenable it?
A: Try rotating your device a bunch of times.
Q: Will this add a triangle to my boot screen?
A: Probably not. We haven't seen one. If it does, oh well, see disclaimer above.
Q: Dafuq are these colors?!
A: What, you don't like the funk?
Q: I'm colorblind you royal assh0le!
A: I'm... genuinely sorry if this is unreadable to anyone, colorblind or otherwise.
Q: So you're going to release a normal-colored one?
A: Now, I didn't say that... But official CWM is due rather soon.
Q: How about root?
A: Sure. Use Chainfire's SuperSU 1.25+. Put it on your device, reboot to recovery, and flash it. Easy.
Downloads
Download Odin 3.07
Download Recovery TAR
Download Recovery TAR (Mirror)
Source
OUDHS CWM-Based Recovery - Github
Device files for jfltetmo - Github
Credits:
Shabbypenguin: for being made of 99.99% pure awesome, or liquid metal (but seriously he did this, not me)
Garawynn: assistance in setting up jftle-common items
mattlgroff: testing of pre-final build
Cyanogen (Steve Kondik): fixes to jflte-common tree
Koush and the entire CyanogenMod project: CWM itself
Donations
This is not, and will never be donationware. However, bandwidth and time isn't free. The donation button below leads to Shabbypenguin. Your generosity - if you feel like showing it - is highly appreciated! Thank you!
P-O-S-T :: R-E-S-E-R-V-E-D
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original artwork by Pendulum via Gasolin3.
...for future use.
Follow me on Twitter @k0nane and @publik0! Follow Shabby on Twitter @Shabbypenguin!
Join the OUDHS and I on IRC at irc.freenode.net #oudhitsquad, or via the webchat link in my signature.
404 error on the odin download, but found another through google
cant wait to add this though.
TheAtheistOtaku said:
404 error on the odin download, but found another through google
cant wait to add this though.
Click to expand...
Click to collapse
Fixed.
ermahgerd dats me!
flashed and working. thanks for the work
shabbypenguin said:
ermahgerd dats me!
Click to expand...
Click to collapse
Ermahgerd it's the guy with the magic and the win!
e: If the text looked too small to you, folks, redownload and reflash the recovery or not.
Though I Bricked, LOL
I'm such a lame sometimes and this is a heads up to anyone else who might goof up like this.
I followed instructions per OP, put phone into download mode, or so I thought. I turned my device off, held the power& vol down button but did not hit the vol-up button to fully go into download mode.
Then I ran Odin and it said failed. When I tried to restart the device - I had a yellow triangle symbol with a firmware error message. I panicked for a moment , then tried to get into download mode again and did it right this time, flashed recovery, all good :good:. The font is kind of crazy colorful, but thank god I didn't botch it up too bad.
Just an FYI in case someone else get's that firmware error message, only a soft brick so far.
Edit - attached picture of recovery and that zany font, lol.
Awesome! You and shabby make me feel like I'm back on sprint again lol. Good thing since both of you rock but man did sprint suck.
glensta said:
The font is kind of crazy colorful, but thank god I didn't botch it up too bad.
Click to expand...
Click to collapse
The font is intentionally colorful. As for Odin errors... well, Samsung stock USB cables and all. Any former GS1 series owners will know what I mean. (It's more likely to be a bad download now.)
Dulanic said:
Awesome! You and shabby make me feel like I'm back on sprint again lol. Good thing since both of you rock but man did sprint suck.
Click to expand...
Click to collapse
I remember you.
Dulanic said:
Awesome! You and shabby make me feel like I'm back on sprint again lol. Good thing since both of you rock but man did sprint suck.
Click to expand...
Click to collapse
id rather forget i was ever on sprint......the e4gt was a great phone. just crappy service
now we just need some awesome roms to flash with this awesome recovery and its the perfect phone
had phone 2 hrs. rooted and recovery! Can't wait for all the goodness..
Worked! I love this and how quick everything is going compared to many other phone experiences I had. I have a harder time tying then having the device rooted and recovery. Not sure how someone could brick their device doing this.
i cant seem to get odin to see my phone.
when i have the phone on and useable, if i open odin, i see that it find it on COM3
when i reboot, then press power + vol up, i get it into download mode (is it normal that the android has a red triangle above it?) and open odin again, it doesnt see it.
i have usb debugging enabled.
wavrunrx said:
i cant seem to get odin to see my phone.
when i have the phone on and useable, if i open odin, i see that it find it on COM3
when i reboot, then press power + vol up, i get it into download mode (is it normal that the android has a red triangle above it?) and open odin again, it doesnt see it.
i have usb debugging enabled.
Click to expand...
Click to collapse
That wasnt download mode...
Do this to go to it
Code:
adb reboot download
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
That wasnt download mode...
Do this to go to it
Code:
adb reboot download
Click to expand...
Click to collapse
Or READ THE OP like the big red text said to - download mode is Vol Down + Power. Recovery is Vol Up + Power.
Any chance to get the recovery to download back up to sdcard. Kind of short on memory since we only get 9gb of phone storage
cbetso said:
Any chance to get the recovery to download back up to sdcard. Kind of short on memory since we only get 9gb of phone storage
Click to expand...
Click to collapse
"Backup to external SD card"
cbetso said:
Any chance to get the recovery to download back up to sdcard. Kind of short on memory since we only get 9gb of phone storage
Click to expand...
Click to collapse
I think the 'backup to external sdcard' option is what you are looking for...
Can't see with all the pretty color thanks
Related
Hey guys, I'm new here and im really new to Android, i decided to switch over from apple because they are lame... I bought a samsung galaxy s3 AT&T 16gb, roughly 2 n a half weeks ago. I was looking at the OMEGA rom and i read that i had to be rooted first so i tried to root my phone and when i used odin, it said my phone was incompatible with the root file. I then unplugged and tried to reastart my phone but it put me at the recovery screen that says i need to plug my phone into kies for restoration, i did that and my phone wasn't detected... It wouldn't let me start the phone back up and the only thing i could do was the download transfer... I then tried to fix it by doing this ...
http://forum.xda-developers.com/showthread.php?t=1506330
I open odin and used that tar file and it said everything was successful, and that my phone was reastarting, but it started up to the words Samsung and turned off... It won't power on for the reset volume up+ home + power. It starts to start up once i do those keys but not always, and if it starts up it says SAMSUNG and at the top left there is a blue text ( words ) that say something but i cant read them in time and the phone turns off.. I am still able to get into the DOWNLOAD mode but it also doesn't let me sometimes only if it's connected to the computer and when i hold volume down plus power it goes into the download mode. I'm really upset, i know it takes time to fully understand all of the techniques to flashing, roms, and other things.. Im a noob and i really hope to get my phone working again... I really would appreciate if someone could help me out.. I didn't understand how to back it up and thats where i went wrong i should of spent time figuring it out but i didnt....
My phone is AT&T sgh 1747.
Please guys, help me out. I am willing to donate a couple bux for someone that can guide me through this process of fixing my phone and putting it back to exactly stock and brand new like out of the box from att.
Update* Those blue words in the right hand corner say Recovery Booting, but then the phone kicks back off again.
Go into download mode and flash a stock rooted ROM... use Odin. Reinstall drivers and use OEM cord to connect with if it's giving you problems. Windows 7? If you can get into download mode your not bricked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Go into download mode and flash a stock rooted ROM... use Odin. Reinstall drivers and use OEM cord to connect with if it's giving you problems. Windows 7? If you can get into download mode your not bricked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your reply, Like i said im a noob currently with roms am flashing an all that stuff could you please guide
Me step by step? I dont really understand what drivers i would have to reinstall? and yes i am on windows 7. Also what options would i set in odin to do this?
First off are you releasing the buttons as soon as you see the screen with the blue words, if your not you should be, if you are and still get reboots I would suggest you follow the directions in the thread I will link below. The image you will need is the AT&T image ending with I747UCALG1.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
This will give you stock with root only. Then if you so choose you can follow the third option in that thread to install a custom recovery.
jethro650 said:
First off are you releasing the buttons as soon as you see the screen with the blue words, if your not you should be, if you are and still get reboots I would suggest you follow the directions in the thread I will link below. The image you will need is the AT&T image ending with I747UCALG1.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
This will give you stock with root only. Then if you so choose you can follow the third option in that thread to install a custom recovery.
Click to expand...
Click to collapse
When i click PDA it's not locating the file unless i type it in into where the file is written in the text box.. Once its in odin, i click pda load that file.. and its saying this...
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Why is it doing this?
In that thread i dont see a stock odin tar which is says to use first. Im currently looking for a stock odin tar for my 1747 att if anyone already has it please post it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here's a screen shot.
Update.. I re- did it again.. I used this file I click on PDA and put this in pda-odin-att-stock-kernel.tar.. after that was done. the phone still keeps doing the same thing.. Im trying to use this file root69_ATT_I747UCALG1.7z but its not working?
update* I used http://forum.xda-developers.com/showthread.php?t=1727443 and now it does the same thing but now it shows Samsung Galaxy s3, and it shows on my computer drivers installing... But then after like 30 seconds it says drivers stopped installing and the fone vibrates and i still can't get it to boot into recovery.. i can still get it into download mode... The only thing it fixed was now i can see Samsung Galaxy S3 which it didn't do until i used his file... Mine is the international gsm att 1747 model. Ugh.. I really need to get it fixed.
You need to unzip the .7z file you download so that it ends in .tar then it should work, that is step two in the link I posted for you. Your screenshot shows you trying to flash the .7z file, BUT....did I see you mention international version....that's a completely different phone or did I read your post wrong?
twistedpwnsj00 said:
Mine is the international gsm att 1747 model. Ugh.. I really need to get it fixed.
Click to expand...
Click to collapse
I don't think that a international model exists in AT&T's line up. I747 is a US variant. If you have AT&T stick with the AT&T forum. Using files from a different carrier can potentially brick your phone.
Plug in the oem usb cable into the phone after its connected to the computer and after the phone is in download mode. It will recognize it. You just need the right files and ODIN will do the rest.
You can fix it via Kies too, but you'll have to look in the help section. It explains how to do it. I searched in help to find the answer.
AT&T GS3
Rom: AOCP
Kernel: KT747
jethro650 said:
You need to unzip the .7z file you download so that it ends in .tar then it should work, that is step two in the link I posted for you. Your screenshot shows you trying to flash the .7z file, BUT....did I see you mention international version....that's a completely different phone or did I read your post wrong?
Click to expand...
Click to collapse
Please disregard that i don't know why i included that... It's not international i just double checked.
im trying to unzip that file now.
jethro650 said:
First off are you releasing the buttons as soon as you see the screen with the blue words, if your not you should be, if you are and still get reboots I would suggest you follow the directions in the thread I will link below. The image you will need is the AT&T image ending with I747UCALG1.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
This will give you stock with root only. Then if you so choose you can follow the third option in that thread to install a custom recovery.
Click to expand...
Click to collapse
I did everything and the phone booted up and works now!!!!! Thank you so much!!!!!!!!!! Does this mean its fully stock now an i dont have to factory reinstall? or should i?
twistedpwnsj00 said:
I did everything and the phone booted up and works now!!!!! Thank you so much!!!!!!!!!! Does this mean its fully stock now an i dont have to factory reinstall? or should i?
Click to expand...
Click to collapse
Use root checker from the play store to see if you're rooted. If not you'll have to try again. You are most likely in stock.
AT&T GS3
Rom: AOCP
Kernel: KT747
twistedpwnsj00 said:
I did everything and the phone booted up and works now!!!!! Thank you so much!!!!!!!!!! Does this mean its fully stock now an i dont have to factory reinstall? or should i?
Click to expand...
Click to collapse
You are fully stock(system,kernel,recovery,apps) just with root. Look in your app drawer and see if superuser or superSU is there, if not then go to the play store and get superSU, and install that to control what gets root access and what doesn't.
Or just stay stock till you read more of the forums....
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I followed the instructions listed here.
androidorigin. c o m /samsung-galaxy-note-4-root-how-to/
It did not work and I am now stuck on the screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
I tried Kies and it says it is not compatible.
Anyone have the stock rom or know of a way to get this root?
I am fairly tech savvy but this is my first time rooting.
travr6 said:
I followed the instructions listed here.
androidorigin. c o m /samsung-galaxy-note-4-root-how-to/
It did not work and I am now stuck on the screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
I tried Kies and it says it is not compatible.
Anyone have the stock rom or know of a way to get this root?
I am fairly tech savvy but this is my first time rooting.
Click to expand...
Click to collapse
There are no Roms or stock image files that I am aware of. When someone releases one or the other. Flash TWRP in Odin and flash new rom through TWRP or Odin stock image.
Sent from my SPH-L900 using XDA Free mobile app
http://shabbypenguin.com/?developer=Sprint_Note_4-trltespr&folder=Stock-NIE
^^^^ this guy just saved your ****!
Sent from my SPH-L900 using XDA Free mobile app
fatboypup said:
http://shabbypenguin.com/?developer=Sprint_Note_4-trltespr&folder=Stock-NIE
Click to expand...
Click to collapse
when you flash via odin, do you see the message 1 succeeded and 0 failed of do you see 0 for both?
Thanks but I think I figured it out.
I tried using 4 different versions of ODIN.
I also used different versions of the MD5 files.
I finally got one to stick and I appear to be rooted.
http://www.sammobile.com/firmwares/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
travr6 said:
Thanks but I think I figured it out.
I tried using 4 different versions of ODIN.
I also used different versions of the MD5 files.
I finally got one to stick and I appear to be rooted.
Click to expand...
Click to collapse
Anyway you could share what you did and which links worked for you? Don't be greedy with detailed info! =)
TheTOBster87 said:
Anyway you could share what you did and which links worked for you? Don't be greedy with detailed info! =)
Click to expand...
Click to collapse
Just for everyone's info: the stock tar is located in the "general" section of this forum (Sprint galaxy note 4)... Easy to find.
Cf-auto-root is here:
http://forum.xda-developers.com/showthread.php?t=2897428
Instructions are in the OP.
Just odin the one you need for your purposes (stock tar or auto root) and your good to go (Phone must be in download mode of course).
jhill110 said:
Just for everyone's info: the stock tar is located in the "general" section of this forum (Sprint galaxy note 4)... Easy to find.
Cf-auto-root is here:
http://forum.xda-developers.com/showthread.php?t=2897428
Instructions are in the OP.
Just odin the one you need for your purposes (stock tar or auto root) and your good to go (Phone must be in download mode of course).
Click to expand...
Click to collapse
I already tried rooting before I found XDA, and now my Note 4 is bricked or soft bricked? idk. Can you or anyone provide the direct links to what I need to download?
http://androidromupdate.com/2015/03...axy-note-4-5-0-1-lollipop-stock-firmware-tar/
TheTOBster87 said:
View attachment 3330055
I already tried rooting before I found XDA, and now my Note 4 is bricked or soft bricked? idk. Can you or anyone provide the direct links to what I need to download?
Click to expand...
Click to collapse
Stock OB7 tar here:
http://forum.xda-developers.com/showthread.php?t=3056478
Use Odin to flash it. If you can boot to custom recovery now... Do it and wipe everything but internal & external storage first x 3.
Then:
Odin Cf-auto-root as in my prior post
Then:
TWRP Recovery here:
https://twrp.me/
Use Odin to flash it. You WILL be good to go.
Now re-setup your phone.
Hard Bricked Note 4 Sprint
I have a hard Bricked note 4 from sprint that just landed in my possession. Phone appears dead but when I plug into the computer i get the Qualcomm driver not found. Wondering if anyone can point me to a solution. Thank you of course in aadvance.
gamethriller said:
I have a hard Bricked note 4 from sprint that just landed in my possession. Phone appears dead but when I plug into the computer i get the Qualcomm driver not found. Wondering if anyone can point me to a solution. Thank you of course in aadvance.
Click to expand...
Click to collapse
If you can get into download mode (volume down, home button & power button at the same time) then go to this link, read the OP carefully, follow the instructions and and you should be ok.
http://forum.xda-developers.com/showthread.php?t=3176288
jhill110 said:
If you can get into download mode (volume down, home button & power button at the same time) then go to this link, read the OP carefully, follow the instructions and and you should be ok.
http://forum.xda-developers.com/showthread.php?t=3176288
Click to expand...
Click to collapse
Ok guys Ive tried every post I can find on getting TWRP on my phone. I have the latest Odin3 v3.10.6.exe, the latest TWRP, twrp-2.8.7.0-trltespr.img.tar and tried, openrecovery-twrp-2.8.5.0-trltespr.img.tar, I have followed the posts and pulled the usb, then the battery for 30 seconds. I have unchecked the auto reboot, left it checked, tried it in the AP and BL slots and I cant get a custom recovery to stick. Here is the stats on my phone, Im at my wits end with this any help or suggestions would be much grateful. Ive already bricked it with cf autoroot and reinstalled the stock rom. Im wondering if I shouldn't of let it auto activate? Does sprint have a kill mode now for TWRP?
Software Version, N910PVPU4COG5
HARDWARE VERSION N90P.O5
ANDROID VERSION 5.1.1
BASEBAND VERSION SAME AS SOFTWARE VERSION
KERNEL VERSION
3.10.40-530320
DPI!SWHE8820 #1
BUILD NUBMER
LMY47X.N910PVPU4COG5
SECURITY SOFTWARE VERSION
MDF V2.0 RELEASE 1
VPN V1.4 RELEASE 5.2
KNOX VERSION
KNOX 2.4.1
Where am I missing it???
jhill110 said:
If you can get into download mode (volume down, home button & power button at the same time) then go to this link, read the OP carefully, follow the instructions and and you should be ok.
http://forum.xda-developers.com/showthread.php?t=3176288
Click to expand...
Click to collapse
No the phone won't get into anything or show anything. It's hard Bricked not soft bricked.
Johniex said:
Ok guys Ive tried every post I can find on getting TWRP on my phone. I have the latest Odin3 v3.10.6.exe, the latest TWRP, twrp-2.8.7.0-trltespr.img.tar and tried, openrecovery-twrp-2.8.5.0-trltespr.img.tar, I have followed the posts and pulled the usb, then the battery for 30 seconds. I have unchecked the auto reboot, left it checked, tried it in the AP and BL slots and I cant get a custom recovery to stick. Here is the stats on my phone, Im at my wits end with this any help or suggestions would be much grateful. Ive already bricked it with cf autoroot and reinstalled the stock rom. Im wondering if I shouldn't of let it auto activate? Does sprint have a kill mode now for TWRP?
Click to expand...
Click to collapse
Ok, how exactly did you get to 5.1.1? OTA?
Hey everyone,
I just bricked my T805. I was following this guide:
[OFFICIAL] LOLLIPOP 5.0.2 /SM-T800/ SM-T805/ Firmwares T800XXU1BOCC / DOWNLOAD / ROOT
http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
Installing Lollipop Firmware
Instructions:
1. Download the needed firmware from above.
2. Download Odin_3.10.0 from the attached file below
3. Open Odin, select AP and than select your firmware.
4. Make sure you have installed all samsung drivers
5. Shut down your Tab S.
6. Open download mode by holding volume down, home button and power button.
7. Connect it to your PC.
8. LEAVE EVERY THING AS IT IS IN ODIN, OTHERWISE THERE WILL BE A CATASTROPHE (If you select something wrong.)
9. When your tablet is connected, there will be a blue box in odin.
10. Hit start and wait
11. It will reboot and you will get the latest firmware from samsung.
Click to expand...
Click to collapse
So I was in Download mode, klicked on Start in ODIN.
After one minute, this is what followed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Tab hangs in the Download mode screen...
USB connection does not work, PC is not recognizing the tab anymore.
Power off does not work, no chance to power down or reset the device (have to wail 'til battery is empty?)
Anyone knows what to do?
Thanks!
sheng1337 said:
Hey everyone,
I just bricked my T805. I was following this guide:
[OFFICIAL] LOLLIPOP 5.0.2 /SM-T800/ SM-T805/ Firmwares T800XXU1BOCC / DOWNLOAD / ROOT
http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
So I was in Download mode, klicked on Start in ODIN.
After one minute, this is what followed:
The Tab hangs in the Download mode screen...
USB connection does not work, PC is not recognizing the tab anymore.
Power off does not work, no chance to power down or reset the device (have to wail 'til battery is empty?)
Anyone knows what to do?
Thanks!
Click to expand...
Click to collapse
You didn't read the WHOLE THREAD. If you had you wouldn't have had to make this unnecessary post.
Your image isn't showing.
californiarailroader said:
Your image isn't showing.
Click to expand...
Click to collapse
Use a browser.
Got ya, it must be a bug with Tapatalk. It looks like you did everything right, I followed those same instructions to flash my SM-T700 and I had no issues. I'm sorry about the brick, I've done it once and it's upsetting for sure.
Edit- Did you make sure you had all the drivers installed correctly and the PC detected and installed everything?
californiarailroader said:
Got ya, it must be a bug with Tapatalk. It looks like you did everything right, I followed those same instructions to flash my SM-T700 and I had no issues. I'm sorry about the brick, I've done it once and it's upsetting for sure.
Edit- Did you make sure you had all the drivers installed correctly and the PC detected and installed everything?
Click to expand...
Click to collapse
Hidden.img part of that file fails unless have a vodafone locked tablet. This was VERY well explained. Flash the latest T805 UAE firmware and it will be fine, no loss of data. READ BEFORE YOU FLASH!
lynxblaine said:
Hidden.img part of that file fails unless have a vodafone locked tablet. This was VERY well explained. Flash the latest T805 UAE firmware and it will be fine, no loss of data. READ BEFORE YOU FLASH!
Click to expand...
Click to collapse
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Restart with the download mode 3 button combo then flash the UAE firmware.
sheng1337 said:
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Click to expand...
Click to collapse
You're almost there, you have nothing more to do than boot to stock recovery then wipe the cache.
The tablet will then successfully boot to lollipop.
POWER +VOL DOWN + HOME to restart then immediately change to VOL UP whilst still holding POWER + HOME.
sheng1337 said:
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Click to expand...
Click to collapse
For reboot you can also press and hold a few seconds only 2 buttons HOME and VOL-
lynxblaine said:
Restart with the download mode 3 button combo then flash the UAE firmware.
Click to expand...
Click to collapse
Ok I finally managed to get into download mode again. So i'm in Odin Mode. But please, can you explain why I should flash the UAE version?
ashyx said:
You're almost there, you have nothing more to do than boot to stock recovery then wipe the cache.
The tablet will then successfully boot to lollipop.
POWER +VOL DOWN + HOME to restart then immediately change to VOL UP whilst still holding POWER + HOME.
Click to expand...
Click to collapse
I can't boot to stock recovery. I only managed to get into download mode. Recovery is not working.
UAE as it flashes nicely it's got the highest change list and it's clean - no bloat. I flashed it earlier today.
lynxblaine said:
UAE as it flashes nicely it's got the highest change list and it's clean - no bloat. I flashed it earlier today.
Click to expand...
Click to collapse
UAE is the country code for United Arabian Kingdoms, but I have a german device. Well it's not going to be worse than it is, so i will give it a try. Thanks, I will report back.
Sent from my Nexus 5 using XDA Free mobile app
sheng1337 said:
I can't boot to stock recovery. I only managed to get into download mode. Recovery is not working.
Click to expand...
Click to collapse
All you have to do is flash one.
I live in the UK, the firmware region makes little difference apart from that it can determine the bloatware you get. You will get offered the next OTA from the region you are in: but you can always manually flash any newer ROM.
Thank you very much all. I got it working, POWER+VOLDOWN to resrart, instantly HOME+VOLDOWN+POWER to switch to Download Mode. Connecting to PC, flashed UAE version with ODIN. TAB runs good now! Apps and Data were not cleared/wiped.
Thanks again!
Sent from my Nexus 5 using XDA Free mobile app
Would someone mind helping me out, I cant use my phone any more. The last thing I did was install Emotion OS and then I installed the Emotion Kernel, upon reboot the phone was stuck on the emotion boot screen after restarting the phone Im not sure how it happened however the phone went from TWRP to some recovery that looks like the lineageos logo, I cant install any updates from this recovery and my phone via USB in download mode or ADB is not detected by any computer I have tried 3 computers in my house. I have never seen this recovery screen and I do not know what to do. I downloaded a stock MM firmware and converted it to a zip file from a tutorial on here however I keep getting an error message from this recovery. I really need my phone back up and running Im not sure what the heck happened.
Continued from other posts
Quote:
Originally Posted by shadeau
Do you have any options in recovery? Even if you could perform a "factory reset" with lineage OS you'd at least be able to enable ADB and reinstall TWRP. Also, when you say that the phone isn't recognized by the computer does that mean ADB, ODIN, and your OS don't recognize the phone?
So I do have options in this Lineage Recover but I cant get anything to work, Here are my options Reboot System Now, Apply Update, Factory Reset, Advanced. I have already tried factory reset however I may have deleted the OS all together with the Wipe Data Option. When I reboot the phone it stays on the the Samsung Galaxy Note 4 Screen with the little padlock that shows my bootloader is unlocked. I was messing around with flashing betwen several roms, I went from CM 14.1 to Lineage to Emotion OS, I then flashed the emotion kernel. If I select Apply update it gives me these several options, Apply from ADB choose from emulated (no typo) choose from sdcard1. I have tried to sideload via adb shell and my pc ( have tried multiple computers) does not detect the device. I even went to the extent of reinstalling windows and all Samsung USB and ADB drivers. Selecting choose from sdcard1 I can see the various zip files on my sd card however when it goes to install any roms it fails and just says error. There is a error log however it will not let me view these. My phone before this stopped connecting to any pc's I could plug the phone in via usb and it would charge but I would not get any notifications from windows! I will seriously send money to who ever can hlep me out I do not want to shell out for a new phone. Placing the phone in download mode still works however odin will not detect the phone either lol what the heck is going on here. I do have a micro sd card reader for the mc so i can place files on the phones card but I dont know what kind of file this recovery is looking for. I do not know how this recovery even got on here as I have been using TWRP from the very beginning. Please help me
I have never seen this recovery it has the lineage os logo and just says RECOVERY. I wish I could take a picture of the screen.
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
ziggsta2 said:
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
Click to expand...
Click to collapse
Are you using the Samsung OEM USB cord?
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
good questions will try another usb cable all I have is 1 for right now
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
quinciebee said:
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
Click to expand...
Click to collapse
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
ziggsta2 said:
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
Click to expand...
Click to collapse
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
quinciebee said:
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
Click to expand...
Click to collapse
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
ziggsta2 said:
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
Click to expand...
Click to collapse
CHECK THIS OUT People are having the same issues
https://forum.xda-developers.com/android/help/phone-stuck-bootloop-t3510266
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ziggsta2 said:
Click to expand...
Click to collapse
In the advanced menu is there an option to "mount system" or something? Also see if there's a setting in there for chmod
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
ziggsta2 said:
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
Click to expand...
Click to collapse
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
shadeau said:
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
Click to expand...
Click to collapse
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
ziggsta2 said:
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
Click to expand...
Click to collapse
Well, good luck! Send me a PM if you have trouble finding the links to unlocking and rooting.
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
mojoswagger1980 said:
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
Click to expand...
Click to collapse
Ouch ! I kinda failed to take into account the very real possibility the ROM you wished to flash might not be on your device and you may have no means to get it there.....in which case flash twrp then you need (if you don't want relock bootloader) to flash a system only image . vague I know I'm thinking .....bottom line is whatever you flash cannot contain aboot image or you will relock boot loader. If on 6.0.1 boot loader there is a safeupgrade to the most recent firmware that won't relock if on 5.1.1 (bpa1 ) idk if there is one . I think there is . in fact I'm sure there is hsbrad made Odin flashable IMG for all Verizon note 4 firmware broth dev and retail . look under his profile on XDA should link you to it
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
weard1212 said:
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
Click to expand...
Click to collapse
Yeah ty I went ahead and tried last night cause I was bored ....meh lack luster . oh and I did it intentionally and just restored recovery with flashify and I just realized this probably wasn't directed at me but yep lineage
After years of flashing roms (and lurking here, especially DrKetan´s thread), I hard bricked my brand new SM-N975F. When I power it on, it goes to the screen that tells me the bootloader is unlocked, then to a welcome screen, and that is where it stays. (see pics).
I have tried the following:
1) All possible hardware combinations. (I tried at least 100 times all combinations between the keys): always the same.
2) Odin3 does not detect the phone in either screen.
3) Samsung Tool 300K does not detect the phone.
4) ADB does not detect the phone. (adb devices comes empty)
I am about to get a hammer and wreck the little guy, but I decided to ask you first.
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Sent from my SM-N975F using Tapatalk
carlitobahsoun said:
i think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Click to expand...
Click to collapse
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.
dk1965 said:
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.
Click to expand...
Click to collapse
i think ur fault was when u let it reboot / u must after odin twrp forced to reboot to custom twrp recovery and do as i think format data , well never root my samsung mobiles 3 years ago , i advice u to be cool + send private msg to dr ketan to get help OR if u have telegrams u can join many group and i know u will get help.
iam out of telegram 1 years ago too so i dont know any groups for n10+ .
try first dr ketan by pm him and wait till anyone read here and help
Sent from my SM-N975F using Tapatalk
you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk
ziotom2 said:
you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you! I tried Dr Ketan´s instructions, but no matter how hard I try, I can´t get to the download mode. I followed your instructions but the phone does not go to download mode, it just shows the "bootloader modified" screen, then the other one. Odin (nor Samsung Tool 300K) do not recognize the phone at any time, not even for a second, so I can´t flash anything to it.
Sm-n975f hard brick - solved
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!
dk1965 said:
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!
Click to expand...
Click to collapse
happy they solve it but let me be honest with u , in my country LEBANON middle east i KNOW and more knowledge than SAMSUNG'S guys inside , some small questions they wasent able to answer....so u are lucky guys that in ur country they are good knowledge to fix....
happy new year and keep enjoy ur n10+
Sent from my SM-N975F using Tapatalk
You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy
I know you said you tried 100 times, different combinations, by any chance was this - Press and hold the Volume Up + Bixby / Power buttons. - one of them? It should boot into recovery mode not download mode. I had a similar issue, I had to try and try until I was able to get into recovery, from there did wipe data/factory reset several time, and then select reboot to bootloader, then flash the latest firmware(since you probably wont know which booltloader you have on it). Also remember to used the recommended Odin by the XDA team.
Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.
Note 10+ SM-N975F/DS very very HARD BRICK --- Advice?
Andrewtst said:
Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.
Click to expand...
Click to collapse
Thank you for your feedback. I had tried that, but the recovery screen did not come up. The method you suggest will work for most cases, but in my case I had screwed up the recovery itself by flashing the wrong TWRP.
Moral of the story: do not flash the wrong TWRP, because it may corrupt your recovery, and then getting to download mode is a lot more complicated.
exocetdj said:
You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy
Click to expand...
Click to collapse
I agree with you, real good. It may not be a complete hard brick, as the repair guys did not open the phone nor changed the motherboard. Still, it was as bad as a soft brick can get....
ust buy a z3 and fix it lol
Samsung Smart Switch
As far as I know, Samsung Smart Switch is the only method to recover your phone. Download it on your pc. Launch the app and connect your phone. Choose to recover bricked phone.
I bricked about 8 different phones with the new A/B thing before I learned TWRP doesn't work and the fix was to flash the stock boot.img to both partitions with:
./fastboot flash boot --slot all <nameofboot.img>
Download the modded version of Odin. Here's a link to it in my Google Drive: https://drive.google.com/folderview?id=10F5bh4YmD0vAduSMfuqF7jQl4ho1s83a
Sent from my [device_name] using XDA-Developers Legacy app
Did it work buddy?
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issue
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.
Plz delete
---------- Post added at 06:20 PM ---------- Previous post was at 06:03 PM ----------
vs|porkchop said:
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.
Click to expand...
Click to collapse
YEAH you saved my ass!!!
Thank you wherever your are :victory:
God bless you :angel: