Related
Is a sad day for me...i didn't knew about the Hardware Lock of Vibrants and i rooted and applied lag fix to my phone. After this i just updated the phone via Kies to JI6 then when phone rebooted got stucked after the second stage of booting with a blank screen. I tried many methods of get into Recovery or Download to flash again but can't because of Hardware Lock. Anyone knows if my problem have a solution?? Im very sad plz help.
Have you tried holding volume down and power until it boots?
Sent from my T-Mobile G2 using XDA App
Yah....Nothing!!
Try all methods:
http://forum.xda-developers.com/showthread.php?t=771247
I think you may need to use ADB commands to force it to reboot into download.
You may need to do method #4.
You may want to keep adb up and keep typing 'adb devices' to see if it sees the device when you try these different methods. If so - reboot into recovery from that.
You should be able to get into DL mode. Do you have ADB on your computer? If not, get it. Put it on the root of your C:\ and than make sure you get the drivers installed on your PC. Get ODIN and have it open. When that is done, connect your phone to your PC and boot it up. Open a cmd prompt (if you are in windows 7 you may need to open as admin) and navigate to C:\ (or where ever you decided to put ADB). At the command prompt type this exactly minus the parenthesis: "adb reboot download" Should shoot you right into DL mode. At that point you will need to flash a new ROM via ODIN, so make sure you read up.
Hope this works/helps.
I tried all that but cant get into recovery or download mode, my phone is not stuked on vibrant logo it just go to the second logo and then blank screen. Fabrication date is 08-10.
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Thx, Really wish someone had a one-click option, I guess i'll just have to jump in
I've been trying to boot into recovery for a while now, but with no luck. I installed the full SDK platform, and the Manager app downloaded and installed all the available packages (took forever). The 'push' command seemed to work fine, and when I do "adb reboot recovery" the tablet reboots, but just goes into the battery charging screen. Any idea why this might be happening, and what I can do to get into recovery?
kentoe said:
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Click to expand...
Click to collapse
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Itaintrite said:
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Click to expand...
Click to collapse
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Battery not recovery mode
I am in a similar situation, when I use adb to run recovery mode it sends me to teh battery charging screen. With the exception of that they only other things I can do are to hold power and vol to get option of using Fastboot or ODIN. I do not have any options ever to chose to go into recovery mode. Anyone know why this may be? I am running 3.1 IO version.
Thanks
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Installing the sdk works best, as drivers needed are acquired from the process! ELse there are extracted contents available on net including just the drivers, adb (and fastboot!)
Check my thread #9
http://forum.xda-developers.com/show....php?t=1136958
bakobitz said:
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Click to expand...
Click to collapse
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Berner said:
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Click to expand...
Click to collapse
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
engljeff said:
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
Click to expand...
Click to collapse
Use the quick boot app. Works well for me. Supports power off, recovery, and normal reboot for the free version. Oh yeah but that requires root.
Sent from my GT-P7510 using Tapatalk
mughalgxt said:
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
Click to expand...
Click to collapse
yes it did.. thats why I said try that ..
On 3.1 IO too .. though I broke it within 3 weeks
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
This worked for me on Rogers 4G version
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse
so i have this phone samsung sm-g360h
which doesn't boot into system
doesn't boot into recovery ( doesn't have recovery at the first place)
doesn't boot into download mode
doesn't boot into fastboot mode (used to but after i flashed a boot it stopped i can't enter fastboot mode again)
it's just stuck at samsung prime core logo and keep restarting but i can shut it down btw
and yes it has both download and fastboot mode each one of them is different than the other
the download mode is the normal download mode (don't not turn off the target and downloading etc)
the fastboot mode is black screen with fastboot mode on the left down corner
can't do anything about it :\
hope u can help me
Mysteriom45 said:
so i have this phone samsung sm-g360h
which doesn't boot into system
doesn't boot into recovery ( doesn't have recovery at the first place)
doesn't boot into download mode
doesn't boot into fastboot mode (used to but after i flashed a boot it stopped i can't enter fastboot mode again)
it's just stuck at samsung prime core logo and keep restarting but i can shut it down btw
and yes it has both download and fastboot mode each one of them is different than the other
the download mode is the normal download mode (don't not turn off the target and downloading etc)
the fastboot mode is black screen with fastboot mode on the left down corner
can't do anything about it :\
hope u can help me
Click to expand...
Click to collapse
Follow below link
http://forum.xda-developers.com/t/galaxy-core-prime
Salman Al-Badgail said:
Follow below link
http://forum.xda-developers.com/t/galaxy-core-prime
Click to expand...
Click to collapse
i checked the website forums there is no thread about it
Solution for you is you need to flash your device with stock ROM
Salman Al-Badgail said:
Solution for you is you need to flash your device with stock ROM
Click to expand...
Click to collapse
how can i flash stock rom if i can't enter recovery,bootloader or download mode
that is my problem :\
Mysteriom45 said:
the download mode is the normal download mode (don't not turn off the target and downloading etc)
Click to expand...
Click to collapse
Wait, so that means you CAN go into download mode?
If you can, you have to do the following:
The only solution to this is to flash the stock firmware with Odin.
DISCLAIMER: I WILL NOT HOLD ANY RESPONSIBILITY IN THE EVENT THAT THIS HARD BRICKS YOUR DEVICE. FOLLOW MY INSTRUCTIONS AT YOUR OWN EXPENSE!
Now that's out of the way, let's get to it.
The only problem is, the sites that host stock firmware images have download throttling and you need to sign up. If you're willing to sign up and wait a couple of hours, you can try this:
https://www.sammobile.com/firmwares/galaxy-core-prime/SM-G360H/
Firstly, you will want to download the file. Just select your mobile carrier's country (for example, if you used O2 in the UK, it'd be O2U or O2 (just an example)), then select the download link.
You'll need to sign up, though.
Once it's downloading, in the meantime, get Odin from here if you don't already have it:
https://odindownload.com/download/Odin3_v3.12.3.zip (latest as of the writing of this post)
and, if you don't already have them, USB Drivers from here:
http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows (I didn't need them, but I advise you to use them)
Install the USB drivers first (if needed), then extract the Odin zip.
Now, you need to wait until the firmware finishes downloading.
Then, extract the firmware ZIP.
The firmware should have G361F followed by a load of random letters and numbers and have the extension .tar.md5 or .tar
Now, fire up Odin and boot your device into download mode.
Press Volume Up at the custom OS warning screen.
Now, connect your Android device to your computer and wait until Odin shows [Added!!] and your device appears as [COM:] something.
Now, click AP (or PDA) and browse to the firmware and select it.
Wait until Odin shows [Leave CS].
Now, I warn you, flashing a stock OS usually saves all your data because it only needs to flash the system files. HOWEVER, in semi-rare cases, it WILL wipe your data (but very unlikely and rare)
Here is your last chance to chicken out and leave it for now. It should be fine, though, if you followed the instructions correctly.
Now, click START in Odin and sit back, relax and DO NOT DISCONNECT YOUR DEVICE FROM THE COMPUTER until your phone reboots and (hopefully) boots up to Android!
If you can't access Download Mode or Fastboot mode, I'm sorry but you're stuffed as far as I know.
I tried to root my phone using this guide, followed it down to the word and yet my phone's stuck in a bootloop. It keeps restarting to the Poco start screen.
Ive got the stock recovery, and for some odd reason fastboot commands work only in the "FASTBOOTD" screen and not the the "FASTBOOT" screen which you get from "adb reboot bootloader" command.
I try to shut it down and it boots up back again in the same screen and is stuck there.
Im clueless and I really dont know what to do. Some help would be greatly appreciated.
edit: I tried to use the stock recovery and wipe data. No progress.
I tried to connect the phone with the MIAssistant but the app doesnt recognise the device.
I tried using the MiFlash tool to flash the stock rom, it goes on infinitely. Im currently trying to use the SP Flash tool and MediaTek Bypass tool but I havnt got any progress yet.
I promise I'm never buying MediaTek devices ever again.
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
aricooperdavis said:
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
Click to expand...
Click to collapse
It was a driver issue, thanks for the link.
What I did to get out of the bootloop:
1. Download the latest Miui rom for your version, make sure it's the recovery version and not the fastboot one.
2. Press ALL the buttons, Vol+ Vol- and Power button to shut it down for a few seconds (assuming you can't switch it off as it keeps powering back up again).
3. After it's switched off, quickly press the power and vol- button until you see the FASTBOOT screen.
4. Connect with PC, make sure you have the proper drivers and have connected with the right USB port.
5. Download OrangeFox custom recovery. It is a unofficial custom recovery, so its stability is questionable. But it does the job here.
6. Copy the OrangeFox zip and the Miui rom file to your phone's SD card or any external storage which your phone can access.
7. In your PC, extract the OrangeFox zip folder in your platform-tools folder. (The folder where you run your cmd fastboot/adb commands)
8. Open up cmd, and enter the command:
fastboot flash boot recovery.img
9. Your phone should boot up to the OrangeFox recovery. If not switch the phone off (Step 2) and press power + vol+ button for booting up to the recovery.
10. Locate your OrangeFox zip installer file in the recovery and flash it.
11. Reboot to the recovery again.
12. Locate the Miui rom and flash that. Before swiping to flash the rom, there is a check box which says something like "flash OrangeFox once the rom has been flashed". If you want to keep OrangeFox as your recovery then check it, or else leave it unchecked. Flashing roms remove custom recoveries.
13. Your phone must reboot to miui.
NOTE: You can use fastboot commands to flash the rom but I'm not very familiar with fastboot commands (I actually forgot most of them). Hence I use the recovery method.
warhead1721972 said:
It was a driver issue, thanks for the link. Should I delete this post? It isnt much big of an issue imo.
Click to expand...
Click to collapse
Great, glad you got it sorted! No, leave it up, you never know someone might stumble across it and find it useful