Hey guy's I haven't had time to pick up and fix my transformer since the whole recovery flashing issue I've finally come back to it but none of the guides to get the new recovery to stick work I've tried a few different methods I can cold-boot Linux and boot into android and drop back into recovery but I can't get anything to stick.
If I run this command: adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
All i get is a message saying no space left on device even thought I got 12GB left on the internal storage.
and I also tried this command: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
But I get a syntax error in adb saying that dd is not a recognized command.
Am I missing something big here as it's really annoying I can't even use my tablet properly.
Thanks in advance!
Bump
I really need help on this does no one know?!
APX is your best option to flash a new recovery
Sent from my Galaxy Nexus using Tapatalk 2
Related
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
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 !
Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!
nicklefloss said:
Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!
Click to expand...
Click to collapse
From the TWRP terminal command type
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
then hit enter and reboot.
jsho31 said:
From the TWRP terminal command type
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
then hit enter and reboot.
Click to expand...
Click to collapse
Thanks but that doesnt work because my phone doesnt register on ubuntu
nicklefloss said:
Thanks but that doesnt work because my phone doesnt register on ubuntu
Click to expand...
Click to collapse
you use the terminal command via TWRP, not your lcomputer
Here's my problem. I think its not related to any particular ROM, but I'm in need of some help. I tried upgrading from Katkiss Lollipop v10 to v11 of this ROM. Have the latest TWRP 2.8.1.1. Clean wiped everything including formatting data and installed v11 + Gapps. Wiped Cache and Dalvik before rebooting to the new OS. Strangely, the tablet restarts, and goes to the EEE Pad screen and stays there for hours. No matter how many times I flash any ROM in recovery, it doesn't go past the EEE Pad screen.
Googled the issue and a gentleman from this forum had suggested to run this command which resolved the issue for him.
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
Since I don't have a USB cable to connect my TF to my desktop, I actually ran the following commands from the TWRP Advanced menu. The commands ran successfully, but didn't help with booting into Android
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Any ideas from anyone on how to fix this ?
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