I was stuck in a Clockworkmod Recovery Bootloop after an otherwsie successful install of CM11. Had everything all set up the way I like it, and bam, I tried to power down but could not, it just went to clockwork recovery, screen on. So I searched for solutions and sadly, tried this in the terminal:
"echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0"
Now the phone appears to be hard bricked. :crying: Cannot hold volume up, down, or both in combo with power switch, and, there is no orange led indicator when the power is plugged in. Any help would be deeply appreciated.
Thanks! AB
brockmanah said:
I was stuck in a Clockworkmod Recovery Bootloop after an otherwsie successful install of CM11. Had everything all set up the way I like it, and bam, I tried to power down but could not, it just went to clockwork recovery, screen on. So I searched for solutions and sadly, tried this in the terminal:
"echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0"
Now the phone appears to be hard bricked. :crying: Cannot hold volume up, down, or both in combo with power switch, and, there is no orange led indicator when the power is plugged in. Any help would be deeply appreciated.
Thanks! AB
Click to expand...
Click to collapse
What on earth did you do that for?
When you plug the phone in does device manager indicate anything has been plugged in?
Yes "My HTC" shows up as an Android item
brockmanah said:
Yes "My HTC" shows up as an Android item
Click to expand...
Click to collapse
And it doesn't respond to adb devices or fastboot devices?
dottat said:
And it doesn't respond to adb devices or fastboot devices?
Click to expand...
Click to collapse
No, there's no reply.
brockmanah said:
No, there's no reply.
Click to expand...
Click to collapse
Have access to a Linux machine?
dottat said:
Have access to a Linux machine?
Click to expand...
Click to collapse
'fraid not. I suppose I can look into installing it on a partition if absolutely required.
dottat said:
Have access to a Linux machine?
Click to expand...
Click to collapse
I stand corrected on fastboot devices. It does return the following:
UEUUUEWUUU§UUUU fastboot
brockmanah said:
I stand corrected on fastboot devices. It does return the following:
UEUUUEWUUU§UUUU fastboot
Click to expand...
Click to collapse
What happens if you type
Fastboot reboot-bootloader
?
dottat said:
What happens if you type
Fastboot reboot-bootloader
?
Click to expand...
Click to collapse
It shuts down and I have to hard reset to get it to show up in the device manager. But that does seem to indicate that fastboot is working. Would something like :
fastboot -c "echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0"
with the 1 and zero replaced with the right variables work? (Confessing that I don't know what the right variables are).
brockmanah said:
It shuts down and I have to hard reset to get it to show up in the device manager. But that does seem to indicate that fastboot is working. Would something like :
fastboot -c "echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0"
with the 1 and zero replaced with the right variables work? (Confessing that I don't know what the right variables are).
Click to expand...
Click to collapse
No. What happens if you try to fastboot flash zip nameofruu.zip
dottat said:
No. What happens if you try to fastboot flash zip nameofruu.zip
Click to expand...
Click to collapse
Having trouble finding the filename of my RUU to try it... I presume i need to get the filename of the latest clockwork mod?
brockmanah said:
Having trouble finding the filename of my RUU to try it... I presume i need to get the filename of the latest clockwork mod?
Click to expand...
Click to collapse
No. Download an ruu and put that in your fastboot directory.
dottat said:
No. Download an ruu and put that in your fastboot directory.
Click to expand...
Click to collapse
Seems to fail, says batt level is set wrong:
C:\Users\Adam\AppData\Local\Android\sdk\platform-tools>fastboot flash zip cm-11-
20150101-NIGHTLY-m8.zip
target reported max download size of 1834942464 bytes
sending 'zip' (239956 KB)...
OKAY [ 7.645s]
writing 'zip'...
(bootloader) radio_batt_level: NOT IMPLEMENTED!
FAILED (remote: not allowed)
finished. total time: 7.659s
brockmanah said:
Seems to fail, says batt level is set wrong:
C:\Users\Adam\AppData\Local\Android\sdk\platform-tools>fastboot flash zip cm-11-
20150101-NIGHTLY-m8.zip
target reported max download size of 1834942464 bytes
sending 'zip' (239956 KB)...
OKAY [ 7.645s]
writing 'zip'...
(bootloader) radio_batt_level: NOT IMPLEMENTED!
FAILED (remote: not allowed)
finished. total time: 7.659s
Click to expand...
Click to collapse
You can't flash a Rom like that. Can you install teamviewer quick and pm me the id and passcode. I think you wrecked your board info partition.
dottat said:
You can't flash a Rom like that. Can you install teamviewer quick and pm me the id and passcode. I think you wrecked your board info partition.
Click to expand...
Click to collapse
I'm from Vietnam. And i have the same problem! Can you help me to fix it by Team View! If you can help me, give me a dating.....i really thank you!
Rockernam2 said:
I'm from Vietnam. And i have the same problem! Can you help me to fix it by Team View! If you can help me, give me a dating.....i really thank you!
Click to expand...
Click to collapse
Did you already try flashing the RUU?
dottat said:
Did you already try flashing the RUU?
Click to expand...
Click to collapse
My phone now can't turn-on. When i connected it to PC and flash RUU.zip by ADB, message on ADB: radio_batt_level: Not inplemented.
And when i flash by RUU.exe, it's not see my device, although when connect PC, i see Android usb device (My HTC) in Computer Magagement
Can you help me.
Rockernam2 said:
My phone now can't turn-on. When i connected it to PC and flash RUU.zip by ADB, message on ADB: radio_batt_level: Not inplemented.
And when i flash by RUU.exe, it's not see my device, although when connect PC, i see Android usb device (My HTC) in Computer Magagement
Can you help me.
Click to expand...
Click to collapse
When you run the command
Fastboot devices
Do you get the serial number as a response?
Sent from my XT1575 using Tapatalk
dottat said:
When you run the command
Fastboot devices
Do you get the serial number as a response?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Before flash RUU, I was try to do it, but nothing response !!!
Related
NB/EDIT : I am pretty sure this is due to cmupdater requiring "next boot" to recovery. Is there any way to get through this?
NB/ EDIT : Now, I can cold boot. But the flash (DD/ fastboot seems not be working. hope better news next hours).
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...
http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
florck said:
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...
Click to expand...
Click to collapse
Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
elfaure said:
http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
Click to expand...
Click to collapse
florck said:
Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
Click to expand...
Click to collapse
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com
elfaure said:
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com
Click to expand...
Click to collapse
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...
florck said:
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...
Click to expand...
Click to collapse
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.
_that said:
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.
Click to expand...
Click to collapse
Unfortunately, i don't have twrp... I can't see the solution here... :crying:
florck said:
Unfortunately, i don't have twrp... I can't see the solution here... :crying:
Click to expand...
Click to collapse
Why doesn't adb work? Can you see any USB device on your computer?
_that said:
Why doesn't adb work? Can you see any USB device on your computer?
Click to expand...
Click to collapse
Oh ! I got and ADB shell.
but when I "ls /dev/block", I only get
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p3
platform
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?
florck said:
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?
Click to expand...
Click to collapse
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment bootit.zip
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.
_that said:
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment 1985914
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.
Click to expand...
Click to collapse
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?
florck said:
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?
Click to expand...
Click to collapse
The funny serial number is normal for the recovery.
Try the procedure again and hold down volume-left immediately after pressing "Enter" in adb shell on the insmod command. Maybe you can get to the bootloader menu. If not, I'll try to build another kernel module.
That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.
florck said:
That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.
Click to expand...
Click to collapse
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment bootit-bootloader.zip
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.
_that said:
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment 1985941
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.
Click to expand...
Click to collapse
You're a genius, I can now fastboot and / or cold boot. When I cold boot I have my fully functional previous android. But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?
florck said:
You're a genius, I can now fastboot and / or cold boot.
Click to expand...
Click to collapse
That's good news - until today your situation was considered an unrecoverable hard brick.
florck said:
But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?
Click to expand...
Click to collapse
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...
florck said:
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...
Click to expand...
Click to collapse
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461
_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
_that said:
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461
Click to expand...
Click to collapse
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...
florck said:
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...
Click to expand...
Click to collapse
Any other idea ? Something to flash in other blocks?
I am fairly new at all of this and am reaching out to the experts out there.
I have an Asus TF700T Infinity. It is unlocked and has TWRP recovery installed. The tablet keeps booting into the TWRP recovery. See this thread:
http://forum.xda-developers.com/showthread.php?t=2311162
Thank You "_that" for the help getting me to this point.
Come to find out, somehow during the modding process I accidentally installed the TF201 boot-loader on my TF700 tablet. I have ADB and Fast-boot installed on my Windows 8 computer, but I'm not really sure how to use it.
Right now, the only way for me to boot into the boot-loader is by going into the "terminal command" in TWRP and using this command:
"insmod /external_sdcard/bootit.ko". (I have this on my ext.sdcard) There I can see the 4 icons of the boot-loader.
I have tried installing multiple roms using the TWRP, it shows a successful install, but when rebooting, the tablet goes back to the TWRP recovery.
Can anyone out there help me get this tablet back to the TF700 boot-loader? Is it even possible? I am in desperate straits here. Please help.
cnh56 said:
Come to find out, somehow during the modding process I accidentally installed the TF201 boot-loader on my TF700 tablet. I have ADB and Fast-boot installed on my Windows 8 computer, but I'm not really sure how to use it.
Click to expand...
Click to collapse
ADB should be able to communicate with TWRP, and fastboot should be able to communicate with the bootloader.
cnh56 said:
Right now, the only way for me to boot into recovery is by going into the "terminal command" in TWRP and using this command:
"insmod /external_sdcard/bootit.ko". (I have this on my ext.sdcard) There I can see the 4 icons of the recovery.
Click to expand...
Click to collapse
TWRP is the recovery. The thing with the 4 icons is the *bootloader*. Should be obvious by reading the text near the top of the screen.
cnh56 said:
I have tried installing multiple roms using the TWRP, it shows a successful install, but when rebooting, the tablet goes back to the TWRP recovery.
Click to expand...
Click to collapse
I have a new theory about why this happens: partition tables mismatch. In other words: The location where the recovery writes the blob is not the same as where the bootloader expects it. Thus the bootloader ignores your blob.
Since the fastboot protocol is handled by the bootloader, you might be able to reflash the bootloader using fastboot:
* obtain the correct bootloader (10.6.1.14.x) for the TF700 in blob format - download the correct file from http://forum.xda-developers.com/showthread.php?t=2223492
* unpack the "blob" file that's inside
* connect your TF700, put it into fastboot mode (choose USB from the bootloader menu)
* on your computer, run "fastboot -i 0x0b05 flash bootloader blob" (easiest way to do this is to put the blob file in the same location where your fastboot.exe is, and run the command in that directory too)
Checked to see if it was seeing my device.
C:\android-adb>fastboot devices
015d2a5087240a0b fastboot
Question? - What is this number? - 015d2a5087240a0b
I did a complete wipe in TWRP and then ran the command in fastboot
This is what I did from command prompt:
C:\android-adb>fastboot -i 0x0b05 flash bootloader blob
sending 'bootloader' (9574 KB)...
OKAY [ 3.034s]
writing 'bootloader'...
OKAY [ 1.400s]
finished. total time: 4.437s
C:\android-adb>
***********************************************************************************************************************************
What should I do next? When I rebooted, it went back to TWRP.
cnh56 said:
Checked to see if it was seeing my device.
C:\android-adb>fastboot devices
015d2a5087240a0b fastboot
Question? - What is this number? - 015d2a5087240a0b
Click to expand...
Click to collapse
I believe that's the serial number of your Tegra 3 chip.
cnh56 said:
C:\android-adb>fastboot -i 0x0b05 flash bootloader blob
sending 'bootloader' (9574 KB)...
OKAY [ 3.034s]
writing 'bootloader'...
OKAY [ 1.400s]
finished. total time: 4.437s
Click to expand...
Click to collapse
Looks good so far. At least the communication with the PC appears to work.
cnh56 said:
When I rebooted, it went back to TWRP.
Click to expand...
Click to collapse
I assume if you had seen the blue progress bar on the bootloader screen and a quite long (almost 1 minute) delay, you'd have reported that. If you use the insmod bootit.ko command to activate the bootloader, does it now have a different version number?
_that said:
I believe that's the serial number of your Tegra 3 chip.
Looks good so far. At least the communication with the PC appears to work.
I assume if you had seen the blue progress bar on the bootloader screen and a quite long (almost 1 minute) delay, you'd have reported that. If you use the insmod bootit.ko command to activate the bootloader, does it now have a different version number?
Click to expand...
Click to collapse
It look to be the same.
"Android Cardhu-user bootloader <1.00 e>
Released by "Us_epad-10.4.2.15-20120917 A03"
Do you still know what file you flashed to get the TF201 bootloader on your TF700?
_that said:
Do you still know what file you flashed to get the TF201 bootloader on your TF700?
Click to expand...
Click to collapse
I'm really not sure, but I think it might be this one, It was on my external sd card:
Upgrade Hairybean 4.2.1 Bootloader & Recovery
Update: I checked my history in my browser and I pretty sure it was the above file.
@that: Could this method to push a stock blob file solve this problem?
http://forum.xda-developers.com/showthread.php?t=1803343
The instructions are for the ICS rom, but I know of two people who successfully used it with 4.2.1 when the only part of their tablet they could access was TWRP.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
@that: Could this method to push a stock blob file solve this problem?
http://forum.xda-developers.com/showthread.php?t=1803343
The instructions are for the ICS rom, but I know of two people who successfully used it with 4.2.1 when the only part of their tablet they could access was TWRP.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Tried executing this command in adb from the above thread:
This is what I got. Not very familiar with ADB commands.
C:\android-adb>su dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\android-adb>
cnh56 said:
Tried executing this command in adb from the above thread:
This is what I got. Not very familiar with ADB commands.
C:\android-adb>su dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\android-adb>
Click to expand...
Click to collapse
You need to be rooted to run that command. su=superuser.
elfaure said:
You need to be rooted to run that command. su=superuser.
Click to expand...
Click to collapse
doesn't matter, it won't work anyway.
I compiled this a while ago after seeing someone in the Q&A section ask about if it was available for the desire. I only had a few minutes to test that it boots back when I compiled it, and I forgot what works and what doesnt. Therefore this is a complete beta test. Do not use this if you dont know what you are doing. In its current state its for advanced users only. Install using fastboot:
Code:
fastboot flash recovery philztouch.img
If you just want to temporarily test it (without fully installing) you can run this:
Code:
fastboot boot philztouch.img
That'll boot the image and let you play around with the recovery, but once you reboot it will be gone and you will have your old recovery back. (good for testing purposes)
Feedback is appreciated. Thanks
Credits for the development of this recovery go to Phil3759. For more info read here.
Once some testers confirm that it works decently, I will make the OP look pretty and more n00b friendly.
Seems no SD card tools??
How likely will this brick?
smsmasters said:
How likely will this brick?
Click to expand...
Click to collapse
Its almost impossible that this will brick your phone (unless you are flashing it on a phone other than the desire)
If you just want to test without permanently installing, use the fastboot boot command described in the OP.
enix2k said:
Seems no SD card tools??
Click to expand...
Click to collapse
Yes, you seem to be correct. I cant find any of that stuff.
Chromium said:
Its almost impossible that this will brick your phone (unless you are flashing it on a phone other than the desire)
If you just want to test without permanently installing, use the fastboot boot command described in the OP.
Click to expand...
Click to collapse
Any chance for a flashable ZIP?
Can't get fastboot to work right now.
smsmasters said:
Any chance for a flashable ZIP?
Can't get fastboot to work right now.
Click to expand...
Click to collapse
Yeah Ill make it tomorrow when I have time, too busy atm,
No problem mate, no rush. I'll test this out for you.
Chromium said:
Yes, you seem to be correct. I cant find any of that stuff.
Click to expand...
Click to collapse
What sdcard tools r u trying to find? U mean mount usb?
smsmasters said:
Any chance for a flashable ZIP?
Can't get fastboot to work right now.
Click to expand...
Click to collapse
Attached below.
jmcclue said:
What sdcard tools r u trying to find? U mean mount usb?
Click to expand...
Click to collapse
No, Im talking about sdcard partitioning stuff. Do you know if thats normally available in this recovery?
Chromium said:
Attached below.
No, Im talking about sdcard partitioning stuff. Do you know if thats normally available in this recovery?
Click to expand...
Click to collapse
On my S4 Mini and LG G Pad 8.3 with Philz Touch Recovery there is an option under "Advanced Menu" to Partition the sdcard with a selectable ext size, etc...
Chromium said:
Attached below.
No, Im talking about sdcard partitioning stuff. Do you know if thats normally available in this recovery?
Click to expand...
Click to collapse
Il check my desire s... They pretty much the same phone.
Edit: yh the desire s doesnt have partitioning tools. But to be honest, phils recovery is based on CWM its just got a [email protected] load of extra features. And we all know not to partition sdcard with cwm so no real loss if u ask me.
jmcclue said:
Il check my desire s... They pretty much the same phone.
Edit: yh the desire s doesnt have partitioning tools. But to be honest, phils recovery is based on CWM its just got a [email protected] load of extra features. And we all know not to partition sdcard with cwm so no real loss if u ask me.
Click to expand...
Click to collapse
Yes, thats true.
So to the people that tested the recovery so far, any issues or feedback?
I flashed ZIP file and the device is stuck in a boot loop
And tried fastboot, ended up in this error:
sending 'recovery' (4996 KB)... OKAY [ 0.801s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.807s
Fast solution please! No recovery now!!
pc boy said:
I flashed ZIP file and the device is stuck in a boot loop
Click to expand...
Click to collapse
Strange, did anyone else have problems with the zip?
Use fastboot instead to flash the image.
pc boy said:
I flashed ZIP file and the device is stuck in a boot loop
And tried fastboot, ended up in this error:
sending 'recovery' (4996 KB)... OKAY [ 0.801s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.807s
Fast solution please! No recovery now!!
Click to expand...
Click to collapse
what did u type in the command? that error is because like if u type "fastboot flash boot recovery.img" get what i mean? (did it last night lol )
correct command is
fastboot flash recovery recovery.img
God I know the fsatboot commands!!
Now I can't even flash the 4EXT recovery back!!!
The same error
Help PLZ!!
pc boy said:
God I know the fsatboot commands!!
Now I can't even flash the 4EXT recovery back!!!
The same error
Help PLZ!!
Click to expand...
Click to collapse
Both "fastboot flash recovery recovery.img" and "fastboot boot recovery.img" are not working? They give the same error?
pc boy said:
God I know the fsatboot commands!!
Now I can't even flash the 4EXT recovery back!!!
The same error
Help PLZ!!
Click to expand...
Click to collapse
yh so do i but i made a mistake last night, it happens. post here what ur typing in the command window.
Chromium said:
Both "fastboot flash recovery recovery.img" and "fastboot boot recovery.img" are not working? They give the same error?
Click to expand...
Click to collapse
flashing does not work but I can boot using the second command!
Now what to do?!
jmcclue said:
yh so do i but i made a mistake last night, it happens. post here what ur typing in the command window.
Click to expand...
Click to collapse
Copy paste:
Fastboot flash recovery recovery.img
renamed the file to recovery.img
Hi,
I've posted on this topic on transformerforums website but have not had any success (despite valiant attempts from the guys on the forums).
I am unable to post the link here, please PM me for a link to my original post.
Basically my TF700T got stuck in a bootloop. I have unlocked the bootloader but have not flashed it so it's on stock ROM. I have not been able to flash a recovery ROM and am at a dead end as to what to do.
I am able to get to bootloader and I when I run
Code:
fastboot devices
I get the following output
Code:
015d2a506733f618 fastboot
Which all seems correct. I have access to the tablet when connected to my pc.
When I try to flash the recovery rom, it takes a very short amount of time and on my tablet the device hangs (i.e the RCK icon is no longer flashing). I have checked the blob, it is the correct one and the MD5 hash is correct.
Code:
C:\androidsdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp-2.7.1.1-tf700t.blob
sending 'recovery' (6894 KB)...
OKAY [ 0.868s]
writing 'recovery'...
OKAY [ 0.089s]
finished. total time: 0.958s
I can get back into the bootloader if I restart again but attempting to flash it results in a hang.
I have tried to insert an sd with the stock ROM and boot in RCK mode but this has not worked either.
Has anyone any suggestions as to what to do?
The tablet is 2 years old now so not under warranty.
thanks in advance.
anyone have any suggestions?
I'm going on holidays on Thursday and would really love to get this resolved before I go.
deleted
Shameless bump .... are my only options to return this to the manufacturer?
Anyone any suggestions, do you need more info from me?
What you did looks correct, only the short time for "writing" looks suspicious. Try the fastboot command again, but replace "recovery" with "staging", maybe that works better. At the next reboot you should see a blue progress bar on the boot screen for a few seconds and it should reboot again.
Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?
I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?
knoxor said:
I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?
Click to expand...
Click to collapse
When blobs are written to the staging partition, on next boot. the bootloader flashes the contents to the relevant partitions (i.e., kernel, system, bootloader)
knoxor said:
Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?
Click to expand...
Click to collapse
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul
knoxor said:
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul
Click to expand...
Click to collapse
Well shoot me a PM, Lets see if we can find a solution to your issue ...
Thx Josh
bump again.
Is there anyone there who can help me on this please ?
knoxor said:
Is there anyone there who can help me on this please ?
Click to expand...
Click to collapse
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.
_that said:
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.
Click to expand...
Click to collapse
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks
knoxor said:
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks
Click to expand...
Click to collapse
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....
berndblb said:
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....
Click to expand...
Click to collapse
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??
knoxor said:
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??
Click to expand...
Click to collapse
If you got the charger from anywhere else but Asus - yes, that could be the issue. And the only one left I can think of....
Hello,
My honor 8 is hard bricked, yesterday I wished to install custom Rom and it was encrypted so I decided to return to EMUI, I installed stock recovery I installed rollback package to emui 4.1 and emui 4.1 now i'm stuck on boot screen. I already do a format data and wipe cache but nothing.
Please help me.
EDIT : I can go to ADB but I have this message when I try to flash anything... "FAILED (remote: Command not allowed)" FRP is locked
Please help me I'm so bored about this problem
There are some guides on how to unbrick phone with FRP locked... You could try to watch on them.
That's mine guide
ScardracS said:
There are some guides on how to unbrick phone with FRP locked... You could try to watch on them.
That's mine guide
Click to expand...
Click to collapse
The problem is when i use ADB command it wrongs me
"target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.894s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.903s"
If you can't find any solution with ADB, as a last resort you could use DC Phoenix to fix it. But it costs 15 Euros to use it. That's what I had to do fix the same problem you have.
BnK1986 said:
The problem is when i use ADB command it wrongs me
"target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.894s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.903s"
Click to expand...
Click to collapse
Go with dload method. Try downloading the full firmware for your model and use the 3 combination to flash. There is quick guide in my signature if you are not aware of the exact method for dload.
shashank1320 said:
Go with dload method. Try downloading the full firmware for your model and use the 3 combination to flash. There is quick guide in my signature if you are not aware of the exact method for dload.
Click to expand...
Click to collapse
I can't do dload method it shows me boot screen.
BnK1986 said:
I can't do dload method it shows me boot screen.
Click to expand...
Click to collapse
You may not be doing it right. Assuming.
Keep trying couple of times, remember to press power up+powet down 1st and then power key and keep pressing all together
shashank1320 said:
You may not be doing it right. Assuming.
Keep trying couple of times, remember to press power up+powet down 1st and then power key and keep pressing all together
Click to expand...
Click to collapse
Yes I know i was doing this before and it worked but now it's not possible I will try several times like 5-10 times in a row
BnK1986 said:
Yes I know i was doing this before and it worked but now it's not possible I will try several times like 5-10 times in a row
Click to expand...
Click to collapse
are you able to get into fastboot or recovery?
shashank1320 said:
are you able to get into fastboot or recovery?
Click to expand...
Click to collapse
No I hold the 3 buttons it shows me boot screen, black screen for 1 second and again boot screen
shashank1320 said:
are you able to get into fastboot or recovery?
Click to expand...
Click to collapse
Any solutions?
BnK1986 said:
Any solutions?
Click to expand...
Click to collapse
You can enter in fastboot, by pressing volume down when the phone is powering on and holding the button, immediately insert the usb cable (already plugged in the pc) and you will enter in fastboot.
Video
Sent from my FRD-L09 using XDA Labs
grilla99 said:
You can enter in fastboot, by pressing volume down when the phone is powering on and holding the button, immediately insert the usb cable (already plugged in the pc) and you will enter in fastboot.
Video
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
I can do this but ADB commands not working
BnK1986 said:
I can do this but ADB commands not working
Click to expand...
Click to collapse
When you enter in this shell, you are not allowed to use ADB commands, but only fastboot commands, previously you typed adb devices, now you can't. But if you type fastboot device it will shown you your id number plus device, just try if what i sad is true
Sent from my FRD-L09 using XDA Labs
tnks !!!! friend save _me !!!!!
hey i have the same problem
what did you exactly do in fastboot mode? no commands works on my phone