Related
Today I tried upgrading to NFSFANS updated 6.5 rom and my phone just hangs in the bootloader. I dont get it, its never done this before... I have tried to flash back to the default bell rom and nothing... when the ruu shuts the phone down and restarts in the bootloader my phone is no longer recognized by windows and it just sits there the ruu program stays at 0% and then goes to a screeen that says my phone has been disconnected from the cradle please reatatch and run the program again.... any ideas?
Im pretty sure at the bottom on the bootloader screen the grey box use to say usb connected or something along those lines but now is blank... I dunno what to do!
TrainWreck44 said:
Today I tried upgrading to NFSFANS updated 6.5 rom and my phone just hangs in the bootloader. I dont get it, its never done this before... I have tried to flash back to the default bell rom and nothing... when the ruu shuts the phone down and restarts in the bootloader my phone is no longer recognized by windows and it just sits there the ruu program stays at 0% and then goes to a screeen that says my phone has been disconnected from the cradle please reatatch and run the program again.... any ideas?
Im pretty sure at the bottom on the bootloader screen the grey box use to say usb connected or something along those lines but now is blank... I dunno what to do!
Click to expand...
Click to collapse
Did you unlock it yet?
Maybe try re-flashing the unlocker, perhaps it got damaged somehow?
yes Ive unlocked it... I am currently running NFSFANS Rom v8.... Ill try running cokes unlocker again hopefully that works....
I am making this thread because I just bought a ATT Tilt 2 yesterday and i've been doing my best to flash this phone but it wont work! I know how to flash because I've done it plenty of times with the Fuze, but this phone keeps freezing when it gets to the percentage screen.
I've tried both methods, Via USB and Via Micro SD....
When I did the USB, everything goes fine until the percentage screen on my phone and the computer screen show up, then it stays on 0% until I get an error messages telling me to unplug my phone and retry.
When I tried Micro SD, at the bootloader screen it stays on the "Loading..." forever, it never goes to "Checking"...
So i'm thinking AT&T has something to do with this? They've found a way for customers to be blocked from flashing another rom? Please tell me there is a way out of this...i've seen other users with ATT Tilt 2's claiming they've flashed their phones...but I know I can't be the only one with this problem.
I take it you have already put Hard SPL on the device?
Plenty of other people have put custom ROMs on their Tilt 2. So it's nothing AT&T have done.
Dave
HardSL
It wont let me even put HardSPL....it wont let me do anything period... it just freezes.
The percentage screen stays at zero percent. So i'm lost.
Have you installed the enablerapinew cab? That's all I had to do in order to get HardSPL to go through on my Tilt2
http://forum.xda-developers.com/showpost.php?p=4727487&postcount=1
themasterhook2000 said:
It wont let me even put HardSPL....it wont let me do anything period... it just freezes.
The percentage screen stays at zero percent. So i'm lost.
Click to expand...
Click to collapse
I have a tilt 2 and I am running NRG Photon 10/17 ROM and loven it, but is was not easy to get to this point. My main issue was with HardSPL. I had to go through a couple extra steps in order for it to work. The first issue was a connection error, i followed the directions in the error message and went to the appropriate link.
The second issue is on the flashing page. "anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.[/I]
These helped me out and all is good. Hope this helps you as well. If not, good luck my friend.
Decer said:
Have you installed the enablerapinew cab? That's all I had to do in order to get HardSPL to go through on my Tilt2
http://forum.xda-developers.com/showpost.php?p=4727487&postcount=1
Click to expand...
Click to collapse
That was my first step as well. I did not have the link handy...
try this. http://rhodium.htc-unlocks.com/ works like a treat and although I paid for it, I am also Security unlocked.
Oke I flashed my TP2 , and the flashing had one problems that was the first time I run the flashing rom(energie) it stop on the tri-color screen, and the flashing stopt there so I ran the same flashing rom again wile the TP2 showed the tri-color and it continued the flashing process so I thought every thing is a oké.
Then the phone did it first boot on the new rom and it stopt at the rom loading screen so right a way I knew somthing is not a oké. I tried flashing with sd, hard reset, mutty, 1 minute battery out the phone. I will give these option another go if you tell me how to do it with this phone.:
So kan somebody help me with this problem.
TP2 Info :
I bought the phone in The Nederlands
I don't know the rest of the specs
SORRY
St3v3-) said:
Oke I flashed my TP2 , and the flashing had one problems that was the first time I run the flashing rom(energie) it stop on the tri-color screen, and the flashing stopt there so I ran the same flashing rom again wile the TP2 showed the tri-color and it continued the flashing process so I thought every thing is a oké.
Then the phone did it first boot on the new rom and it stopt at the rom loading screen so right a way I knew somthing is not a oké. I tried flashing with sd, hard reset, mutty, 1 minute battery out the phone. I will give these option another go if you tell me how to do it with this phone.:
So kan somebody help me with this problem.
TP2 Info :
I bought the phone in The Nederlands
I don't know the rest of the specs
SORRY
Click to expand...
Click to collapse
Go into bootloader, plugin your usb, run task 29. Then when you are finisht, go back into bootloader, plug in your usb. Then flash the rom again true your pc.
btw did you install hardspl? you didn't mention it.
Lennyz1988 said:
Go into bootloader, plugin your usb, run task 29. Then when you are finisht, go back into bootloader, plug in your usb. Then flash the rom again true your pc.
btw did you install hardspl? you didn't mention it.
Click to expand...
Click to collapse
How do i get in bootloader, is that the screen that comes after tri-color screen.
btw and yes I did use install hardspl.
St3v3-) said:
How do i get in bootloader, is that the screen that comes after tri-color screen.
btw and yes I did use install hardspl.
Click to expand...
Click to collapse
The Tri Color screen is the bootloader. When connected to the computer it should say "USB" at the bottom. Otherwise it says "Serial".
EDIT: What version is your SPL? The unlocked version is 85.
stevedebi said:
The Tri Color screen is the bootloader. When connected to the computer it should say "USB" at the bottom. Otherwise it says "Serial".
EDIT: What version is your SPL? The unlocked version is 85.
Click to expand...
Click to collapse
I used the Rhodium-HardSPL_V2_00R3.exe. I am using Radio 2.08.50.05 + task29.zip. I am using the task 29 after is pushed the power, Call, Hang Up, but i keep getting the 260 error. What I am doing wrong.
St3v3-) said:
I used the Rhodium-HardSPL_V2_00R3.exe. I am using Radio 2.08.50.05 + task29.zip. I am using the task 29 after is pushed the power, Call, Hang Up, but i keep getting the 260 error. What I am doing wrong.
Click to expand...
Click to collapse
When you go into bootloader screen, what version of SPL is displayed? It should end in 85.
stevedebi said:
When you go into bootloader screen, what version of SPL is displayed? It should end in 85.
Click to expand...
Click to collapse
I cant see the tri-color screen long enough too read what it shows.
RHOD 100 32M SS-BC
SPL - 0.85.011 MAX
MicroP(LED) 0X0A
MicroP(KEY) 0X04
Read this page for your questions.
http://forum.xda-developers.com/showthread.php?t=550540
Then go into the bootloader. Plugin your usb and flash using your pc. Just run the customruu.exe.
Or you can try flashing from your sd card. your choise
Thanks for helping guys, I have fix the phone. I did not now that I could enter bootloader with VolDown + power button, thanks to that I could fix the phone by flashing the phone with a rom.
Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(
Genesis01 said:
Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(
Click to expand...
Click to collapse
Did You HardSpl Your Phone First?
yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?
Genesis01 said:
yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?
Click to expand...
Click to collapse
Since You Can Boot Into Bootloader You Can Check Your SPL Version From There Check It Out & See What Is & Post What It Is Here.
just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000
Genesis01 said:
just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000
Click to expand...
Click to collapse
Follow The Instructions In This Thread ---> http://forum.xda-developers.com/showthread.php?t=550131
tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program
when i go to manual it will start but will hang at 0% until the comp says there was an error in connection =(
Genesis01 said:
tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program
Click to expand...
Click to collapse
Try Booting Phone Into Bootloader Screen Then Plug In Usb Cable Make Sure It Says Usb At The Bottom Of The Phone Screen Then Try To HardSpl Again.
Try Installing This Cab On Your Phone --> http://hpcmonex.net/roms/enablerapinew.cab Then Run HardSpl Again.
kk thank you, i will try. will post results as soon as i get them. Thanks again. kudos to you!
If your phone does not have the HardSPL on it, and it will not boot properly, you need to get it back into bootloader mode, wait for 'USB' to appear on the screen, and flash the stock ROM, then try again with the HardSPL program.
EDIT: To see what version of Rhodium you have, remove your battery and look at the sticker under there on the phone. you should see something like RHOD100, RHOD200, RHOD300, RHOD400, or RHOD500. RHOD100-300 is GSM. RHOD400 & 500 is CDMA. Make sure you flash the correct ROMs, radios, and HSPL for your device or you run the risk of bricking it.
Some how I got my Galaxy Tab S 8.4 to lock up. I can get it to a screen with a message on the top saying "recovery is not seandroid enforcing"
On that screen I can not seem to do anything, the other screen I can get to is the ODIN download screen. I am not overly familular with the Samsung=, yet, how do I get this to reboot back into something working. Even if I have to wipe the entire memory that is OK.
Greg
gregorywest said:
Some how I got my Galaxy Tab S 8.4 to lock up. I can get it to a screen with a message on the top saying "recovery is not seandroid enforcing"
On that screen I can not seem to do anything, the other screen I can get to is the ODIN download screen. I am not overly familular with the Samsung=, yet, how do I get this to reboot back into something working. Even if I have to wipe the entire memory that is OK.
Greg
Click to expand...
Click to collapse
How you get it to reboot back into something working depends mostly on what you did to get into the condition it's in. Since I don't know what that was, I can't help you there. But:
The good news it that as long as you can get it into Odin Download mode, you can fix it. But you have to have the right OEM ROM. It's a very simple process, but you have to follow the steps precisely. First, get the correct OEM ROM from SamMobil. If you're in a hurry, you'll want to sign up for an account (less that $10). Otherwise, you'll have to wait until the free servers have undergone their maintenance and come back online. This would also be a good time to familiarize your self with the Odin Process. You might want to start here: https://odindownloader.com/download/odin3-v3-11-2
I think i got here by running a 'reboot to recovery' widget that i was trying to remove.
my tablet now has:
ODIN MODE (in red)
PRODUCT MODE: SM-T700 (white)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
Secure Download: Enabled (dark blue)
KNOX WARRANTY VOID: 1 (0x0500)
AP SWREV: A1
then the green android with 'Downloading..... Do not turn off target!!'
Running ODIN 3.13 on Windows 10, plug in tablet nothing shows up in log, or in the ID:COM section.
Any help?
I responded too soon. Need to think some more.
It may mean Android debugging isn't enabled. If you can't get in to settings, I'm stumped on that for the moment. Try:
A different USB cable.
Make sure you're connecting to a USB 2.0 port. (I just have lousy luck with USB 3.0 ports.)
OK, tested cables they are OK. I can plug the tablet in question to my Linux laptop. When I do and run 'adb devices' in terminal the tablet shows up with 'not authorized' beside it. I am guessing USB debugging is kinda out. But is there a way to just tell it to reboot to OS and not recovery?
gregorywest said:
OK, tested cables they are OK. I can plug the tablet in question to my Linux laptop. When I do and run 'adb devices' in terminal the tablet shows up with 'not authorized' beside it. I am guessing USB debugging is kinda out. But is there a way to just tell it to reboot to OS and not recovery?
Click to expand...
Click to collapse
Here's why I'm stumped. Odin has always been just brain-dead, stupid simple for me to use, I've never needed to to use ADB. But it does run in my mind that there is a command-line mode for nearly anything and everything. And there's a wealth of resources at your fingertips. I'm sorry I can be of more help than that. But congratulations. Your learning curve just went seriously vertical.
Is it a possible Windows 10 issue? Do I have to "Run as administrator" for ODIN to work correctly?
gregorywest said:
Is it a possible Windows 10 issue? Do I have to "Run as administrator" for ODIN to work correctly?
Click to expand...
Click to collapse
My gut tells me it's not Windoze (This time.).
I've always been in the habit of running as admin, anyway. It can't hurt to try. But for sure, debugging isn't enabled. And that's the show stopper.
Hi there, sorry for the delay work had been little nuts.
OK got to try everything using "Run as administrator" and ODIN say the tablet. When I did the 'Start' function I got a FAILED error. What I did which is probably not correct, it put the Firmware file name in each of the areas to upload. Do I do that, or put it in one or two (if so which one(s)). Think I am getting close to fixing this with the help you have given me!
Getting further
OK, did get a firmware update to download. Looks like it installed the firmware. When finished rebooted the T-700. Got a message with the android bot "Updating Firmware" the T-700 reboots again, the SAMSUNG logo (grey work) comes up after a while vibrated one long 3 short, pauses about 30 seconds then vibrates again... This went on for about 2 hours, then the screen flashed a lot and powered off.
Can get back to the logo screen, some flashing, then log off.....
Any suggestions on what to try?
Greg
wellersl said:
My gut tells me it's not Windoze (This time.).
I've always been in the habit of running as admin, anyway. It can't hurt to try. But for sure, debugging isn't enabled. And that's the show stopper.
Click to expand...
Click to collapse
gregorywest said:
What I did which is probably not correct, it put the Firmware file name in each of the areas to upload. Do I do that, or put it in one or two (if so which one(s)).
Click to expand...
Click to collapse
Errr.... no. (I wish I had a screen shot of that.) After Odin is satisfied that the tab is connected, You should only click on the AP button which will open up a navigation window so you can point it to the image you want to flash. After that, Odin will check the file's integrity, then stop and wait for you to tell it START.
gregorywest said:
OK, did get a firmware update to download. Looks like it installed the firmware. When finished rebooted the T-700. Got a message with the android bot "Updating Firmware" the T-700 reboots again, the SAMSUNG logo (grey work) comes up after a while vibrated one long 3 short, pauses about 30 seconds then vibrates again...
Greg
Click to expand...
Click to collapse
Well... I'm not surprised, but I've never seen one buzz an error code. It's new territory for me. There may or may not be a file somewhere that explains what the buzzing means. (It's Morse code for "b" but that's probably meaningless.) This is the best explanation I can find for how to do this. If you're doing anything this doesn't tell you to do, it's probably wrong: https://www.**********.com/install-android-6-0-1-marshmallow-on-galaxy-tab-s-8-4-sm-t700-wifi/