Database Info

[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] TF101G stuck on boot, recovery not working

OK, let's start from the beginning. I installed TWRP recovery, EOS 4 and KAT Kernel successfully today and I was quite happy with the results but decided to try Revolution HD. Since I am more used to ROM Manager, I decided to change TWRP to CWM and use it for recovery. After that things got messy. First of all CWM said that it can't find sd card and secondly my TF wouldn't boot up anymore after exiting recovery. I've been messing with it for hours and can't find a solution. It only got worse and for awhile the only way I could access it through ADB was to do a cold boot and it would get stuck at the spinning EOS logo, but atleast it would allow ADB access.
Last thing I tried is this and the tablet reboots, but it's still stuck on spinng EOS logo, but I don't have to do a cold boot to get stuck there anymore
AW: [Q] TF101G stuck on boot,cannot access recovery. Any way to fix via adb maybe?
So, for all those who have the same problem as I had, I found a solution and its a pretty easy one!
In my case, it seemed to be a permission problem concerning /dev/block/mmcblk0p3. So, I went through different threads and found a suitable solution here:
http://forum.xda-developers.com/show...530337&page=20.
All you have to do is to enter terminal emulator on your device (or use adb alternatively) and enter:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
You should see the asus eee pad screen with a blue progression bar and then it should boot normally. Thanks to partio for this hint! :thumbup:
Sent from my Transformer TF101G using xda app-developers app
Click to expand...
Click to collapse
If I select recovery after reboot, it will get stuck at Booting recovery kernel image. So any ideas what to do next ?
Edit: That's what is visible on my tab from QtADB
OK I've tried everything I could find but nothing
Computer recognizes it fine when it's cold booting and as you can see, ADB works on it but can't get fastboot to work. I guess the solution would be to get a working recovery on it again, but I can't figure out how without fastboot.

http://forum.xda-developers.com/showthread.php?t=1671598
Don't use ROM manager.
Get adb access and use it to run that command you quoted, then reboot, run the command again, and run adb push recoveryblob /sdcard/ then dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 to restore a working recovery. Then from there mount and reflash.

Thing O Doom said:
http://forum.xda-developers.com/showthread.php?t=1671598
Don't use ROM manager.
Get adb access and use it to run that command you quoted, then reboot, run the command again, and run adb push recoveryblob /sdcard/ then dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 to restore a working recovery. Then from there mount and reflash.
Click to expand...
Click to collapse
OK, tried it but I couldn't complete it.
The first part works ok and after reboot I see the blue line filling up and after that the usual EeePad screen and it boots to EOS loading screen and I can get ADB access again.
But after I have to write "adb push recoveryblob /sdcard/" CMD says
Daemon not running starting it nor on port 5038
Daemon started successfully
And after that it just doesn't do a thing and then it reboots and I can't enter the final code. And under directory tree the sdcard is not a folder but it's just a file or smthing like that "sdcard -> /storage/emulated/legacy" is written.
EDIT:
Man, I would kiss you if I could ! Worked, finally it worked !
So the problem was, that it couldn't find sdcard and so it rebooted. Changed the sdcard to another directory, /dev in my case and after that it completed it and booted perfectly into recovery. AWESOME !

[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?

Stuck in Boot Loop

Strange thing here....
Upgraded my tf300t to katkiss 6.0.
Worked great for about a month. Then it started doing screwy things, random restarts, etc.
Shutdown to boot into TWRP and reflash the ROM and now it is stuck in a boot loop.
If I try to boot into TWRP it still loops.....Any suggestions or hope here....probably something I just haven't had time to figure out or find yet.
Thanks

hurdlesemo said:
Strange thing here....
Upgraded my tf300t to katkiss 6.0.
Worked great for about a month. Then it started doing screwy things, random restarts, etc.
Shutdown to boot into TWRP and reflash the ROM and now it is stuck in a boot loop.
If I try to boot into TWRP it still loops.....Any suggestions or hope here....probably something I just haven't had time to figure out or find yet.
Thanks
Click to expand...
Click to collapse
I had simmilar issue, this helped:
Tools that you need:
ADB & Fastboot:
TF300t Drivers
Command lines
adb shell
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
TWRP (Use this line to fix TWRP):
adb reboot recovery
turn off and on again

Ok it has been a while, but here is the issue....
Start tablet in fastboot
When I plug the USB cable into the computer the green square that flashes around the RCK will stall for a moment as if it is trying to recognize something. However the tablet is not recognized by the computer anywhere in device manager.
I had some success on a machine once or twice with it being recognized in Windows 10, but then it would only be recognized intermittently. I attempted to connect it to another machine on Win 10, Vista and 7, but it is till not being recognized. Help...???

hurdlesemo said:
However the tablet is not recognized by the computer anywhere in device manager.
I had some success on a machine once or twice with it being recognized in Windows 10, but then it would only be recognized intermittently. I attempted to connect it to another machine on Win 10, Vista and 7, but it is till not being recognized. Help...???
Click to expand...
Click to collapse
If not already done, please install "Minimal ADB and Fastboot" on your machine. Since you have startet it "C:\Programm Files (x86)\ Minimal ADB and Fastboot" appears. Then write adb devices and push enter. Your device should appear as serial number.
After that you may use the advised commands in the 2. post.

ebonit said:
If not already done, please install "Minimal ADB and Fastboot" on your machine. Since you have startet it "C:\Programm Files (x86)\ Minimal ADB and Fastboot" appears. Then write adb devices and push enter. Your device should appear as serial number.
After that you may use the advised commands in the 2. post.
Click to expand...
Click to collapse
Installing ADB Minimal fastboot has nothing to do with whether or not the computer is recognizing the tablet at all. But just an FYI ADB Minimal fastboot is installed on the computer....

try this with adb command "adb shell recovery --wipe_data"

Help needed to unbricked my G2 D800

Hi, I tried to install the OTA lollipop update with USB debug mode, the process did not go thru and the phone rebooted into recovery (teamwin). I did restore my backup with recovery successfully, but every time I rebooted from recovery, it went directly to the recovery again. I could power off my phone from recover, but when I power it on, it goes directly to recovery. I tried power phone off, hold volume up key, plug in USB cable, it does not enter download mode, instead it goes into recovery mode again.
It seems that I do have ADB access, but the devices shows in "recovery" mode and I can't switch to "adb shell"
C:\Users\adb_fastboot>adb devices
List of devices attached
09cb97618d0ae1c6 recovery
Please help!

I searched some old post and did the following to unbrick my phone.
In TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
I had "no space left" type of errors reported after both commands. However after reboot, my phone boots up to normal system! Yeah!

By the way, can someone share a lollipop recovery backup file, so we can just load from recovery? I don't have the courage to go thru that USB debug session once more. Thanks!