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?
Hi all !
Two weeks ago I somehow lost my recovery...
I had CWM 6.0.2.1 and decided to flash compatible TWRP zip 2.6.3.0 and switch recovery. I think i forgot to wipe something. It did flash it, but not successfully. When I tried to enter the recovery it stucked in "searching RCK" and didn't enter the costume recovery. I rebooted it and it get stucked on the ASUS screen. So now I have 2 options:
(The tablet is off)
1. Turning on- holding POWER- stucked on ASUS boot screen.
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing- I have two options:
2b.a. cold boot - boots normally to the ROM (CM10)
2b.a. wipe data - haven't tried it, but i belive it will wipe my data XD
I've tried PERI and 1ClickTransformerRoot - no results...
In my opinion, the main problem is that the tablet can't reboot normally...
I need your help, I'll apritiate it a lot !
Sent from my SL101 using xda app-developers app
Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
frederuco said:
Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.
sidneyk said:
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.
Click to expand...
Click to collapse
Thanks a lot ! It now boots normally !
frederuco said:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I've tried it before and now - didn't worked for me...
Can I try a similar method with CWM ? :fingers-crossed:
Btw. you two are great !
You can do the same with a CWM blob file.
Also, if you have a TF101 (non 3G) you can boot to APX and install using NVFlash (EasyFlasher).
See here for details on how to use EasyFlasher: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Yeah, we know!
DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Should understatements really be allowed? :laugh:
@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?
FIXED
Goggle81 said:
@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?
Click to expand...
Click to collapse
I did what frederuco suggested, just with CWM:
http://forum.xda-developers.com/showthread.php?t=1855686&highlight=cwm
frederuco said:
Download the CWM you want to use.
Unzip so you have the CWM.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/CWM.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
And my slider booted normally :victory:
Good luck mate ! I hope it will work for you :fingers-crossed:
Didn't work for me. Will check it again.
Thanks mate!
Edit: sadly I didn't find the time to do it until know.
Thanks at all! Got recovery back. Now I will flash 4.4.2
I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty
Mirabeau78 said:
I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty
Click to expand...
Click to collapse
Have you tried cold boot?
Read through the OP in order to cold boot into ROM:
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
Click to expand...
Click to collapse
If it worked, download Android Terminal Emulator and type in:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots.
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ su
# dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
# reboot
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery and install KatKiss :highfive:
Big TNX to @frederuco and @sidneyk , if it woks thank them before you thank me, it is their instructions above
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
in my case
2a. it does enter recovery cwm, but cant format and it doesnt see the sd card - cant mount it.
2b. press nothing
2b.a cold boot - doesnt boot normally. it stays on the asus logo page and the bubbles rotates
therefore i dont know where could i install that terminal
is my situation helpless? (
Mirabeau78 said:
is my situation helpless? (
Click to expand...
Click to collapse
While in recovery, are you able to connect to a PC and get adb access from a CMD prompt if in Windows or a terminal if in linux?
Sent from my SM-N900T using XDA Premium HD app
i have windows and i tried using 1click and it cant find the device. old adb base or something even if is completly updated
I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!
Jeretista said:
I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!
Click to expand...
Click to collapse
Rommanager = not good for Asus tf101. Also, you don't need any app for installing twrp. If you have a working, up to date recovery, you should be able to flash the twrp zip directly from recovery. I recommend my builds of twrp, of course.
Sent from my Transformer TF101 using XDA Premium HD app
NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.
Jeretista said:
NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.
Click to expand...
Click to collapse
Congratulations. Way to stick with it!
I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?
tjk639 said:
I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?
Click to expand...
Click to collapse
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.
cmendonc2 said:
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.
Click to expand...
Click to collapse
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.
tjk639 said:
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.
Click to expand...
Click to collapse
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"
cmendonc2 said:
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"
Click to expand...
Click to collapse
Where do I find "fastboot devices"?
tjk639 said:
Where do I find "fastboot devices"?
Click to expand...
Click to collapse
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.
cmendonc2 said:
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.
Click to expand...
Click to collapse
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.
tjk639 said:
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.
Click to expand...
Click to collapse
hmm idk. Im guessing you flashed the wrong version of TWRP, which has ended up in a brick for most users, but they had fastboot access and could later recover it using this: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. You dont seem to have either ADB or fastboot, and TWRP is in a non working state. You could try reinstalling your fastboot and ADB drivers with the universal naked drivers, and then retrying ADB reboot bootloader and fastboot.
All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.
tjk639 said:
All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.
Click to expand...
Click to collapse
No problem, glad I could help!
Hey guys this is my first thread, I hope it's in the right section
Here's my problem:
Yesterday my Moto G 2013 with CM12.1 just froze (I could turn the screen on and off but that was it)
I tried opening the reboot menu, which worked, but it got stuck on "rebooting", so I just holded the power key until it turned off.
After that I got to the boot logo, but nothing happened from there, not even the boot animation showing up.
Next I tried to boot into TWRP, but it only got to the TWRP boot logo and nothing happened after that, so I flashed CWM, which I could access, but when trying to flash something it just doesn't progress. When I press "reboot to bootloader" on CWM it just freezes there aswell.
In another thread I read that flashing the gpt.bin should fix everything but it didn't help.
I don't really want to perform a factory reset, because of the data loss, but I think this would be my only option.
My question is:
How can I fix my phone (preferably without a factory reset), for example by getting TWRP to work again, because I have a Backup of my system and a zip of CM12.1 on it?
Btw another thing to mention is that when being in Recovery/System USB doesn't really work, but if my phone is turned off or in bootloader it works just fine.
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
_that said:
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
Click to expand...
Click to collapse
When I try "fastboot boot twrp.img" it reboots and get's stuck at the boot logo of android (Motorola logo) and I can hear the "Device disconnected" sound of windows.
But I flashed TWRP into recovery and it get's to the curtain screen. But it doesn't recognize my phone which might have to do with that as soon as it boots into a system USB just won't work
The following command will get TWRP working: fastboot erase userdata
lost101 said:
The following command will get TWRP working: fastboot erase userdata
Click to expand...
Click to collapse
But this will delete everything like my pictures folder, right? Isn't there a way to backup these files ?
@Ju43
adb pull /sdcard/ c:/motog_backup/
lost101 said:
@Ju43
adb pull /sdcard/ c:/motog_backup/
Click to expand...
Click to collapse
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Ju43 said:
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Click to expand...
Click to collapse
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
lost101 said:
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
Click to expand...
Click to collapse
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Ju43 said:
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Click to expand...
Click to collapse
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot
lost101 said:
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
I see what you mean but I got adb to work most times when android was still working (just not in recovery) but I also had problems with charging when the phone was turned on, so I assume it's a problem with android, but I'll search for a Ubuntu Live CD that should be layng around somewhere here (lol) and I'll try it
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Ju43 said:
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Click to expand...
Click to collapse
Use: sudo fastboot devices
lost101 said:
Use: sudo fastboot devices
Click to expand...
Click to collapse
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Ju43 said:
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Click to expand...
Click to collapse
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
lost101 said:
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
Click to expand...
Click to collapse
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Ju43 said:
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Click to expand...
Click to collapse
Try CWM.
lost101 said:
Try CWM.
Click to expand...
Click to collapse
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Ju43 said:
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Click to expand...
Click to collapse
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
lost101 said:
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
Click to expand...
Click to collapse
Downloading it right now, could you please exactly tell me what to flash with which command ?
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?