Database Info

[HELP] U8150, No Fastboot mode and Recovery Mode Fails, adb working

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...

[Q] Galaxy ace plus bricked and dead

I am using Galaxy ace Plus GT-S7500, I rooted my phone successfully and used for 2-3 months, today i did factory restore with formatting internal sd card (usb storage), after that phone rebooted to CWM recovery mode automatically and can't boot to OS... then i find this solution on xda website
" [HOW-TO] Unbrick your Transformer Prime (or not) --- Option 1a
Don't be afraid, your Prime should be recoverable. This is the good news. The bad news is, that you need quite some knowledge of ADB.
To recover your Prime (most likely) you need the following:
A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
The USB-Cable to connect the Prime to your PC
A few minutes time
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want."
after this i rebooted from CWM, then my phone stuck at the splash screen and can't switch off from power button, then i removed battery directly and reinserted and tried to switch on... nothing happens... then i come to know that MY PHONE IS DEAD.... SWITCH ON NOT WORKING, NOTHING HAPPENS IF I TRY TO SWITCH ON.. ALSO TRIED SWITCHING TO RECOVERY MODE, DOWNLOAD MODE - DOESN'T WORKS.... ALSO NO DISPLAY WHEN I CONNECT THE CHARGER...
PLEASE HELP ME SIR :crying::crying::crying:

