okay soo basically i was screwing around with twrp and messed it up and long story short, my tablet is fully functional but when i try to go into recovery mode it kind of locks up and i have to use the command;
abd reboot bootloader
just to get it back to normal. any ideas? ive been trying to get a rom. also, if you know how to fix this to get it back to the normal recovery mode thing and/or know how to get a rom on samsung galaxy tab s t-700 thats decent ( i really only want version 6+, it can even be a stock rom) and please help me with this. i dont have any more tablets other than this and i screwed up!!!!!
You can get stock roms at sammobile and flash them with Odin. Later flash twrp and magisk. It should work.
Related
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Download the latest kies from the samsung website.. and then open tools and then firmware update and initialization.. pull out the battery and type the model number and serial number kies asks.. follow the instructions.. your phone will be fine..
Sent from my GT-N7100
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Try flashing a recovery for ur device with Odin, not a ROM, just flash twrp recovery with Odin, after u flash the recovery u will be able to access recovery and flash a stock ROM through twrp. I think what happened to u is when u flashed the update it tried to right over the unlocked bootloader which caused the soft brick, try flashing the recovery for ur device and if that doesn't work try the above posters way...
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi, I'm having trouble booting after flashing the stock jelly bean rom 4.3 from tmobile. Right now it is just stuck on the Samsung logo. The problem may have been that I had installed the slimkat Kitkat rom and tried to go back to stock tmobile rom which was jelly bean. (stupid I know)
The second problem is that my volume up button is broken so I can't hold it long enough to boot into recovery. I am able to get into download mode and use odin if I get lucky and struggle with the up button but it only works in short bursts as it's damaged on the actual board and not the rocker.
Is there any other way I can get into recovery? I can't boot into the os so rebooting from there is out of the question. I'm running out of ideas now.
any suggestions would be greatly appreciated.
Flashing stock was fine. Your roms version doesnt matter, its your base firnware that does. Whenever you go between tw and non-tw roms you have to factory reset or itll hang at boot, which is what is happening to you.
Since you flashed stock, i dont know if itll work or not, but if ADB is set up on your computer, connect while in download mode, open command prompt and type
Adb devices
This will start the service and tell you if its detected.
Next type
Adb reboot recovery
If thats not going to work, youre going to need to find a way to make an odin flashable cm rom (not sure if you can), or get the the volume button fixed.
I dont know of any other way to boot recovery if you cant boot your rom as well.
DocHoliday77 said:
Flashing stock was fine. Your roms version doesnt matter, its your base firnware that does. Whenever you go between tw and non-tw roms you have to factory reset or itll hang at boot, which is what is happening to you.
Since you flashed stock, i dont know if itll work or not, but if ADB is set up on your computer, connect while in download mode, open command prompt and type
Adb devices
This will start the service and tell you if its detected.
Next type
Adb reboot recovery
If thats not going to work, youre going to need to find a way to make an odin flashable cm rom (not sure if you can), or get the the volume button fixed.
I dont know of any other way to boot recovery if you cant boot your rom as well.
Click to expand...
Click to collapse
Thanks for the reply, I do have ADB set up but unfortunately when running the command on adb it's not finding any devices. Odin finds it ok. I also have the android toolkit but it looks like it only works if the phone boots into the os..
Well I got it working now. Playing with a piece of tin foil around the volume up button finally let me hold it long enough to get into recovery. Wiping the cache got it all working properly again. thanks again.
Nice fix man!
As for adb, I figured it wouldn't work, but was worth a shot in case I was wrong. Pretty sure that it requires an insecure kernel since it didnt work though.
And just remember in the future, every time you switch between TWO and nonTW roms you have to factory reset. Glad you got it working!
hi guys
so basically i installed some roms on my note 2 but i didnt like them so i reflashed note 2's stock firmware.
when i got the phone i wasnt able to go into download mode, the problem was i could go pass Volume Up: Continue
once i reflashed the stock rom i waited for it to boot, ive dealt with difference samsung phones and from my knowldge it wont boot until i do a full wipe after the flash. i pulled out the battery and tried to get into recovery but it wont go in it.
i used adb to go into download mode and recovery mode before since it was the only option. but now i cant because it doesnt recognize the device. odin detects the device when not in download mode but wont do anything. i really need help guys.
thank u i hope someone can help
MIght be minor for you but huge for me. I dont consider myself a noob, probably the step above, but Im in a little situation. So a coworker of mines is into rooting and roms like myself. He had a sm-n910p which was only rooted running stock rom. One day while changing batteries (which one was stock and the other from anker) it just went into a bootloop. When the phone powers on it says
RECOVERY BOOTING . . . .
Samsung
GALAXY NOTE 4
Powered by android
then shuts off and starts the bootloop. When I installed CWM or TWRP it goes away but I can never really enter into recovery mode with either stock or custom recovery, and also i notice in download mode with TWRP or CWM installed it say COULD NOT LOAD NORMAL BOOT or something like that in red above ODIN MODE. I have installed all the firmwares i could find like the ANIE, BOB, and COG ones which passes on odin but just continues bootloop. I've even thought about if it has something to do with partitions and do i need pit files or something. But im done looking everywhere for answers so im just trying to get my questions answered. Your two cents on the situation would be much appreciated THANKS GUYS!!!
aspeeed said:
MIght be minor for you but huge for me. I dont consider myself a noob, probably the step above, but Im in a little situation. So a coworker of mines is into rooting and roms like myself. He had a sm-n910p which was only rooted running stock rom. One day while changing batteries (which one was stock and the other from anker) it just went into a bootloop. When the phone powers on it says
RECOVERY BOOTING . . . .
Samsung
GALAXY NOTE 4
Powered by android
then shuts off and starts the bootloop. When I installed CWM or TWRP it goes away but I can never really enter into recovery mode with either stock or custom recovery, and also i notice in download mode with TWRP or CWM installed it say COULD NOT LOAD NORMAL BOOT or something like that in red above ODIN MODE. I have installed all the firmwares i could find like the ANIE, BOB, and COG ones which passes on odin but just continues bootloop. I've even thought about if it has something to do with partitions and do i need pit files or something. But im done looking everywhere for answers so im just trying to get my questions answered. Your two cents on the situation would be much appreciated THANKS GUYS!!!
Click to expand...
Click to collapse
PM me... Don't want to say what I will say out in the open. You'll be good to go after... Noob.
Hello everyone,
So I am very new to the concepts of rooting and custom roms, and I know I should have done some more research before I started. But now I have gotten myself into a bit of a pickle. I have the SM-G920P (Sprint) S6 and earlier this week I managed to root the phone and use TWRP to download and flash a custom rom. I used MD5: 7c1d34f7ab066104c924fb7a960b57d0 to install Renegade and then the phone booted just fine. I made the mistake afterwords when I let the phone reboot, but I had not turned on the option for OEM so now my phone is stuck in a boot that gives me a FRM lock because of the custom binary. It will not let me get into the andriod recovery (volume up, home, and power) but I can get to the download mode. I cannot seem to get any firmware to flash onto the device because I always get a fail after NAND write. Any help or direction from here would be great, Thanks.
dinomut101 said:
Hello everyone,
So I am very new to the concepts of rooting and custom roms, and I know I should have done some more research before I started. But now I have gotten myself into a bit of a pickle. I have the SM-G920P (Sprint) S6 and earlier this week I managed to root the phone and use TWRP to download and flash a custom rom. I used MD5: 7c1d34f7ab066104c924fb7a960b57d0 to install Renegade and then the phone booted just fine. I made the mistake afterwords when I let the phone reboot, but I had not turned on the option for OEM so now my phone is stuck in a boot that gives me a FRM lock because of the custom binary. It will not let me get into the andriod recovery (volume up, home, and power) but I can get to the download mode. I cannot seem to get any firmware to flash onto the device because I always get a fail after NAND write. Any help or direction from here would be great, Thanks.
Click to expand...
Click to collapse
Hi, we'll walk you through it.
First off, use the PF4 firmware from here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Be sure to allow it to complete and it should reboot. If you continue to get NAND write errors you may need to try different ports on your PC or different cables.
Let us know when that completes for you.