i was updating my U8150 with a custom ROM (Ideos HD) and somehow i did something wrong, i did the wipe and install the custom ROM and the Kernel update at the same time. The phone was taking long time to install and when splash logo stops for a few seconds it restart and the phone continues on that more, restarting one and one more time.. then i try to see if i can enter to the Recovery mode and looks like i missed the clockworkmod mode, i cannot enter to that, then y try to see if I can enter to fastboot to reinstall the recovery image (clockworkmod) mode and i see an error message saying " Firmware Update Step 1/2 Unpacking" then after the progress bar it says "Update Failed"
i check the cmd and fastboot mode is not allowed, even the device manager is not on that mode, then doing the recovery i can enter for a few seconds to adb but because the phone is restarting i need to do a few commands on this mode....
My question is: if somehow i can flash the recovery mode with adb?? i have see that some guys do with a terminal emulator but with the phone working and the normal way I hace seeing is on fastboot mode but i cannot enter to that mode...
i just wanted to see if somehow i can install with adb the recovery or maybe entering to the adb with shell and install it from there…
any crazy idea I will try it…
Regards
i just download the original firmware and when entering fastbootmode it automatically detects the .APP File, lets see what happens...
i take the file from this >>> http://forum.xda-developers.com/show....php?t=1011527
i hope at least i can get from stock, i will see if need to do root again...
Related
Hey All,
My Dad's Xoom died over the weekend - 13months after purchase so is not covered by the warranty. He was browsing a site, it came up with a "Internet is not responding - do you want to continue to wait" message and he clicked Wait - after a second the tablet knocked off. It will not come on by pressing Power and only turns on by pressing Power and Vol +
It gets past the Motorolo logo screen and the device starts the boot animation, about 20 seconds into this it freezes and reboots - this continues in a loop. It's been GEDified and was running the last OTA update 4.1.2 - no root etc.
I can get into the stock recovery and performed a factory reset - but the same thing happens. I've also tried Update From USB with an OTG cable but the screen just shows Choose a package to install and under it has /sdcard but nothing else. I have a dummy zip on both the Flash disk and SD card so it's not reading either.
I've also tried to perform update via ADB - when I select it and connect to a PC (Win 7 32bit) it tries to install drivers but I see In Computer Management that it shows under Unknown. ADB Devices returns List of devices message but nothing under it.
I've also selected the fastboot command at boot, tried fastboot devices and the command does see the Xoom.
So my questions
1) Anyone seen anything like this issue before and know how to fix it?
2) Is it best to try to reinstall the ROM? If so, how do you suggest I can see it with ADB?
3) As I have Fastboot command, could I try to install CWM and see if that sees a ZIP on the sdcard - so I can install a new ROM.
Any help much appreciated :good:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
claned said:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
Click to expand...
Click to collapse
So just to add to this, I found the stock recovery.img, boot.img, userdata.img and system.img and used the fastboot commands to send all to the motorola - all succeeded without error....still the same problem though.
I installed RSD lite and tried a few SBF files but I'm getting an INI error - off to google possible solutions to that now
I want unlock bootloader on S.trend plus- s7580 i have adb and fastboot. Adb detecting my phone and this commend works "adb reboot bootloader" phone restarting only problem is that not boot in fastboot mode. And fastboot can't detect phone (waiting for device).
With odin 3.10.7 I installed TWRP(maybe older version file type tar text mode no buttons),with TWRP i tried install supersu 1.34 it's installing but after restart still dont have root.
There is one more problem i cant use buttons on phone to set download mode or fastboot mode, bottons just doesn't work i tried many times and nothing phone starting normal. So to use download mode i use "tool samsung 300k tool"or to boot in with TWRP i need use commend "adb reboot recovery". I don't know how push this phone to boot in fastboot mode to unlock bootloader(vol up/down +power +home doesn't work).
I would like enable root to have posibility to overclock cpu etc. And i would like to install newer android 5.1 or 6.
So can you help me and tell me what to do step by step. The phone is branded maybe this is problem ?
1 more queston if i would like delete TWRP and back to stock what need to do ? Install orginal rom ?
Samsung phones use Odin instead of fastboot, fastboot are not exist on Samsung phones
Guys,
I need help. I'm struggling for the last 3 days trying to revive my phone with no sucess. :crying::crying::crying:
I managed to put a custom rom sucessfully, but i had to make a restore on recovery mode.
During the restore process some error ocurred, something like "something not mounted", i did'nt have the ROM to flash anymore. For no reason i decied do reboot the phone.
Now i can't enter recovery anymore and the phone is froze on the "Sony Xperia" on the begginig.
Since start i'm having difficulty with the Z3 driver for Windows 10. To enter recovery mode i tryed to adb reboot recover but my adb doesn't work.
It's strange..
if i type fastboot devices it's show.
if i type adb devices it's show's "no emulators/xxx found".
I need help, don't know what to do anymore.
TLDR:
- Frozen at "Sony Xperia"
- Recovery don't enter pressing Volume Down/UP
- adb devices doesnt' work.
- fastboot devices work
Thank you!
pedroveber said:
Guys,
I need help. I'm struggling for the last 3 days trying to revive my phone with no sucess. :crying::crying::crying:
I managed to put a custom rom sucessfully, but i had to make a restore on recovery mode.
During the restore process some error ocurred, something like "something not mounted", i did'nt have the ROM to flash anymore. For no reason i decied do reboot the phone.
Now i can't enter recovery anymore and the phone is froze on the "Sony Xperia" on the begginig.
Since start i'm having difficulty with the Z3 driver for Windows 10. To enter recovery mode i tryed to adb reboot recover but my adb doesn't work.
It's strange..
if i type fastboot devices it's show.
if i type adb devices it's show's "no emulators/xxx found".
I need help, don't know what to do anymore.
TLDR:
- Frozen at "Sony Xperia"
- Recovery don't enter pressing Volume Down/UP
- adb devices doesnt' work.
- fastboot devices work
Thank you!
Click to expand...
Click to collapse
You have some choices to restor stock rom:
1) Try Xperia compagnon fron Sony ==> Software repair (not shure about the label in english version)
2) Use flashtool (google for it) and a rom (*.ftf) of your choice.
When you are back to stock, then you can install a custom rom again
HTH
Norbert
Hey,
Sounds like a corrupted system, not too sure what happened with the recovery though.
Try this out:
1. You need the phone driver and the fastboot & ADB driver. You can get the Sony phone drivers from the Xperia PC Companion. You can get fastboot & adb drivers almost anywhere, just google for them or scroll a bit through xda.
2. Unlock your bootloader if you haven't done so already here.
3. boot into fastboot mode by completely powering off the phone then holding "power+volume up" and waiting until a blue LED appears in the top left.
4. Find a custom recovery, rename it to recovery.img, navigate to the folder that contains it in CMD (i.e. cd C:\Users\USERNAME\Downloads\Android) and type "Fastboot flash recovery recovery.img"
5.You should now be able to boot into recovery again. All that's left is find a ROM of your liking, push it to the phone in ADB and install it.
Hope this helps!
Samyam25
While installing TWRP on my Samsung tab, my tablet shut off and I got this error. So after tons of research, I want to help the people that come into this problem!
Case 1:
Can't boot into the device but can boot into download mode or recovery
Solution:
Simple, go into download and use Odin/ADB to flash stock ROM.
Case 2:
Can't boot into device, download mode, or recovery
Solution:
Download ADB, and run "ADB devices"
If it shows a device, you're in luck, use "ADB reboot bootloader" and use Odin/ADB to flash stock ROM.
If it does not show up, try these tricks: https://technastic.com/samsung-download-recovery-mode/
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Command
Code:
adb reboot fastloader
doesn't exist.
Look inside here:
How to Reboot Android Device into Fastboot or Recovery Mode via ADB « My Digital Life
If you’re using Android phones, tablets or devices, which is proliferating across all markets, prices and channels nowadays, then you may want to familiar yourself with fastboot or recovery mode, which is useful when you need to troubleshoot your beloved phone from the like of Samsung, HTC...
www.mydigitallife.net
introjoe said:
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Click to expand...
Click to collapse
Hi introjoe,
Are you doing? i have the doogee s60 but i just cant root it :'( can you tell me please how did you do it, or the files you use for it? i allready tried but, when i reset and enter fastboot mode, my pc simply dont recognize it.
I want to upgrade the android system to 9 or 10, thats why im doing all o this.
Thanks in advance.
@doryan666
i wasnt able to root the device in the end unfortunately.
i tried using an unofficial twrp, but i was stuck at the main boot screen
i t seems to need some bootloader-activation-code to enter the bootloader to install a new os.
the command line would look like
adb reboot bootloader "CODE"
the activation code has not been released yet by doogee ... and most probably never will be.
sorry to say but i dont think android upgrad will be possible with this device