if you can put it to ftm mode then you can flash rom using odin.i don`t remember how to enter ftm mode.use search in this forum i you will find the answer,or use google.good luck.

That's your own fault, read the guide you used. It clearly says TRANSFORMER PRIME, not Galaxy Ace Plus. You've likely overwritten the bootloader, a fatal mistake. Your only point of call now is maybe a jig, or more likely, just send it back and say something happened

[Q] Possible to flash phone from factory/test mode (not recovery mode)?

I have a Fairphone (original) and I passed the wrong file to adb sideload (yep, feeling dumb right now).
The phone now will not boot. It goes into a boot loop, even if I take the battery out, and then boot while holding power and volume up to get to recovery, it still goes into a loop.
I even tried this script to see if there was a brief window I could get into adb to repair during bootloop, but adb never finishes waiting for the device even after about 5 consecutive reboots.
If I plug the phone in to charge, the empty battery appears, but then after a few seconds it goes into a boot loop too.
Code:
#!/bin/sh
echo "Waiting for device."
./adb wait-for-device
echo "Freeze!"
./adb shell stop
I can get into factory/test mode by holding Volume Down and Power. This seems to be the only state I can get the phone into that doesn't involve a boot loop.
Factory mode looks (mostly) like this picture (my screen shows english translation as well as mandarin):
vi8.info/pic/2014-01/Factory-Mode-Menu.jpg
While in factory mode:
adb can connect
adb shell gives me a shell, but su in the shell gives me permission denied, so no root access it seems
adb sideload says error, disconnected.
fastboot cannot see the device
adb reboot bootloader takes me back into a bootloop
adb reboot recovery takes me back into a bootloop
Is there anything I can do from here to flash a working ROM onto my phone?
I'm on a Mac. I can get access to a Windows machine in a week or so and will try SP FLash when I do, but until then, is there anything that can be done with Mac only?

TF300 boot loop, twrp, no fastboot

Hi druids of android,
I have an unlocked Asus TF300 with CM-11 and TWRP 2.8.1.0
Recently I've updated CM via OTA to the latest available snapshot and after that I've done factory reset from android UI (I lost my password so I decided to create a new g. account)
Now my tablet after reset shows Asus logo, 4 penguins and it stucks on blue striped treamwin splash screen.
Splash screen flickers every 6s. I see the device by lsusb, adb devices for 5 seconds, after the device disappears for a while and it backs again. I can do some adb commands like adb shell ls, cat, rm but I can't do any fastboot command to flash recovery or system.
Any fastboot call ends with 'waiting for device'. I call it through sudo and I've configured udev according to wiki.cyanogenmod.org/w/UDEV
I've tried restart tablet with power+volUp, power+volDown, with the same results descibed above. PaperClip+VolUp turns the tablet off.
I've found /cache/recovery/recovery.log file. (can't attach whole file because I'm a fresh member)
Partitions were mounted and the loop begins after:
Code:
SELinux contexts loaded from /file_contexts
Full SELinux support is present.
I:Boot command: boot-recovery
I'm fighting with it a few evenings and I decided to ask You for help.

I have the exact same problem. Happened last night after the Wipe Data option.
I have since read that that is a horrible thing to do.
I did try this - http://forum.xda-developers.com/showthread.php?p=63269550&nocache=1#post63269550
But I am unable to get to the fastboot screen still after dd-ing. The data partition dd took hours and hours. Left it overnight.
Help would be appreciated.

SOLVED!
Got TWRP working again!!
Follow this post right under the post of which link is above!
http://forum.xda-developers.com/showpost.php?p=64591975&postcount=88
I was unable to get the adb shell commands working separately after going into #.
So I just put in
Code:
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1"
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1"
This should fix it!

Hello guys.Finally i found solve for my TF300T loop on TEAMWIN logo.I read many threads in XDA forum for this problem but nothing happens .I had no fastboot with adb ,no recovery menu with adb and combinaiton keys until get this command "adb shell recovery --wipe_data" found.First you must install naked drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2139767.Then plug usb tablet to pc(windows) and open cmd and enter the command "adb shell recovery --wipe_data"and press enter.
Sorry for my english

Gonna try this tonight. Did the same thing to my tablet yesterday. I am running the latest TWRP(Kang) and Katkiss MM 6.0.1 ver 24 Did a wipe of the cache and dalvik as I was having some issues. It then started random rebooting into Android. So I went into bootloader screen and tried to start recovery and accidently hit wipe data and got the boot loop. Now it just boots and reboots about 3 times and shuts down. I will try the naked drivers and your commands.

To point out ,that before i found solution fo my tablet,i had no fastbout wih comb-keys .My loop was only on the TWRP LOGO and never restarting or closing alone,until to press power button for 20s about to restart tablet or press reset button + power button for 20s to shut down tablet.I hope find solution and sorry fot my english again.
Thanks to tobdaryl member

[GUIDE] [TA-1032] How to unlock bootloader, install TWRP and Magisk

Code:
TRY THIS AT YOUR OWN RISK! This could brick your phone. It shouldn't but it can. If you brick your phone, or anything stops working on your phone, YOU are responsible.
Reboot combinations:
Fastboot: Shutdown and with USB cable hold power and volume down until it says FASTBOOT MODE at the bottom
Recovery: Shutdown and with USB cable hold power and volume down until the
Code:
Please release key to power off *
dissapears.
Unlocking Bootloader
Code:
Note: This will delete all user data! Backup all your data before doing this!
This part of the guide is part of the tutorial made by @Arin59 at https://forum.xda-developers.com/nokia-3/how-to/method-to-unlock-bootloader-nokia-3-pie-t4012285
First of all convert your serial number (should look like NE1*************) to MD5 Hash and enable OEM Unlock in developer options.
Then reboot to fastboot and type
Code:
fastboot oem key {HASH}
then type
Code:
fastboot flashing unlock
.
To reboot to Android, run fastboot reboot.
Installing TWRP
Code:
This will delete your user data, but it should be already deleted.
You can use any TWRP image made for this device but I had the most success with https://forum.xda-developers.com/nokia-3/development/twrp-teamwin-recovery-nokia-3-t3762512 .
Flash your TWRP Image chosen with
Code:
fastboot flash recovery your-recovery-image.img
and then reboot to recovery.
In TWRP go to Wipe and then Format Data and type yes.
Install Magisk
Install Magisk normally.

< waiting for device >
I put the phone in fastboot mode and ran fastboot with the oem key md5 hash command but it just said "< waiting for device >". I think it might be because I forgot to install the Nokia 3 USB drivers. I'm using a linux computer, do I need to find OS specific drivers?
edit: And now my phone is stuck in fastboot mode and for some reason will not shutdown no matter how long I hold down the power button for.

Totalitor said:
I put the phone in fastboot mode and ran fastboot with the oem key md5 hash command but it just said "< waiting for device >". I think it might be because I forgot to install the Nokia 3 USB drivers. I'm using a linux computer, do I need to find OS specific drivers?
edit: And now my phone is stuck in fastboot mode and for some reason will not shutdown no matter how long I hold down the power button for.
Click to expand...
Click to collapse
If you're using a linux computer, you should try running the command with sudo.
If it doesn't work, try with another cable (or computer if it doesn't work) and try again.

#AC said:
If you're using a linux computer, you should try running the command with sudo.
If it doesn't work, try with another cable (or computer if it doesn't work) and try again.
Click to expand...
Click to collapse
Thanks. I've since got it working. For some reason I had to use the -i argument (the interface argument) along with the code for the device (0x2e04) "fastboot -i 0x2e04 <command>".
However, I've recently bypassed the "NO COMMAND" screen and gained access to TWRP custom recovery but in trying to shut down the phone, it shuts down fine but only boots up in fastboot mode. Even using the fastboot reboot command from adb tools boots it up in fastboot mode. This is a problem as I need to boot it in its normal mode so I can download the magisk.zip file required for installing magisk but I seem to be unable to do so.

Totalitor said:
Thanks. I've since got it working. For some reason I had to use the -i argument (the interface argument) along with the code for the device (0x2e04) "fastboot -i 0x2e04 <command>".
However, I've recently bypassed the "NO COMMAND" screen and gained access to TWRP custom recovery but in trying to shut down the phone, it shuts down fine but only boots up in fastboot mode. Even using the fastboot reboot command from adb tools boots it up in fastboot mode. This is a problem as I need to boot it in its normal mode so I can download the magisk.zip file required for installing magisk but I seem to be unable to do so.
Click to expand...
Click to collapse
Try holding volume up and down at the same time while holding the power button.

#AC said:
Try holding volume up and down at the same time while holding the power button.
Click to expand...
Click to collapse
Thanks, it worked.
Though I tried wiping, but it didn't solve the booting issue. Unsure how to proceed at this point. I feel like I've tried everything. Actually, I just checked my /boot folder and it's empty...is that why it's always booting into fastboot?
I tried using adb to sideload the magisk.zip file but then the phone rebooted into stock recovery??
Any and all guides on this say to download the magisk.apk either into the SD card or internal storage, but I don't have a micro SD card and I can't access the normal mode of the phone to download anything.
What can I do?

I've flashed TWRP successfully but forgot to download the magisk.apk. Now whenever I boot up my phone, it boots into stock recovery mode automatically, even if I tell TWRP to reboot into system it reboots into Stock Android recovery. I can still access TWRP by holding down the up + power buttons on boot though, but I can't access the normal mode of the phone anymore.
I tried using TWRP's sideload feature with ADB tools to sideload Magisk.zip and it said it succeeded but in using TWRP's install feature to find the zip file, it wasn't in /sideload/ or /storage/ as both were empty.
How can I temporarily restore normal functionality so I can simply download the Magisk manager.apk?