Hi Guys,
I have Vanir ROM installed and had a problem with SIM. It was showing a SIM card symbol instead of network bars. I wasn't able to connect to mobile network.
I decided to wipe davlik and other cache, reboot it and give it a try if it work.
After wiping memory and rebooting it I saw "No OS installed are u sure to reboot"
-- I knew at this point I was screwed. I shouldn't have rebooted it :'(
After reboot it got stuck on Google logo (Black screen, white Google logo)
Now If I try to get into bootloader/Fastboot mode it doesnt as my volume button wasnt working from some time
---- I know I should have got it repaired :'( ---
Please tell me is there any way I can go to fastboot mode
Pls guys somebody reply..
..........................................
Do you have adb set up on your computer? If so, you could probably use "adb reboot recovery" to get into recovery. Then you can download a ROM to your computer and use adb to install it with "adb sideload romfilename.zip".
Remove battery and put again and press volUp+volDown+Power to enter fastboot mode, then enter recovery and wipe all. Flash factory image and custom recovery, copy ROM on sdcard and then flash. It will connect to mobile network 100%
Is it just volume down that doesn't work? You could volume up+power for boot to recovery.
Related
Hi guys.
I had installed one of ROM's, i even don't remember the name, it was 5 months ago.
Then in Settings I pressed to reset factory data, which deleted all my applications, personal data and etc.
After that when it restarted, it stuck in TWRP recovery mode..
I tried installing several ROMs http://forum.xda-developers.com/showthread.php?t=1619550 and http://forum.xda-developers.com/showthread.php?t=1488930 but after flashing/installing it stuck again.
what should i do? :s
i tried googleing but nothing came up .. :s
Do you have the Kindle Fire Utility installed on your PC? If so you could try using that to set you bootmode back to 4000 (normal).
If you can mount SD card and move a new rom file and gapps try aokp do a full wipe factory/data ,cache,dalvik and system reflash new rom new gapps reboot or better yet flash the new bootloader via twrp and use the power button to toggle to normal boot or change bootmode
http://forum.xda-developers.com/showthread.php?t=1632375
Download and flash FFF 1.4A from http://forum.xda-developers.com/showthread.php?t=1632375
Reboot the kindle
See the blue and white logo
Press the power button
Don't press anything, it'll select normal boot
hunterhk said:
Download and flash FFF 1.4A from http://forum.xda-developers.com/showthread.php?t=1632375
Reboot the kindle
See the blue and white logo
Press the power button
Don't press anything, it'll select normal boot
Click to expand...
Click to collapse
Essentially the same thing I said in the post above but its good to have it reinforced
Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me
did you erroneously flash the boot.img to the recovery partition? that would be the only thing that would cause that i'd think..
i would retry the following.
fastboot flash recovery clockworkmod-5.8.4.0.img
fastboot flash boot boot.img
fastboot erase cache
with boot.img being the kernel provided with your cm10 rom and clockworkmod-5.8.4.0.img being the name of your CWM recovery image.
as for fastboot working intermittently I would check to make sure the cable is snugly plugged into the computer and try another cable if possible.
Vorphs said:
Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me
Click to expand...
Click to collapse
I have just overcome a similar problem myself.
Start over, and do factory reset (after nandroid). Then flash the latest clockwork recovery to your phone (CWR 5.8.4.0) using
"fastboot flash recovery <filename.zip>" in the command line
then, boot into recovery, insert usb cable and choose mount usb. simply drop CM rom zip file onto your phone form the PC.
then unmount, go back to recovery menu and select install zip from sd card, then choose your zip file. after this, select reboot system from recovery. it should work fine.
I think you may have acidentally installed the CM10 rom as recovery using the wrong syntax in fastboot.
Hope that helps
Thx for the reply's, unfortunately whenever i try to flash something using fastboot, i get "error: cannot load imagename.img". Only the erase cache command works...
Fixed it using fastbootflasher!
I can't boot up my device it's have blink sleeping android error. (my device is ze551ml running WW_2.19.40.22 firmware and never ever ROOT!!! )
I tried hold power button and press volume up button but its doesn't work.
I also can't access to recovery mode too.
It's have the same blink error message and can't pass by hold power button and press volume up button.
Oh but i can access to fastboot page.
and my computer don't recognize my phone at all(i already install driver)
Before this problem happen I get in to recovery mode try to wipe cache but i miss press and i selected "apply update from adb"
and that time my phone doesn't connected with PC. I don't know what to do so I turn off my phone.
then I open recovery mode again and select wipe cache then I go out to take a bath.
I came back and see my phone is off so I boot it.
It's booting about 2-3 mins and nothing happen so i go to recovery mode again but this time they have problem like i explain before(blink error message that can't pass by hold power button and press volume up button)
So anyone have a solution for my problem. please I really need your help!
Sorry for my bad english
Hi,
I had this when I went to wipe my system cache and it failed. Your best bet, especially if you can't get into recovery is to fastboot flash the recovery again if you have an unlocked bootloader.
If you don't you'll want to unlcok the bootloader and follow the instructions for using ADB if you're new to it: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
How can I unlock my boot loader when i can't even open up my phone.
stultus136 said:
How can I unlock my boot loader when i can't even open up my phone.
Click to expand...
Click to collapse
If you hold volume down and power, it should go to bootloader first, then you have your choices for recovery....Get it to the bootloader screen, then run the commands to unlock it...
Could you please tell me everything step by step on how to cure my phone?
I'm very noob.
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
stultus136 said:
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
Click to expand...
Click to collapse
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Same Problem
smokinjoe2122 said:
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Click to expand...
Click to collapse
Hey I'm having the same problem, how'd you get the computer to recognize that the phone was plugged in? My computer does not recognize that the phone is on when I have the flashing error screen, so ADB doesn't recognize that there is a device connected.
Hi,
I had the exact same problem, and I managed to boot up again thanks to you!
What I did :
Install ADB and Drivers
Boot my phone into Fastboot (Power+Volume Up at boot, keeping VolumeUp button pressed while booting). Don't go into any menu (do not select recovery or so). At this point your computer should recognize your Android phone when you plug it in through USB.
Open up a cmd with admin rights, navigate to adb install path by typing : cd C:\adb
Then type : fastboot erase cache
It should trigger an action on your device, and the prompt should display sth like "Cache successfully erased" (I don't remember exactly)
Finally type : fastboot reboot, press volume up while booting again, and access Recovery like usual!
Now you can try wiping your partition cache again.
Worked like a charm for me! Thanks a lot
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
Hi all,
I have a Lenovo TB3-730X tablet.
Recently I wanted to flash a custom ROM but it turned out it was not compatible and the tablet was messed up.
What I did before reaching at this messed up state was:
1) Flash TWRP recovery
2) Copied the custom ROM into SD card and installed it, the installation failed and boot failed. The tablet stuck in the logo screen forever
3) I tried to install the stock ROM back using PC and SP Flash Tool but the latter never managed to connect to my tablet.
4) I manually copied the system.img and boot.img from stock ROM into SD card and tried to install them manually using TWRP by selecting "System Image" and "Boot" partitions respectively. After this and before rebooted the tablet, TWRP reported that "No OS is installed". I went ahead and rebooted the tablet anyway and now it keeps restarting. It shows the logo screen for few seconds and then restarts over and over again. I cannot connect to TWRP recovery mode anymore as the Volume-UP / Volume-DOWN + Power button are being ignored. I am not sure if the TWRP was gone after flashing the boot with boot.img. Also the tablet cannot be connected to the PC at all because it keeps restarting and it doesn't get stable to the logo screen as before so that the USB connection cannot be established. This means I cannot use "adb" from PC to connect to recovery mode using "adb reboot recovery" command
I really stuck here and would appreciate any help.
Thanks in advance!