Related
i have a problem, for some reason i cant go to recovery mode. i have JFv 1.42_RC33... what can i do
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Iceucold said:
Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
That made even less sense.
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
kydcleric said:
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
Click to expand...
Click to collapse
i dont know im new to this stuff but what happens is that the g1 boot screen pops up when i press home+power then it just restarts and shows the g1 boot screen again then it goes to the normal home screen
Iceucold said:
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
i dont know what u mean
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Iceucold said:
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Click to expand...
Click to collapse
nothing happens i put that in there and it just shows a money sign under it.. and when i just put reboot it says
reboot: operation not permitted
You are holding down home first right? I.e. press home and hold it down and then press power(I continue to hold home down all the way up until I see recovery mode starting)
Can you check if the recovery image (/system/recovery.img) is intact?
if you're using the haykuro builds, it is known that reboot won't work from terminal emulator. but you should be able to reboot recovery through adb shell.
I remember I read somewhere that certain bootloaders have a different key sequence for recovery mode, but i've never seem any of them.
ooooo crap i just checked it and there is no recovery.img in there ok what do i do??
someone plz help me out
probably best to dl the one from the Rooting Hacking & Flashing... post. They have a link to the file there. Just dl it and, as su, copy it to the folder they say.
what post???
Cosine said:
what post???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=442480
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Cosine said:
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Click to expand...
Click to collapse
The suggestion was to try restoring the recovery image as outlined in that thread: (though you shouldn't need to do the "telnetd" part)
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse
so should i just try
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
in the terminal emulator
I was reading the threads in the dream forum and found his progress and instructions. I added them to my wiki so they can be continually edited and updated as new methods are found. I did not have any part in this but I noticed that there was not a formal post here about it yet so I decided to make one.
http://android-dls.com/wiki/index.php?title=Magic_Rooting
Please feel free to thank him with some nesquik if you find this helpful!
I was pasting the new instructions here every time they changed but they seem to change often. Please visit the above url to see the current instructions. They were placed on the the wiki so anyone could make edits and changes to them, which is useless if this post needs to be updated each time. I wish vbulletin had some sort of wiki quote that could auto read that page and insert it here for me
Great!
If would be great if this post were a sticky. It also would be nice it the post was updated to include the instructions here as well.
Thanks,
Anders
Just quoting the solution here..
First of all, everyone owes Haykuro a great big thanks for working on this and helping create the solution without even owning a magic. The following is his method just reworded slightly.
1. To gain root access on your HTC Magic/Sapphire you will need to download the magic-root-boot.img zip file and unzip it so that you have boot-new.img in a location you can find.
2. On your device, enter the bootloader by trying one of the following
* Turn off your device and while it is off hold down home while you press power.
* Turn off your device and while it is off hold down volume down while pressing power
3. Make sure your usb cable is inserted and you have Fastboot installed and ready to use.
4. Type the following commands on your desktop (not on the device):
Code:
fastboot boot boot-new.img
5. wait for the following to flash and the phone to reboot:
Code:
downloading 'boot-new.img'... OKAY
Code:
booting... OKAY
6. make sure you have ADB installed and run the following commands from your desktop (not on the device):
Code:
adb push boot-new.img /sdcard/boot-new.img
Code:
adb shell flash_image boot /sdcard/boot-new.img
anyone tried this?
I was going to post the actual text here but the reason for doing it in the wiki is because the methods seem to change very often (the g1 method changed almost daily for a while). I would still recommend viewing the instructions on the wiki before performing the method to be sure they are the same at the time of use.
Full procedure so far!
1. Download boot-new.img.zip from http://www.droiddeveloper.com/hrbuilds/boot-new.img.zip
2. extract boot-new.img to computer.
3. Download recovery-new.img.zip from http://www.droiddeveloper.com/hrbuilds/recovery-new.img.zip
4. extract recovery-new.img to computer.
5. power off device
6. hold BACK+POWER (or VOLUME_DOWN+POWER) to boot into bootloader.
7.
Code:
[b]fastboot boot boot-new.img[/b]
wait for device to boot.
[b]adb push boot-new.img /sdcard/boot-new.img[/b]
[b]adb push recovery-new.img /sdcard/recovery-new.img[/b]
[b]adb shell flash_image boot /sdcard/boot-new.img[/b]
[b]adb shell flash_image recovery /sdcard/recovery-new.img[/b]
[b]adb shell reboot[/b]
you now have root build, and can flash whatever build you like (test keys and all)
First post and wiki updated to show these changes in more detail.
Hi,
I have a french Magic and I test this solution.
I have a problem, when I use the adb shell, I am "root", but when I use a terminal shell on the phone I'm not "root". I use "id" for my test.
How can I do ?
Thanks.
Edit : Ok I found the problem.
I make these commands after in adb shell:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd system
# cd bin
# cat sh > su
# chmod 4755 su
# sync
# reboot
Thanks
n00b here
can we flash ROMs for dream too or need to wait for magic ROMs ?
it's possible to backup the current firmware of my magic (with or without root), before flashing a new one?
thank you for rooting the magic
thank you for your help
ok i have a big problem when i put (fastboot boot boot-new.img) the phone is restarting every time in htc presentation :S
i put the phone in recovery mode ( fastboot usb ), but then i have the same problem, when i put fastboot boot boot-new.bin, the phone restart always with "boot.bin" , no with "boot-new.bin"...
i try to give the complete path, but always the same result
hello i have a problem.
if i write fastboot boot boot-new.img the console says: the comand "fastboot" is incorrect or bla bla ...
i have a german magic.
sr-ha said:
hello i have a problem.
if i write fastboot boot boot-new.img the console says: the comand "fastboot" is incorrect or bla bla ...
i have a german magic.
Click to expand...
Click to collapse
do you have installed de SDK ¿?
hmm no i dont
should i install it the android sdk 1.5 windows ??
i hve downloadet it but i cant find a icon or sth. to install the sdk
nicola_it said:
it's possible to backup the current firmware of my magic (with or without root), before flashing a new one?
thank you for rooting the magic
thank you for your help
Click to expand...
Click to collapse
nandroid backup 2.1, avaible in recovery mode, doesn't works
sr-ha said:
hmm no i dont
should i install it the android sdk 1.5 windows ??
i hve downloadet it but i cant find a icon or sth. to install the sdk
Click to expand...
Click to collapse
unrar de SDK, and in the "tools" directory you have the ADB and FASTBOOT aplications ( use in the console mode )
Works perfectly with XP, not with vista or win7
sorry but i dont understand what schould i do.
with use in thee console
i think i have to install fastboot or open it. but i cant do nothing of both. if i click on the fastboot exe it blobs open and fast close again.
under windows xp all ok
under windows vista no!!!
I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.
xxwckdxx said:
I had a couple problems so i unrooted then rerooted then i kept trying to flash recovery 1.6.2 but it kept comming up with file not found on the sdcard so i put the file in the tools folder and used android commander. It came up with 2 # then the screen went blank and it sat there so after a few minutes i did a battery pull and now i cant boot into recovery. It just sits at the boot screen.
Click to expand...
Click to collapse
how long has it sat there? sometimes you have to give it a few minutes after going thru all that.
By the way if i dont try to boot into recovery it loads fine how can i reload the reocvery?
Probably 5 minutes and no go
How were you loading it in the first place? Have you checked to see if its on your card? When pushing the image, are you using the exact image name, i.e, v1.6.2-(color).img.? Also, are you holding the end-home keys at the same time long enough to see it come up?
when i first was trying i opened the terminal i had on the phone and typed flash_image recovery /sdcard/recovery-1.6.2.img and it kept comming up with bad filename(wwhich i had renamed the file to that so i dont know why) then i put it in the tools folder and tried the same from commander and it got me to here ;\
What method are you using? Try amon ras or the method used to push it to your card thru root.
havent heard of amon ras.....i just pushed it to the sdcard again and tried the same command and end up with the same thing iam trying to unroot again
nope came up with bootloader error for the unroot
tried using kitchen to reroot but it comes up with errors
Okay, these are Amon RAs methods just depending on what your using:
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.imgvia fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Or thru adb try this:
cd C:\android-sdk-windows\tools
adb shell
adb push recovery-RA-heroc-v<name>/sdcard
adb shell reboot
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.
to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it
VoLoDaR1 said:
to tell you the truth 1.6.2 is basically the same as 1.5.2 the only diff is the power off option and the carebear color so if you have 1.5.2 you should just keep it since you are having trouble installing it
Click to expand...
Click to collapse
I had 1.2.3 or whatever it was thats why i was gonna just shoot to 1.6.2 i had done it before but i dont know what happened this time. I tried the way thru adb and it has been sitting so far 10 minutes and it is still sitting at the boot screen
The first one wont work i cant get into recovery.....the second one i get "fastboot is not recognized as a internal command"and the third is the one i have been trying....
im not sure man i had trouble flashing it also try renameing it to something simple like 1.6.2.img and go to better terminal emulator type in su enter than type in the comands to flash it
flash_image /sdcard/1.6.2.img enter
do not enter mount-a before this this was the problem i was having after you hit enter just type in reboot recovery and you should have 1.6.2 also maKE sure this file is the only file on your sd card that helps good luck man let me know what happens
yeah i renamed it to recovery-1.6.2.img and i just downloaded better terminal but how do you get the keyboard up?
just tap the screen
do you have g talk
sent pm to you
ieatstarz1 said:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.5.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
reboot recovery
This was complements of theresthatguy's method. Hope this helps.
Click to expand...
Click to collapse
This is what worked for me.
The 1.6.2 version did exactly to me like it is doing to you. I couldn't boot in to the recovery screen.
Sooo. I pushed the 1.5.2 image to the sdcard and then I
adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.5.2.img
I was then able to boot into the 1.5.2 recovery
I then pushed the 1.6.2 image again and then it worked.
Hi all,
I've done a search and not found anything that has helped. Long story short I think I have flashed the wrong stock image to my Nexus S so that I can get a warranty repair done.
The problem I am having is that my bootloader seems to be frozen and I cannot use fastboot to flash cwm again to install the stock nandroid that I found in the FAQ. The phone can boot normally and I can use adb but cannot do anything in the bootloader. I've also tried using adb to push the recovery to data but get a permission denied error.
Any helps guys as its kinda urgent.
FirmShark said:
Hi all,
I've done a search and not found anything that has helped. Long story short I think I have flashed the wrong stock image to my Nexus S so that I can get a warranty repair done.
The problem I am having is that my bootloader seems to be frozen and I cannot use fastboot to flash cwm again to install the stock nandroid that I found in the FAQ. The phone can boot normally and I can use adb but cannot do anything in the bootloader. I've also tried using adb to push the recovery to data but get a permission denied error.
Any helps guys as its kinda urgent.
Click to expand...
Click to collapse
What error are you getting in fastboot? You're on the fastboot screen and not trying to access the recovery, right?
Make sure you clean your phone of CWM recovery too before sending to warranty.
polobunny said:
What error are you getting in fastboot? You're on the fastboot screen and not trying to access the recovery, right?
Make sure you clean your phone of CWM recovery too before sending to warranty.
Click to expand...
Click to collapse
I boot into the bootloader and I cannot select any options on the menu, it appears frozen. "Fastboot devices" brings up no devices at all. ADB works when the phone is booted normally. Also it is on the stock recovery so I cannot flash the stock nandroid image that is available. I have got myself into a proper dilemma with it. Believe it or not I have been quite successful with rooting and flashing in the past but this has me puzzled.
I think it is down to the stock image I flashed which was Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader for the i9020a. I was always under the impression I had the i9020a as that's the ota updates I had used since I got the phone.
If I can get fastboot working again then I can flash cwm and restore the nandroid and get myself back to stock. Then I can re-lock the bootloader.
FirmShark said:
I boot into the bootloader and I cannot select any options on the menu, it appears frozen. "Fastboot devices" brings up no devices at all. ADB works when the phone is booted normally. Also it is on the stock recovery so I cannot flash the stock nandroid image that is available. I have got myself into a proper dilemma with it. Believe it or not I have been quite successful with rooting and flashing in the past but this has me puzzled.
I think it is down to the stock image I flashed which was Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader for the i9020a. I was always under the impression I had the i9020a as that's the ota updates I had used since I got the phone.
If I can get fastboot working again then I can flash cwm and restore the nandroid and get myself back to stock. Then I can re-lock the bootloader.
Click to expand...
Click to collapse
So if I get this straight:
-Booting into fastboot you cannot move your cursor using vol + or vol - (?)
-You cannot access recovery, which is stock
-You can use your phone but cannot do anything requiring SU permissions (not rooted)
-You are on stock ROM
-Device is unlocked
Is everything right?
-Booting into fastboot you cannot move your cursor using vol + or vol - (?)
Yeah that's what happens.
-You cannot access recovery, which is stock
I can reboot using adb to get to it. Recovery is stock.
-You can use your phone but cannot do anything requiring SU permissions (not rooted)
I can use my phone but cannot make/recieve calls or send/recieve sms. Wifi works however.
-You are on stock ROM
I am on stock 2.3.6.
-Device is unlocked
Device is unlocked.
Hopefully that clear's it up a bit. Beginning to worry about my phone now
Hi!
If ADB work , you can root your devices then you can change stock recovery with CWM 5.0.2.0 or......
How so? I don't know of a way to change the recovery using adb. I only know how to using fastboot which isn't working.
FirmShark said:
How so? I don't know of a way to change the recovery using adb. I only know how to using fastboot which isn't working.
Click to expand...
Click to collapse
If ADB work it's very easy....
You can changed by installing Rom Manager with root acces and rerwrite recovery with CWR....after that you can install all what you want...
Can you tell me how then as I can't find how to do it???
FirmShark said:
Can you tell me how then as I can't find how to do it???
Click to expand...
Click to collapse
ok
You must do exactly as I say and you will see that it is not hard ... it will root your phone
Yes, what are the instructions?
you need that : http://www.4shared.com/file/7wJht93f/Root.html
unpack in your pc...and waitt me...for detail...
it's not virus...I can help you ....
waitt me 5 min .....
I have downloaded the file.
if you are ready....let's go...
connect your device and see if adb responding >adb devices
normal you will see your id device or un number...and tell me
---------- Post added at 11:52 PM ---------- Previous post was at 11:52 PM ----------
FirmShark said:
I have downloaded the file.
Click to expand...
Click to collapse
ok just unpack
adb is working fine and my device is present.
FirmShark said:
adb is working fine and my device is present.
Click to expand...
Click to collapse
click cmd
>adb push files\zergRush /data/local/tmp/
>adb shell
#chmod 777 /data/local/tmp/zergRush
#exit
---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------
>adb shell
#./data/local/tmp/zergRush
WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
done that, now what?
>adb push files\busybox /data/local/tmp/
>adb shell
#chmod 755 /data/local/tmp/busybox
#exit
>adb shell
#/data/local/tmp/busybox mount -o remount,rw /system
#dd if=/data/local/tmp/busybox of=/system/xbin/busybox
#chown root.shell /system/xbin/busybox
#chmod 04755 /system/xbin/busybox
#/system/xbin/busybox --install -s /system/xbin
#rm -r /data/local/tmp/busybox
#exit
>adb push files\su /system/bin/su
done that now. what do i do now?
>adb shell
#chown root.shell /system/bin/su
#chmod 06755 /system/bin/su
#rm /system/xbin/su
#ln -s /system/bin/su /system/xbin/su
#exit
>adb push files\Superuser.apk /system/app/
>adb shell
#cd /data/local/tmp/
#rm *
#exit
>adb reboot
ALL DONE!!!
now instal ROM Manager for ClockWordMod Recovery
My son tried flashing his TF700T to a custom rom (jellybean 4.4.4)
that appeared to be successfull
however after a few days it rebooted itself and now only boots to the teamwin splash page and stays there
just prior to the teamwin splash page 4 green penguins appear in the top left hand corner of the display.
Let me know what additional information you need to help me diagnose and fix this issue
thanks in advance
dneusitz said:
My son tried flashing his TF700T to a custom rom (jellybean 4.4.4)
that appeared to be successfull
however after a few days it rebooted itself and now only boots to the teamwin splash page and stays there
just prior to the teamwin splash page 4 green penguins appear in the top left hand corner of the display.
Let me know what additional information you need to help me diagnose and fix this issue
thanks in advance
Click to expand...
Click to collapse
Do you have adb access when it is stuck on the twrp curtain ?
Thx Josh
it is stuck on the twrp/teamwin curtain
dneusitz said:
it is stuck on the twrp/teamwin curtain
Click to expand...
Click to collapse
Yes but connect it to a PC and see if you can get adb access. Search on the 700 forums here how to do that if you don't understand as it is too long to retype it all out for you.
adb devices returns the following
List of devices attached
0123456789ABCDEF recovery
please advise what i should do next
thanks
dneusitz said:
adb devices returns the following
List of devices attached
0123456789ABCDEF recovery
please advise what i should do next
thanks
Click to expand...
Click to collapse
What does this command do ?
Code:
adb reboot-bootloader
If you get there look in the upper left for the bootloader version ....
Should start with 'epad' and also contain the SKU of your tablet e.g. would be 'WW' 'US' 'TN'
Get this info if you can ....
Thx Josh
the command
adb reboot-bootloader
does nothing
the tf700t still is sitting on the twrp curtain. nothing appears on the screen
on the PC side the command appears to be waiting on a reply from the tf700t
dneusitz said:
the command
adb reboot-bootloader
does nothing
the tf700t still is sitting on the twrp curtain. nothing appears on the screen
on the PC side the command appears to be waiting on a reply from the tf700t
Click to expand...
Click to collapse
Try a different usb port ...
If that does not work, what does this do ......
Code:
adb shell
with change command prompt to shell, type this in shell
Code:
start recovery
What happens with this ?
Thx Josh
i appreciate your help and patience with me
tried different usb ports
still the same behaviour from adb reboot-bootloader as stated previously
adb shell returns
~ # 4[6n
please note that the 4 in the text above is actually a leftward pointing arrow
I do not understand your instruction "with change command prompt to shell, type this in shell"
when i type start recovery in front of the prompt returned by adb shell like this
~ # 4[6n start recovery
start recovery is echoed and i get the adb shell prompt again like this
~ # 4[6n start recovery
start recovery
~ # 4[6n
nothing happens on the tf700t. i am still at the twrp curtain
dneusitz said:
i appreciate your help and patience with me
tried different usb ports
still the same behaviour from adb reboot-bootloader as stated previously
adb shell returns
~ # 4[6n
please note that the 4 in the text above is actually a leftward pointing arrow
I do not understand your instruction "with change command prompt to shell, type this in shell"
when i type start recovery in front of the prompt returned by adb shell like this
~ # 4[6n start recovery
start recovery is echoed and i get the adb shell prompt again like this
~ # 4[6n start recovery
start recovery
~ # 4[6n
nothing happens on the tf700t. i am still at the twrp curtain
Click to expand...
Click to collapse
Ok, give this a try .....
http://forum.xda-developers.com/transformer-tf700/help/guide-t2853546
Thx Josh
the command
adb shell insmod /bootit.ko
causes the tf700t to shut down immediately
and the USB connection is lost
Next thing you can try to diagnose the problem when it hangs at the TWRP curtain (preferably 1-2 minutes after turning it on):
adb pull /tmp/recovery.log
adb shell dmesg > dmesg.txt
dmesg.txt and recovery.log files are attached
My thanks again for all the help
dneusitz said:
dmesg.txt and recovery.log files are attached
Click to expand...
Click to collapse
TWRP seems to hang after trying to mount the data partition. Run this to see if the mount worked:
adb shell mount > mount.txt
If the output file doesn't contain a line for /data, try mounting it manually and see if it contains the usual directories for an Android /data partition (e.g. app, data, local, media, misc, ...):
adb shell mount /data
ls /data > data.txt
If there is file system corruption on /data, we can try repairing or formatting it in the next step - is there any important data on the device that we should try to recover?
dneusitz said:
dmesg.txt and recovery.log files are attached
My thanks again for all the help
Click to expand...
Click to collapse
Maybe if you would also get a partition table .....
Code:
adb pull /proc/partitions
Thx Josh
adb shell mount > mount.txt output attached as is adb pull /proc/partitions
there is no line for /data in the mount.txt file
adb shell mount /data results in mount: can't read '/etc/fstab': No such file or directory
there is no data on the tablet that he needs to recover. everything of importance is on the SD card
dneusitz said:
adb shell mount /data results in mount: can't read '/etc/fstab': No such file or directory
Click to expand...
Click to collapse
Oops, I forgot that you need to specify everything when mounting manually in TWRP:
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p8 /data
You'll probably get another error message.
The command
adb shell mount -t ext4 /dev/block/mmcblk0p8 /data
never comes back from the tf700t
dneusitz said:
My son tried flashing his TF700T to a custom rom (jellybean 4.4.4)
that appeared to be successfull
however after a few days it rebooted itself and now only boots to the teamwin splash page and stays there
just prior to the teamwin splash page 4 green penguins appear in the top left hand corner of the display.
Let me know what additional information you need to help me diagnose and fix this issue
thanks in advance
Click to expand...
Click to collapse
I am having the same issue too
Hopefully this can be resolved... Hanks in advance!
dneusitz said:
The command
adb shell mount -t ext4 /dev/block/mmcblk0p8 /data
never comes back from the tf700t
Click to expand...
Click to collapse
OK, then TWRP is having the same problem which explains why it hangs. I've never seen mount hang, but this is most likely due to filesystem corruption.
To recreate the filesystem (this will irrecoverably delete all user data on the device), try this:
Code:
adb shell make_ext4fs -l -16384 -a /data /dev/block/mmcblk0p8
Make sure you get it exactly right - use copy+paste. The command should take a couple of seconds to minutes at most and output a few lines of text.