Database Info

[Q] Bricked from rom manager :(

So I figured that since I've used rom manager before on other devices and had no issues that I would just flash clockworkmod via the app. WRONG. Now I'm bricked with no access to adb and presumably no access to fastboot (my TF doesn't show up under fastboot devices). My computer still recognizes the tablet as a media device or something though, evidenced by the "bloop" noise when I turn it on while connected to my PC.
I am however able to access the recovery kernel (the android lying on its back with the chest open and a warning symbol above it?). I was wondering if there was ANY way at all to reflash with a proper CWM or simply revert to stock or something? Honestly I have no qualms with cracking open the device and manually accessing and editing the filesystem from its hard-drive (if that's even possible...)
Failing this, is there any way to convince Asus to replace my tablet for me? I've already gone through the root process, so it's unlocked and I assume that means there's no way to get the warranty back. I'm open to any suggestions that will make my tablet more than just a $400 hunk of plastic. I will definitely be sending the dev team for rom manager all of my annoyance... but any and all replies are appreciated...
*edit* maybe not so bricked after all?
I was able to send the recovery.img from http://forum.xda-developers.com/showthread.php?t=1668173 to the device and presumably flash it to the device...
C:\Fastboot>fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5306 KB)... OKAY [ 2.424s]
writing 'recovery'... OKAY [ 2.069s]
finished. total time: 4.493s
Click to expand...
Click to collapse
I also was able to reboot the device from fastboot, so I suppose fastboot works. I think this means I can save it? I guess I'll keep looking, but I'm still not quite sure...
edit2* Yay! Able to access CWM because of the previous link! Now to see if I can flash one of the official ICS roms...
edit3* K, well I don't have a microSD converter on hand, but every attempt to flash or boot via fastboot has failed, IDK why. I guess if I figure it out tomorrow by putting update.zip on the SD and flashing via clockworkmod, I'll post it...

power off
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks

I am in the same boat. What I did is a CWM backup, then loaded the Cyanogen mod. Decided to go back to my backup so I went to CWM Recovery. Seemed to load everything just fine but when it reboots it is just a black screen......I also cannot see the sd card in CWM and cannot access Fastboot because the MTP driver will not install (maybe because of Cyanogen)........still working on it. Pass along anything you can think of.....I will try anything at this point.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
abe_cedar said:
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks
Click to expand...
Click to collapse
Probably becasue your MTP drivers are not installed. I am having the same issues, but windows will not install the MTP driver......

Did you try to restore the recovery from rom manager? Or all you did was back it up? I ask because I too backed up recovery from rom manager but my tf300 is fine. I no now not to restore the back up.
If you did restore from rom manager. Why?

MTP
My drivers I believe are fine. I was able to adb flash the CWM before I did flash from the CWM app the wrong one. Xplodwild was saying that with the wrong CWM on the tab ( I have now the tf201 version on ) no one was able to recover. I guess I am stuck.

abe_cedar said:
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks
Click to expand...
Click to collapse
Hmmm... I can make it reboot by holding down the power button, then get into the recovery settings via the volume buttons. All that's really stuck is the bootup stuff. Although half the time fastboot recognizes it and half the time it doesn't... CWM doesn't recognize my SD either, just shows me a CWM folder.

trevor7428 said:
Did you try to restore the recovery from rom manager? Or all you did was back it up? I ask because I too backed up recovery from rom manager but my tf300 is fine. I no now not to restore the back up.
If you did restore from rom manager. Why?
Click to expand...
Click to collapse
All I did from rom manager was flash CWM. I didn't restore anything or backup anything... I should have backed it up though... Anyways, CWM works fine, so I don't think that's the problem at this point. I wish I understood more about the Android operating system, cuz I'm not sure what exactly I can blame at this point...
I flashed the Team Win Recovery Project kernel, which seems to work pretty well... it allows me to see that... there's an SD CARD partition on my main drive? wtf? lol. Anyways, it doesn't have external storage support, so that option is out. But it means that I'm able to flash things still... maybe I just need the right system file? I'll keep trying.

To push files in recovery try installing the drivers from my thread: http://forum.xda-developers.com/showthread.php?t=1680570
Recovery doesnt support external SD so this should work for you.

Northern-Loop said:
To push files in recovery try installing the drivers from my thread: http://forum.xda-developers.com/showthread.php?t=1680570
Recovery doesnt support external SD so this should work for you.
Click to expand...
Click to collapse
Hmmm... it does show up in adb devices, however I'm unable to push this way. This is what I'm seeing:
{
"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 very well may be doing something wrong, but I don't know what... This is the closest I've been so far though

BlakeC90 said:
Hmmm... it does show up in adb devices, however I'm unable to push this way. This is what I'm seeing:
[IM]http://screensnapr.com/e/IJ4Zru.png[/IMG]
I very well may be doing something wrong, but I don't know what... This is the closest I've been so far though
Click to expand...
Click to collapse
Error seems to relate to "USB Debugging Mode" I guess you didn't enable this before the brick happened?
Try "adb shell" then su
Well reading more debugging is switched on in recovery.

Northern-Loop said:
Error seems to relate to "USB Debugging Mode" I guess you didn't enable this before the brick happened?
Try "adb shell" then su
Well reading more debugging is switched on in recovery.
Click to expand...
Click to collapse
USB Debugging WAS enabled when I started all this debauchery, but I've cleared so many things and reflashed stuff so many times it very well could have reset itself or something. I'll try what you suggested though and post the results. Thanks for the suggestions, btw

Not sure it will make any difference but try putting the path in quotes
ie
adb push "c:\romfolder\roms.zip" \sdcard\ROMs
SU command wont work, doesnt work on my tab.

Northern-Loop said:
Not sure it will make any difference but try putting the path in quotes
ie
adb push "c:\romfolder\roms.zip" \sdcard\ROMs
Click to expand...
Click to collapse
using adb shell > su doesn't appear to work for me, perhaps because of it being set up in recovery?
I have little experience with adb in general, let alone adb shell, so once again I could be doing it wrong. But I don't think so...
Using quotes, however, it's taking a lot longer to run the line... I hope that means it's working XD
edit* Hmmm... can't tell if it worked or not. It won't show in recovery, but this is what showed in cmd:

BlakeC90 said:
using adb shell > su doesn't appear to work for me, perhaps because of it being set up in recovery?
[IG]http://screensnapr.com/e/A96dAy.png[/IMG]
I have little experience with adb in general, let alone adb shell, so once again I could be doing it wrong. But I don't think so...
Using quotes, however, it's taking a lot longer to run the line... I hope that means it's working XD
Click to expand...
Click to collapse
Yes it should return file sent now

Northern-Loop said:
Yes it should return file sent now
Click to expand...
Click to collapse
*sigh* it worked once, but after that just more protocol errors. I don't know if it technically worked because it doesn't show in recovery and it didn't say file sent.
...I have an option to wipe the system... that would screw things up as badly as I imagine, correct? I think I want to shy away from that, but it's the one thing in recovery I haven't tried...

Try unplugging USB cable or rebooting into recovery?
Protocol error seems to be generic error
Sent from my GT-I9100 using xda premium

Northern-Loop said:
Try unplugging USB cable or rebooting into recovery?
Protocol error seems to be generic error
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Continues to do the same thing... protocol failure... I keep messing around, but honestly I'm confused as to why it won't work... I mean what could the possible reasons be?
I've also tried flashing through fastboot, to no avail.
YESYESYES! I don't know why it decided to work this time, but for some reason, I got it! Fastboot saved me, somehow...

Great news - Has it booted now?
If so I will update my ADB/Bricked Recovery thread with the details on how to recovery from TF201 Recovery Firmware?

Northern-Loop said:
Great news - Has it booted now?
If so I will update my ADB/Bricked Recovery thread with the details on how to recovery from TF201 Recovery Firmware?
Click to expand...
Click to collapse
It's up and running fine! As far as I know, all that should be necessary is the fastboot stuff, so long as you're able to access it... If not, then I think you're SOL... I guess just flash the .29 update blob and it will work? XD I'd try it again and make sure, but I don't have the balls. I guess just tell people to try that though, and if it works, it works. Thanks so much for your help!

BlakeC90 said:
It's up and running fine! As far as I know, all that should be necessary is the fastboot stuff, so long as you're able to access it... If not, then I think you're SOL... I guess just flash the .29 update blob and it will work? XD I'd try it again and make sure, but I don't have the balls. I guess just tell people to try that though, and if it works, it works. Thanks so much for your help!
Click to expand...
Click to collapse
Thanks I'll add credit to you for being the unlucky/though lucky for getting recovery back. As we have a separate recovery I always thought it would of been possible to recovery if you flash bad rom or bad recovery.
Can you vet the info I have put into my thread http://forum.xda-developers.com/showthread.php?p=26724020#post26724020
Installed drivers, boot into to fastboot to flash recovery then fast boot system blob file?

[Q] help! think i bricked my tf700

help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S

prasse said:
help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S
Click to expand...
Click to collapse
How long did you let it sit on the Asus screen?
Which recovery and version?
I've seen my tablet take 45 minutes to boot on older versions of TWRP after a ROM flash.
This hasn't happened for quite a while however.

This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?

sbdags said:
This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?
Click to expand...
Click to collapse
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s

prasse said:
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s
Click to expand...
Click to collapse
Do yo usee ANY number flying about giving any indication as to what bootloader you're on? sbdags made an important point -- you'll need a current bootloader version to get the more recent ROMs working.
Oh, and ehh... please use interpunction -- you know, periods and commas and stuff. It makes a sentence that much more readable and understandable.

okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:

prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?

sbdags said:
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?
Click to expand...
Click to collapse
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.

prasse said:
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.
Click to expand...
Click to collapse
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.

sbdags said:
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.
Click to expand...
Click to collapse
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?

prasse said:
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?
Click to expand...
Click to collapse
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?

prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
How do you know you're on TWRP if you can't get into recovery?

sbdags said:
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?
Click to expand...
Click to collapse
okay thank you for the explanation, but no i dont have fastboot avaliable.... got the same screen as before.

ngionla appearance
Thats OK said:
How do you know you're on TWRP if you can't get into recovery?
Click to expand...
Click to collapse
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.

prasse said:
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.
Click to expand...
Click to collapse
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
{
"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"
}
Is it anything like the above image?

Thats OK said:
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
Is it anything like the above image?
Click to expand...
Click to collapse
Ye almost the excat same, i Can upload a picture when i get home... But no i dont know the difference between, your mentioned wipes sorry :s..

If it looks like that what happens when you push volume up on the RCK icon?

sbdags said:
If it looks like that what happens when you push volume up on the RCK icon?
Click to expand...
Click to collapse
see thats the difference, i only got the two last icons wipe and usb : /

That sounds like you do not have any recovery available. If you connect the tablet to the computer via SUB and pick the USB option, what happens?

Isn't the fastboot built into the bootloader? It should be always possible to recover if you can get to the recovery select screen and select fastboot, shouldn't it?

Bricked again ?

Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers

Good news, i got ADB working.
What should i do?
Rgds !

Cheered to soon, seems like all the ADB commands do not work, see ataached image.
ADB devices show a device and when i unplug it it doesnt show a device.
Funny the device name is 12345789ABCDE.....
Any ideas someone ?
{
"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"
}

Nobody knows an answer ?

martyzzz said:
Nobody knows an answer ?
Click to expand...
Click to collapse
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.

cmendonc2 said:
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.
Click to expand...
Click to collapse
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds

martyzzz said:
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds
Click to expand...
Click to collapse
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.

graphdarnell said:
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.
Click to expand...
Click to collapse
Thanks for your reply, i will give it 1 more go before i trash the TF300.
BTW i did use TWRP 2.6.X.X-4.2 i just wasnt able to flash a working rom with it, tried several but no dice...
Ill get back when i have tried.
Again thanks

martyzzz said:
Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers
Click to expand...
Click to collapse
Have you tried this, saved my bricked tab. Thought I was going to have to geta new motherboard at first...
How to unbrick TF300T

[Q] XT926 Stuck on Bootloader/Eye

Hey guys, my phone is stuck on the Droid BL with the eye thing on it. I tried to post a picture, but since this is a new account it won't let me. The phone is completely stock, no CWM, no root, no ANYTHING. I know I can factory reset it to try and make it work again, but I need the pictures from it for the previous owner. Is there any way to recover anything, or will I have to wipe to stock to have it work again?

ExPwN said:
Hey guys, my phone is stuck on the Droid BL with the eye thing on it. I tried to post a picture, but since this is a new account it won't let me. The phone is completely stock, no CWM, no root, no ANYTHING. I know I can factory reset it to try and make it work again, but I need the pictures from it for the previous owner. Is there any way to recover anything, or will I have to wipe to stock to have it work again?
Click to expand...
Click to collapse
power + vol up and down
then go to recovery
then vol up and down and select factory reset

billycar11 said:
power + vol up and down
then go to recovery
then vol up and down and select factory reset
Click to expand...
Click to collapse
Obviously you didn't read my post. I KNOW I can do that, but I need the pictures for the previous owner. I'm not an idiot.

okay when booting hold both volume + and - that should get you in safe mode you can tell by the watermark on the bottom.
{
"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"
}
also if this does work you can sbf with rsd lite and delete the part of the script that says user data and get var this will keep all the data on the phone and only re flash the system

billycar11 said:
okay when booting hold both volume + and - that should get you in safe mode you can tell by the watermark on the bottom.
View attachment 2744200
also if this does work you can sbf with rsd lite and delete the part of the script that says user data and get var this will keep all the data on the phone and only re flash the system
Click to expand...
Click to collapse
Thanks, I'll try it when I get home

billycar11 said:
okay when booting hold both volume + and - that should get you in safe mode you can tell by the watermark on the bottom.
View attachment 2744200
also if this does work you can sbf with rsd lite and delete the part of the script that says user data and get var this will keep all the data on the phone and only re flash the system
Click to expand...
Click to collapse
Ok so I'm not sure when I hold the buttons. If I hold all three while booting it takes me to the boot mode selection menu. Also, what is sbf and rsd lite? I've never done anything with this phone before.

ExPwN said:
Ok so I'm not sure when I hold the buttons. If I hold all three while booting it takes me to the boot mode selection menu. Also, what is sbf and rsd lite? I've never done anything with this phone before.
Click to expand...
Click to collapse
http://www.talkandroid.com/guides/beginner/how-to-boot-your-android-phone-or-tablet-into-safe-mode-for-troubleshooting/
You don't push all three just the volume up and down buttons

billycar11 said:
http://www.talkandroid.com/guides/beginner/how-to-boot-your-android-phone-or-tablet-into-safe-mode-for-troubleshooting/
You don't push all three just the volume up and down buttons
Click to expand...
Click to collapse
It didn't work. Still stuck on the eye. I guess I'll tell her they're gone unless there's something else I can try?

ExPwN said:
It didn't work. Still stuck on the eye. I guess I'll tell her they're gone unless there's something else I can try?
Click to expand...
Click to collapse
i may be able to help, i have a couple questions.
-do you know how it got stuck like this? any details may be helpful
-if i give you a modified one click script to use, do you know how to put the phone into fastboot and have the moto drivers setup on your pc to use it?
sorry if thats a dumb question, but this will go faster if i know what you know.

bweN diorD said:
i may be able to help, i have a couple questions.
-do you know how it got stuck like this? any details may be helpful
-if i give you a modified one click script to use, do you know how to put the phone into fastboot and have the moto drivers setup on your pc to use it?
sorry if thats a dumb question, but this will go faster if i know what you know.
Click to expand...
Click to collapse
She said that it just rebooted itself while she was on an app one day, and it was fine for a day, then it died and it wouldn't boot back up. She said she got it to boot ONCE (WHY THE **** DIDN'T SHE BACK IT UP THEN) and then she rebooted and it wouldn't start.
Yes I know how to do FB and I do have the moto drivers already.

ExPwN said:
She said that it just rebooted itself while she was on an app one day, and it was fine for a day, then it died and it wouldn't boot back up. She said she got it to boot ONCE (WHY THE **** DIDN'T SHE BACK IT UP THEN) and then she rebooted and it wouldn't start.
Yes I know how to do FB and I do have the moto drivers already.
Click to expand...
Click to collapse
ok, im uploading the file, it will be about an hour.
its not guaranteed to work but i think it will. i removed the wiping commands so it should reflash everything stock but not touch the data partition, again not guaranteed but i removed the commands.
ill post back when its done.

bweN diorD said:
ok, im uploading the file, it will be about an hour.
its not guaranteed to work but i think it will. i removed the wiping commands so it should reflash everything stock but not touch the data partition, again not guaranteed but i removed the commands.
ill post back when its done.
Click to expand...
Click to collapse
So what am I doing, flashing a modified firmware?

ExPwN said:
So what am I doing, flashing a modified firmware?
Click to expand...
Click to collapse
no, its 100% stock. its just going to re-flash the key partitions and should not touch data which is a different partition. im hoping you just have a corrupt file that will be replaced by the re-flash.
if this doesnt work, i have one more idea to use rsd, but i will have to give you another modified file.
im optimistic the utility will work though and we wont have to try rsd.

bweN diorD said:
no, its 100% stock. its just going to re-flash the key partitions and should not touch data which is a different partition. im hoping you just have a corrupt file that will be replaced by the re-flash.
if this doesnt work, i have one more idea to use rsd, but i will have to give you another modified file.
im optimistic the utility will work though and we wont have to try rsd.
Click to expand...
Click to collapse
So what do I use to flash this firmware? Odin or something else?

ExPwN said:
So what do I use to flash this firmware? Odin or something else?
Click to expand...
Click to collapse
no, its a 1 click utility. you just put the phone into ap fastboot, connect to your pc, then open the utility and follow the instructions. its very simple. i removed everything from the utility except the option you need.

bweN diorD said:
no, its a 1 click utility. you just put the phone into ap fastboot, connect to your pc, then open the utility and follow the instructions. its very simple. i removed everything from the utility except the option you need.
Click to expand...
Click to collapse
Sweet, thanks!

ExPwN said:
Sweet, thanks!
Click to expand...
Click to collapse
ok mediafire is not playing nice today and restarted my upload.
lets do this another way.
download this file http://www.mediafire.com/view/vda0q55kocydsci/WindowsUtility.bat
then download this one http://www.mediafire.com/download/ucae9ljgfpda2jc/DROID_RAZR_HD_Utility_1.34.rar
extract the second file to your desktop (its already in a folder), inside near the bottom is a "windows utility" file, delete it then copy the first file i posted in its place.
next follow the instructions in my other post to flash then double click the windowsutility file to start the utility and follow the instructions.

bweN diorD said:
ok mediafire is not playing nice today and restarted my upload.
lets do this another way.
download this file http://www.mediafire.com/view/vda0q55kocydsci/WindowsUtility.bat
then download this one http://www.mediafire.com/download/ucae9ljgfpda2jc/DROID_RAZR_HD_Utility_1.34.rar
extract the second file to your desktop (its already in a folder), inside near the bottom is a "windows utility" file, delete it then copy the first file i posted in its place.
next follow the instructions in my other post to flash then double click the windowsutility file to start the utility and follow the instructions.
Click to expand...
Click to collapse
It just says waiting on device

ExPwN said:
It just says waiting on device
Click to expand...
Click to collapse
hmm, thats not good
your on the fastboot screen? phone should have a bunch of text including "device is locked, status code(some number)" should also say on the phone "usb-connected" etc etc
latest moto drivers?
try a different usb port, usb 2 port not 3
try a different usb cable
one of those items is usually the problem

bweN diorD said:
hmm, thats not good
your on the fastboot screen? phone should have a bunch of text including "device is locked, status code(some number)" should also say on the phone "usb-connected" etc etc
latest moto drivers?
try a different usb port, usb 2 port not 3
try a different usb cable
one of those items is usually the problem
Click to expand...
Click to collapse
I used a different cable. The one I was using was charge only for some reason. I'm waiting for it to finish now

Note 5 bricked

Good Morning
I have spent all night trying to determine how to unbrick my brand new Note 5. I was able to use Odin to root the device, but then when I rebooted after trying to install TWRP, it is just plain bricked. I cannot get Odin to install any firmware, i can boot into recovery mode, but wiping data and cache does nothing. I get a constant bootloop that says Kernel is not SEAndroid and Custom Binary blocked by FRP.
Every time i plug the phone into the laptop, it says that the USB device is unrecognizable. I have installed Samsung USB drivers. I am just at a loss, Odin fails every time.
I will admit that I am a pathetic noob and should have waiting a longer time to do this. I had just given up my iPhone on Sunday.
Any help would be appreciated.

Delete the Samsung drivers and then reinstall them, that may get your computer to recognize your device. As far as the rest idk

Trizen said:
Delete the Samsung drivers and then reinstall them, that may get your computer to recognize your device. As far as the rest idk
Click to expand...
Click to collapse
I have done that several times so far. The thing is, the system says not reco. but Odin sees it. I can boot into both download and recovery. So is this considered soft or hard bricked?

molodoko said:
I have done that several times so far. The thing is, the system says not reco. but Odin sees it. I can boot into both download and recovery. So is this considered soft or hard bricked?
Click to expand...
Click to collapse
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.

Brava27 said:
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.
Click to expand...
Click to collapse
I have used Odin 3.09 and 3.10.7. I got my firmware from Sammobile and search by my device model SM-N920T. I have tried this on two different machines, Win8 and Win10. Someone on another thread asked me to try a few different ways to attempt so I will try this:
One "trick" that might work:
Without your phone plugged-in to your PC,
Set up ODIN w/the firmware of choice,boot-up your phone,plug-in to PC,then,boot into download mode while plugged-in.
Try this,or several variations of it.
I had to do this using ODIN on my Note5 to get programs/ROMS to load up.
This isn't common,but,I've seen a few other people have to do this,it's likely a PC-Driver related thing (I have a somewhat uncommon PC,a Gateway,that may explain it)............from Kolio on AndroidForums

molodoko said:
I have used Odin 3.09 and 3.10.7. I got my firmware from Sammobile and search by my device model SM-N920T. I have tried this on two different machines, Win8 and Win10. Someone on another thread asked me to try a few different ways to attempt so I will try this:
One "trick" that might work:
Without your phone plugged-in to your PC,
Set up ODIN w/the firmware of choice,boot-up your phone,plug-in to PC,then,boot into download mode while plugged-in.
Try this,or several variations of it.
I had to do this using ODIN on my Note5 to get programs/ROMS to load up.
This isn't common,but,I've seen a few other people have to do this,it's likely a PC-Driver related thing (I have a somewhat uncommon PC,a Gateway,that may explain it)............from Kolio on AndroidForums
Click to expand...
Click to collapse
If it's bootlooping, you must go into stock recovery and wipe data, factory reset!
{
"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"
}

Brava27 said:
If it's bootlooping, you must go into stock recovery and wipe data, factory reset! View attachment 3569513
Click to expand...
Click to collapse
I have gone into recovery and wiped data however that does nothing. here are the steps I have done:
Power phone on holding the volume up, home and power buttons - it installs system update
-wipe data/factory reset
I get red line: E: failed to mount /preload (No such file or directory)
then using what was suggested in prior post
When trying to flash with Odin it gets to cm.bin and then fails.

Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Sent from my SM-N920T using Tapatalk

Brava27 said:
Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Yes i have. i grabbed the latest and the one before that. Maybe I should go one further.
I also tried using nobleltetmStockRecovery.tar.md5
I have gotten most success from this though it just hangs after NAND Write Start!!
Click to expand...
Click to collapse

molodoko said:
Brava27 said:
Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Yes i have. i grabbed the latest and the one before that. Maybe I should go one further.
I also tried using nobleltetmStockRecovery.tar.md5
I have gotten most success from this though it just hangs after NAND Write Start!!
Click to expand...
Click to collapse
That method given to me earlier was the key, it was the order in which i plugged it in, turned it on and boom it worked!!
I am not going to do this again until i am much more well versed in the Android world. Thank you to everyone who helped! :laugh::laugh::laugh::good::good::good:
Click to expand...
Click to collapse

molodoko said:
Good Morning
I have spent all night trying to determine how to unbrick my brand new Note 5. I was able to use Odin to root the device, but then when I rebooted after trying to install TWRP, it is just plain bricked. I cannot get Odin to install any firmware, i can boot into recovery mode, but wiping data and cache does nothing. I get a constant bootloop that says Kernel is not SEAndroid and Custom Binary blocked by FRP.
Every time i plug the phone into the laptop, it says that the USB device is unrecognizable. I have installed Samsung USB drivers. I am just at a loss, Odin fails every time.
I will admit that I am a pathetic noob and should have waiting a longer time to do this. I had just given up my iPhone on Sunday.
Any help would be appreciated.
Click to expand...
Click to collapse
It happened to me too i was scared i thought ihad messed my phone up but I found a solution

You can try different usb port and different cable too. And which tab you use for the installing the stock firmware? FRP lock is here because you didnt open the oem unlock before the installing customized file. You have to install stock with odin. and then factory reset and then you can open the device get the development settings and disable the oem unlock.
SM-N920I cihazımdan Tapatalk kullanılarak gönderildi

Brava27 said:
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.
Click to expand...
Click to collapse
Sure you can brick your phone, and the only thing silly about the term brick is the over use of it.