I flashed froyo safe will not brick rom by Eugene and now im stuck on "recovery mode, but cant do anything really . need help here at first i still had adb shell access but seem to be having a driver issue now when i try 2 boot i get Vibrant boot logo then i9000 boot logo then stock recovery mode, im running win 7 32 never flashed froyo prior and was running kernel-vibrant-stock.tar, withe stock some one please help.... even if its just getting back to dl mode so i can use odinat first adb was fine now im having a driver issue please help........
When you are in the recovery, unplug the USB from your computer for a few seconds, then plug back it, then in your terminal window type: "adb reboot"
Please go easy with the font, its abrasive.
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.
Hello friends
I am not very well versed with Android platform and OS. I had CWM ver 5.8 installed on my phone but I never used it. The ROM is Stock ROM. Today, I got a notification for update and I did the same. As after downloading the phone rebooted, it got stuck in CWM Boot loop.
I have searched Google and tried to use "adb" and "fastboot" a number of times. As I input the command "fastboot flash recovery recovery.img" I am getting a "<waiting for device>" and then nothing is happening. I have the USB driver for the phone insatalled and I am using a PC with Windows XP SP3.
Please help me friends, I am in real trouble.
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Hello
I think I've bricked my P760. When i want to run my phone it stuck on LG logo and can't boot to OS. Everything was fine but after installing fix to camera i could boot to OS my phone once and after reboot i can't boot to OS anymore. My phone has root, unlocked bootloader, custom recovery and custom ROM. I don't have acces to recovery. I have only acces to bootloader mode with fastboot (VOL+ + HOME + POWER). Then i have a note "Welcome to LG Fastboot Mode ". My computer detects it and automatically installs drivers (Fastboot interface (Google USB ID). But the problem is that in Device Manager it all time blinks. It's connected and immediately dissconects. I'm using original USB cable from LG charger. When i'm trying to use cmd in fastboot & adb files it's waiting for device all the time.
I don't know what I should do next :C
Pls help guys
SaRLaY said:
Hello
I think I've bricked my P760. When i want to run my phone it stuck on LG logo and can't boot to OS. Everything was fine but after installing fix to camera i could boot to OS my phone once and after reboot i can't boot to OS anymore. My phone has root, unlocked bootloader, custom recovery and custom ROM. I don't have acces to recovery. I have only acces to bootloader mode with fastboot (VOL+ + HOME + POWER). Then i have a note "Welcome to LG Fastboot Mode ". My computer detects it and automatically installs drivers (Fastboot interface (Google USB ID). But the problem is that in Device Manager it all time blinks. It's connected and immediately dissconects. I'm using original USB cable from LG charger. When i'm trying to use cmd in fastboot & adb files it's waiting for device all the time.
I don't know what I should do next :C
Pls help guys
Click to expand...
Click to collapse
I can help you. i just figured it out after walking away for a few weeks. pm me and ill tell you over google+ or skype and walk you through it.
i have same problem.
can someone solved it?
SaRLaY said:
Hello
I think I've bricked my P760. When i want to run my phone it stuck on LG logo and can't boot to OS. Everything was fine but after installing fix to camera i could boot to OS my phone once and after reboot i can't boot to OS anymore. My phone has root, unlocked bootloader, custom recovery and custom ROM. I don't have acces to recovery. I have only acces to bootloader mode with fastboot (VOL+ + HOME + POWER). Then i have a note "Welcome to LG Fastboot Mode ". My computer detects it and automatically installs drivers (Fastboot interface (Google USB ID). But the problem is that in Device Manager it all time blinks. It's connected and immediately dissconects. I'm using original USB cable from LG charger. When i'm trying to use cmd in fastboot & adb files it's waiting for device all the time.
I don't know what I should do next :C
Pls help guys
Click to expand...
Click to collapse
mirul_up said:
i have same problem.
can someone solved it?
Click to expand...
Click to collapse
pseudosane said:
I can help you. i just figured it out after walking away for a few weeks. pm me and ill tell you over google+ or skype and walk you through it.
Click to expand...
Click to collapse
Go through this thread http://forum.xda-developers.com/showthread.php?t=2292828 it will definitely solve your problem, from the screen-shot it seems that you are using windows 10, i'm not sure that omap4430 drivers will work on windows 10 or not, but you'll try otherwise do the process on windows 7, your phone will revive...
@Codeplex its to complicated thread.
before mine become like this my phone alway succes writing recovery via adb fastboot but now i try writing recovery via adb fastboot always filed.
flashing firmware with cmahendra method always get 15% error..
I think all dev not care anymore about our phone..,