Related
I rooted my phone using the gfree method, i still have the file that saves to your phone when you perform that method. I got perm s-off with hboot 0.85.2007 I was and had been on a gorilla sense rom it was cool was working great, i already had flashed the zip that allowed me to go from clockwork 2.... to 3.... but before i went to thunderbolt rom I used trueblue_drew's updated zip the one he got from option94. I flashed the zip in recovery from clockwork 2....I did a nandroid and of the gorilla sense rom, booted back up and went into recovery again wiped data, partition and dalvik i then flashed thunderbolt from my sd card everything went through smooth. I rebooted completed the steps to set it up and was running smooth then out of nowhere my phone just turned off and went into bootloops, sowing the thunderbolt splash screen, i took off the battery and started my phone again and it wouldnt get past the first splash screen which is the initial my touch 4g splash but i had changed that screen a while back to a black screen from cynogen that reads rooted mytouch 4g with the green droid. I then took the battery out again then went into recovery by holding volume and power at this point i got the "cant mount" messages in clockwork i wiped the data but everytime it was done the "cant mount" messages would appear i tried to nandroid restore everyone i had on my sdcard and nothing worked. I tried flashing a older version of thunderbolt and nothing it just stays stuck on the first splash screen.
When i put the PD15IMG zip on my sd card it reads it then the blue status bar pops up and does its thing, it then asks me if i want to install update i press the volume button up for yes and a few seconds go by and on the first one 1.Bootloader i get the "fail PU" message and just says press power to reboot, i do and it takes me to the first splash screen and sits there.
When i am in Hboot screen and plug my phone in i see that it changes to "hboot usb plug" my system info is
sn-sh11yrmo7858
lcd-so-c2
touch panel-atmelc12_20aay
commit-7eafc656
os ver.-1.17.531.2
imei-359637039172891
cid-11111111
ram-768mb
emmc-samsung 2151mb 4407295 sectors
Like i said i have saved the part7backup file from the gfree method, and i have the clockwork folder saved everything else was wiped from my sd card.
I doubt i have adb set up correctly because i type a command and it says "the system cannot find the patch specified" Im slowly losing hope here i didnt think it was possible to brick a phone especially from what i did but i guess it is
Can you boot and get into the HBoot in your current status?
Did you check the MD5SUM of the download?
Sent from my HTC Glacier using Tapatalk
1 more thing that makes me mad ITS NOT BRICKED!!!!
if its a brick you cant get into Hboot or Recovery
anyways it should work also check if your SDCard is formatted to FAT32 (i think)
sounds like your SD card isn't formatted right or could be corrupted. you're not bricked if you can hboot
I am having the same issue, stating "it isn't bricked" without any explanation isn't very helpful. I have tried reformatting my SD card with no avail even tried a different SD card. as far as I am aware unless you have the eng-hboot there isn't a way to fix this since fastboot does not work
accido said:
I am having the same issue, stating "it isn't bricked" without any explanation isn't very helpful. I have tried reformatting my SD card with no avail even tried a different SD card. as far as I am aware unless you have the eng-hboot there isn't a way to fix this since fastboot does not work
Click to expand...
Click to collapse
If you can get into Fastboot or the Recovery Screen simply means just that it's not bricked. A truly bricked phone you cannot get into the engineering screen nor the recovery image.
On the HBoot screen can you get to recovery and access it? If so what comes up?
I dont understand the problem. it sounds like he got a bad download. If his sd was formated wrong it wouldnt load at all. oance you have clockwork installed it is impossabl to brick. You can pull your battery in the middle of a rom load and be fine
Sent from my HTC Glacier using XDA Premium App
When i hold the volume down and power it takes me into the hboot screen, if i have the PD15IMG.zip on my sdcard it automatically reads it then the blue status bar appears it loads then it asks if i want to start update, I press volume up and it fails. I noticed towards the bottom it says "Partition update fail" and under that "update fail"
I can go into recovery, ClockworkMod 3.0.0.5 recovery but i get a messages stating
E:cant mount ?cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
neidlinger said:
Can you boot and get into the HBoot in your current status?
Did you check the MD5SUM of the download?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
TheHypebeast said:
When i hold the volume down and power it takes me into the hboot screen, if i have the PD15IMG.zip on my sdcard it automatically reads it then the blue status bar appears it loads then it asks if i want to start update, I press volume up and it fails. I noticed towards the bottom it says "Partition update fail" and under that "update fail"
I can go into recovery, ClockworkMod 3.0.0.5 recovery but i get a messages stating
E:cant mount ?cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
Click to expand...
Click to collapse
Read through this thread, their should be some guidance hidden with in the scroll.
Link
I read through it, same issue im having only that he was on .86.0000 and im on .85.2007 and he was able to fix and restore with PD15IMG and i get the partition fail
neidlinger said:
Read through this thread, their should be some guidance hidden with in the scroll.
Link
Click to expand...
Click to collapse
Try flashing it through clockwork recovery. Put the zip image in a folder then boot holding volume down and power. When you can chose options in hboot go to recovery hit trackball. You should no what to do from there
Sent from my HTC Glacier using XDA Premium App
Keep looking for a better answer, but if you find nothing you can try this. You'll need adb and fastboot working.
Find an only nandroid, and put the system.img, boot.img and recovery.img from it in your android sdk tools folder.
Reboot into hboot by pressing volume down and power.
Scroll to fastboot and press power.
then type
Code:
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Then fastboot reboot and you should be ok.
lowandbehold helped me.
http://forum.xda-developers.com/showthread.php?t=992283&highlight=rom+manager+question
After the first "fastboot erase system -w" i get "erasing system..." and it just sits there i waited for about ten minutes, how long should that first one take?
option94 said:
Keep looking for a better answer, but if you find nothing you can try this. You'll need adb and fastboot working.
Find an only nandroid, and put the system.img, boot.img and recovery.img from it in your android sdk tools folder.
Reboot into hboot by pressing volume down and power.
Scroll to fastboot and press power.
then type
Code:
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Then fastboot reboot and you should be ok.
Click to expand...
Click to collapse
TheHypebeast said:
After the first "fastboot erase system -w" i get "erasing system..." and it just sits there i waited for about ten minutes, how long should that first one take?
Click to expand...
Click to collapse
Should only take a few seconds.
You may have a hardware problem at this point.
Yeah after i waited a good ten minutes i just unplugged my phone and immediately got "FAILED <status read failed <Too many links>> finished. total time: 510.438s
option94 said:
Should only take a few seconds.
You may have a hardware problem at this point.
Click to expand...
Click to collapse
after several tries now it just fails within seconds of running "fastboot erase system -w"
How can I get my computer to recognize my phone? I can't power up and no hboot with holding down power + vol down. Please help !!
TheHypebeast said:
Yeah after i waited a good ten minutes i just unplugged my phone and immediately got "FAILED <status read failed <Too many links>> finished. total time: 510.438s
after several tries now it just fails within seconds of running "fastboot erase system -w"
Click to expand...
Click to collapse
Could the partitions be wrong somehow? I do not know how to fix that, someone else may. I know sometimes the partitions can get out of wack, or at least I have heard of it on other devices, I think I recall it for this one as well.
Also, try downloading the img file again. I believe you must extract it one time to get the proper zip file needed to flash it. I believe the version I downloaded was the pd15img.zip compressed further into a second zip file. when you look in the file you should see several img files, not a folder.
Also, make sure you are using the proper recovery for the ROM, ROM manager app tells you to update your recovery every time you start it if you are not using 3.0.0.5, if you do update, the phone will keep running but if you later flash a new froyo ROM then you will have issues.
At this point, I would try re-downloading the pd15img file and trying fresh to rule out bad downloads, or flashing a known good ROM zip, and ensuring it works with your recovery version.
zion1827 said:
How can I get my computer to recognize my phone? I can't power up and no hboot with holding down power + vol down. Please help !!
Click to expand...
Click to collapse
Sounds like you are full bricked. That means you can not fix it.
It can be fixed, but only with special equipment that can flash information straight to the internal memory chips. Meaning you need access to the internal components along with the software and equipment. So that means HTC engineering dept is about the only ones who can.
It is really hard to brick a device. Only times you can do it are anytime the Hboot file is flashed or the radio is flashed. As those two files are what boots the hardware and readies the software to boot. Thing is, you don't flash those often. Just once for Hboot, and radio firmware updates are very rare.
Dev posts on rooting need to state that flashing the engineering Hboot should be optional AND only for those experienced in flashing and rooting. First time flashers should probably avoid it for a while.
Thing is, flashing the pd15img file can brick a device as it flashes Hboot and radio.
Try this method, let me know if it works for you..
----> Try not to plug Your device on your computer , Put your image in sd card/ then Reboot into the hboot-- and the phone the automatically detects you image in the sdcard and the phone do the rest.. If you see in the upper right corner a bar thats ok its fine.. The phone loads the image and wait be patient.. the it would ask you when its done if you want those settings to be back to stock ROM. Just Click the Up Volume button , and thats it... Try Backing up after you made some changes on the phone.... <------
chipis said:
----> Try not to plug Your device on your computer , Put your image in sd card/ then Reboot into the hboot-- and the phone the automatically detects you image in the sdcard and the phone do the rest.. If you see in the upper right corner a bar thats ok its fine.. The phone loads the image and wait be patient.. the it would ask you when its done if you want those settings to be back to stock ROM. Just Click the Up Volume button , and thats it... Try Backing up after you made some changes on the phone.... <------
Click to expand...
Click to collapse
Its not Brick it just stuck on something undone....
I have a Sprint Nexus S 4G that I keep in Airplane mode most of the time and rarely use (an hour a week at most, usually). I use it so rarely that it shuts off due to low battery a lot.
The last time it shut off, I wasn't able to boot it up when I turned it back on. It got stuck at the Google logo indefinitely with the bottom buttons lit up. I can boot to CWM Recovery (v6.0.1.9) but when I do, I get the log message "Error mounting /sdcard!" or "E:Can't mount /sdcard/" when I try to search for an update.zip on the phone, or try to mount or format /sdcard. I tried using the "adb sideload" command to install a ROM from CWM, which fails with:
E:Error in /tmp/update.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
I also tried using "adb push cm-10.1.2-crespo4g.zip /sdcard/", which does not fail with any errors but still am unable to mount /sdcard/ through CWM so that obviously isn't any help for me.
I can boot into fastboot and tried flashing back to stock with these commands using the image files from this thread.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash radio radio.img
fastboot erase cache
fastboot reboot
When I flashed using the commands above, I got no errors in the terminal but my phone still would not boot past the Google logo. Afterwards I was able to flash CWM Recovery back onto the phone with no problems but CWM still can't see the /sdcard partition.
I also tried all of the suggestions on this thread with no success.
Nexus S stuck on google boot logo
For an even crazier attempt at a solution, I found a person with a similar problem to mine where they ran a hair dryer over the phone for a few minutes to fix it. That didn't help, either.
I think my nexus died
At this point I'm out of ideas and was hoping someone else might know something I could try. I planned on getting a new phone soon anyway but was hoping to be able to use my old phone for a little while until that happens.
You've tried all sorts of things to recover the SD card portion. Which I think is badly corrupted.
I think your internal memory card has died. I suggest going for a new phone.
One last effort will be to install a different recovery and try formatting the SD card from there. Try Philz Touch or TWRP.
Sent from my Nexus S using Tapatalk 4
danherbert said:
I have a Sprint Nexus S 4G that I keep in Airplane mode most of the time and rarely use (an hour a week at most, usually). I use it so rarely that it shuts off due to low battery a lot.
The last time it shut off, I wasn't able to boot it up when I turned it back on. It got stuck at the Google logo indefinitely with the bottom buttons lit up. I can boot to CWM Recovery (v6.0.1.9) but when I do, I get the log message "Error mounting /sdcard!" or "E:Can't mount /sdcard/" when I try to search for an update.zip on the phone, or try to mount or format /sdcard. I tried using the "adb sideload" command to install a ROM from CWM, which fails with:
I also tried using "adb push cm-10.1.2-crespo4g.zip /sdcard/", which does not fail with any errors but still am unable to mount /sdcard/ through CWM so that obviously isn't any help for me.
I can boot into fastboot and tried flashing back to stock with these commands using the image files from this thread.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash radio radio.img
fastboot erase cache
fastboot reboot
When I flashed using the commands above, I got no errors in the terminal but my phone still would not boot past the Google logo. Afterwards I was able to flash CWM Recovery back onto the phone with no problems but CWM still can't see the /sdcard partition.
I also tried all of the suggestions on this thread with no success.
Nexus S stuck on google boot logo
For an even crazier attempt at a solution, I found a person with a similar problem to mine where they ran a hair dryer over the phone for a few minutes to fix it. That didn't help, either.
I think my nexus died
At this point I'm out of ideas and was hoping someone else might know something I could try. I planned on getting a new phone soon anyway but was hoping to be able to use my old phone for a little while until that happens.
Click to expand...
Click to collapse
I am also having the same situation. OP, were you able to resolve this issue?
Hi,
I've been looking for a solution to get a ROM to work on my phone with no success for the last few days, and I wonder if anyone knew if there is anything I can try to make it work again.
Code:
Rogers Evita
S-ON
HBOOT 2.14.0000
RADIO 0.23a.32.09.29
I put the phone in bootloop by flashing a Endeavour boot.img to it (stupid, yes...), and I'm now trying to get any ROM to work on it.
Here are the steps I tried to install a custom ROM :
Unlocked the bootloader with HtcDev
Flashed TWRP (tried 2.5.0.0 and 2.4.1.0)
Pushed a ROM zip with ADB (Tried CyanogenMod for Evita 10.0 and 10.1-20130813, and Calkulin's one xl ROM v 1.2)
Wiped Cache, Dalvik Cache and Facotry Reset from TWRP
Install ROM from TWRP
TWRP consistently says 'E:Unable to mount /sdcard' when wiping cache and then 'error flashing zip <name-of-the-rom>' when installing.
I also tried to install a stock ROM with the following steps
Relock bootloader
Download stock ROM. The closest I found from mine is 'RUU_Evita_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe'
Launch it from a windows machine
The installer fails and gives me an error 155.
I also tried to retrieve the rom from this installer via the %TEMP% directory, and to install it with Hasoon's Evita toolkit. The installation also fails and gives me 12 'signature' errors.
Lastly, I also tried without success to downgrade my hboot with JET (jet-evita-0.3.3b). The process loops at 'Failed to flash HBoot!!' despite the fact I tried multiple cable / USB ports combinations. The 'jet -u' command worked to unbrick the phone, and the bootloader now works.
Do you guys know if there is something I can try to get a ROM to work ?
Thanks for your help
Well, it seems your original problem was that you didn't flash boot image. What you're going to want to do now is
1. Unlock through HTC dev.
2. Find rom you want
3. Extract boot image and flash via fastboot
4. S-Off so you won't have to flash boot image again.
Sent from my evita
pigeonagressif said:
Hi,
I've been looking for a solution to get a ROM to work on my phone with no success for the last few days, and I wonder if anyone knew if there is anything I can try to make it work again.
Code:
Rogers Evita
S-ON
HBOOT 2.14.0000
RADIO 0.23a.32.09.29
I put the phone in bootloop by flashing a Endeavour boot.img to it (stupid, yes...), and I'm now trying to get any ROM to work on it.
Here are the steps I tried to install a custom ROM :
Unlocked the bootloader with HtcDev
Flashed TWRP (tried 2.5.0.0 and 2.4.1.0)
Pushed a ROM zip with ADB (Tried CyanogenMod for Evita 10.0 and 10.1-20130813, and Calkulin's one xl ROM v 1.2)
Wiped Cache, Dalvik Cache and Facotry Reset from TWRP
Install ROM from TWRP
TWRP consistently says 'E:Unable to mount /sdcard' when wiping cache and then 'error flashing zip <name-of-the-rom>' when installing.
I also tried to install a stock ROM with the following steps
Relock bootloader
Download stock ROM. The closest I found from mine is 'RUU_Evita_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe'
Launch it from a windows machine
The installer fails and gives me an error 155.
I also tried to retrieve the rom from this installer via the %TEMP% directory, and to install it with Hasoon's Evita toolkit. The installation also fails and gives me 12 'signature' errors.
Lastly, I also tried without success to downgrade my hboot with JET (jet-evita-0.3.3b). The process loops at 'Failed to flash HBoot!!' despite the fact I tried multiple cable / USB ports combinations. The 'jet -u' command worked to unbrick the phone, and the bootloader now works.
Do you guys know if there is something I can try to get a ROM to work ?
Thanks for your help
Click to expand...
Click to collapse
TWRP versions 2.4.x and 2.5.x are riddled with bugs so that's why the ROM wouldn't flash.
You'll need to unlock your bootloader, then download TWRP 2.6 from here. Put the TWRP file in your fastboot folder, connect your phone, open command prompt from within fastboot folder, and issue these commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Extract the boot.img from the ROM zip and put that in your fastboot folder, we'll come back to that in a minute.
Now you can enter recovery, make a backup, perform a full wipe (cache/dalvik/factory reset/system), install ROM, reboot to bootloader, make sure phone is connected and it says fastboot usb on the screen, issue this command:
fastboot flash boot boot.img
(You have to do this every time you want to change ROMs because you're s-on)
Reboot phone.
Sent from my Evita
Thank you timmaaa and RollTribe for your quick answer !
I unlocked my bootloader, downloaded TWRP 2.6 and issued :
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
Then tried to do a full wipe, but it failed :
Code:
Formatting cache using mke2efs...
Done.
Formatting data using mke2fs...
Done.
E:Unable to mount '/sdcard'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount storage.
Rom installation failed with a similar log :
Code:
E:Unable to mount '/sdcard'
Error flashing zip '/sdcard/cm-10.1-20130813-NIGHTLY-evita.zip'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount storage.
I've looked for a solution to the possible sdcard corruption problem, but all the posts I see link to a dead thread from team nocturnal of which I can't post the url.
There is an associated youtube video (again, can't post url but it is named 'How to Fix corrupt/unmountable internal storage on the HTC One X'), but it is not of much help without the 'recovery.img' file they use.
Is there another way to solve the sdcard issue ?
Thanks again
Ok, in fact the fix for the sd card was easy!
There is an option to wipe the sd card in TWRP that I had missed. When this was done, everything worked!
I now have a working 10.1 CM!
Thanks again
Glad we could be of help!
Sent from my evita
pigeonagressif said:
Ok, in fact the fix for the sd card was easy!
There is an option to wipe the sd card in TWRP that I had missed. When this was done, everything worked!
I now have a working 10.1 CM!
Thanks again
Click to expand...
Click to collapse
i faced the same problem
its solved by formatting sdcard0
tnx
rasoulcarrera said:
i faced the same problem
its solved by formatting sdcard0
tnx
Click to expand...
Click to collapse
Are you aware that you're replying to a thread that's 18 months old?
Yes!
And keep it in ur mind people's won't get same problems just in same time !
Isn't it?
I made a really stupid mistake...
The Good Part:
...I flashed my bootloader/blob via fastboot with the latest update from ASUS (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), and at that point no problems. Messed around with the thread that mentioned CWM (regular and JB). Found that I couldn't access the SD Cards with CWM JB, so I tried flashing TWRP.
The Bad Part:
I read everything closely, ..... except the darn file name on the TWRP site, so I ended up flashing the TF300TG by accident, instead of the TF300T recovery.
Here's the sum of what I have left:
- no fastboot (Power + VOL DOWN won't work)
- I read about APX mode (Power + VOL UP???) but no dice there if that is supposed to work
- after i realized I lost fastboot I think I panicked and managed to erase the current firmware, so no OS currently on the device
- I think that I may have killed busybox on the device, and any chance of fully using ADB the normal way to restore ROOT/anything else
- I can get into TWRP recovery
- I can use the ADB connection, but none of the commands that would normally use busybox actually work
- under NORMAL circumstances I can't access the internal memory (/SDCard/ mount) nor can I access the external memory
- I CAN select the option to mount SYSTEM, but the contents of SYSTEM are actually my external SD Card (so I can put files on my device)
Through my hours of googling (and searching XDA) i found a thread for another device that mentioned fixing the mount points. I can't seem to find that thread, but again it was for another device, so the commands would probably be different for all the mount points anyways.
So in a nutshell:
- I can use the basic linux commands (like LS and CD), on ADB and in TWRP command line mode, but no mount or push/pull commands
- I can mount "SYSTEM" from TWRP GUI but the contents of SYSTEM are actually my external SD Card, so I can put files on the device
- I can still use TWRP to CHMOD stuff
--->>> Remaining mounts that seem in tact: (all entries are folders unless specified / anything not specified such as ROOT or SDCARD exists but is blank)
- / contains
/default.prop and several other files
- /DEV/
/block
/bus
/graphics
/input
/log
/ts
/snd
/socket
- /ETC/
/fstab (file)
/mke2fs.conf (file)
/mtab (file)
/recovery.fstab (file)
- /LICENSE/
/openaes
- /PROC/
...... lots of folders with numbers for file name
- /RES/
/fonts
/images
- /SBIN/
...lots of files... starting with [, [[, adbd, adjtimex, arp, ash, awk, base64.....
- /SUPERSU/ ... (i tried install from zip with superuser and SuperSU, and TWRP keeps offering to install SU every time I restart)
/99SuperSUDaemon (file)
/install-recovery.sh (file)
/su (file)
/Superuser.apk (file)
- /SYS/
/block
/bus
/class
/dev
/devices
/firmware
/fs
/kernel
/module
/power
/tf_driver
- /SYSTEM/
/bin (but it is empty, when I actually mount SYSTEM, it is then replaced with the contents of my external SD Card)
- /TMP/
/recovery.log (file) ... I think this was an attempt to use TWRP command button to "Copy Log to SD"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I know recovering from this is a major long shot, but the good news is, I have all the data backed up, so nothing is actually lost. Granted I have brick, but it's a brick that I can actually play with, and ADB still partially works. I was wondering about manually installing busybox, fixing mount points, etc, so that I could get back to a state of flashing the proper recovery and/or reflashing the bootloader to an older version.
Of course I'm noob enough to not know exactly where to start, with manually reviving busybox, fixing mount points, and using all this to actually push a bootloader or recovery without fastboot ... and I'm hoping desperately that someone will take a little pity (at least enough to see me squirm???)
I'll appreciate any advice at all to help me recover from my stupidity. I know this is a major long shot. Of course, I'm not above paying ASUS a pretty penny to fix it either, but I'd rather learn and better myself before I shell out money.
I've read a few things about letting the battery completely run out when trying to fix some cases of BRICK ... and supposedly that may get you fastboot back, but I'm holding off on that for the time being while it seems that I may still have a shot since I don't exactly have a 100% brick. My device won't stay on, I can shut it off... (i also read that device staying on all the time = brick??)
Potential Soultion
Quote:
TheArkive said:
I made a really stupid mistake...
The Good Part:
...I flashed my bootloader/blob via fastboot with the latest update from ASUS (TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip), and at that point no problems. Messed around with the thread that mentioned CWM (regular and JB). Found that I couldn't access the SD Cards with CWM JB, so I tried flashing TWRP.
The Bad Part:
I read everything closely, ..... except the darn file name on the TWRP site, so I ended up flashing the TF300TG by accident, instead of the TF300T recovery.
Here's the sum of what I have left:
- no fastboot (Power + VOL DOWN won't work)
- I read about APX mode (Power + VOL UP???) but no dice there if that is supposed to work
- after i realized I lost fastboot I think I panicked and managed to erase the current firmware, so no OS currently on the device
- I think that I may have killed busybox on the device, and any chance of fully using ADB the normal way to restore ROOT/anything else
- I can get into TWRP recovery
- I can use the ADB connection, but none of the commands that would normally use busybox actually work
- under NORMAL circumstances I can't access the internal memory (/SDCard/ mount) nor can I access the external memory
- I CAN select the option to mount SYSTEM, but the contents of SYSTEM are actually my external SD Card (so I can put files on my device)
Through my hours of googling (and searching XDA) i found a thread for another device that mentioned fixing the mount points. I can't seem to find that thread, but again it was for another device, so the commands would probably be different for all the mount points anyways.
So in a nutshell:
- I can use the basic linux commands (like LS and CD), on ADB and in TWRP command line mode, but no mount or push/pull commands
- I can mount "SYSTEM" from TWRP GUI but the contents of SYSTEM are actually my external SD Card, so I can put files on the device
- I can still use TWRP to CHMOD stuff
--->>> Remaining mounts that seem in tact: (all entries are folders unless specified / anything not specified such as ROOT or SDCARD exists but is blank)
- / contains
/default.prop and several other files
- /DEV/
/block
/bus
/graphics
/input
/log
/ts
/snd
/socket
- /ETC/
/fstab (file)
/mke2fs.conf (file)
/mtab (file)
/recovery.fstab (file)
- /LICENSE/
/openaes
- /PROC/
...... lots of folders with numbers for file name
- /RES/
/fonts
/images
- /SBIN/
...lots of files... starting with [, [[, adbd, adjtimex, arp, ash, awk, base64.....
- /SUPERSU/ ... (i tried install from zip with superuser and SuperSU, and TWRP keeps offering to install SU every time I restart)
/99SuperSUDaemon (file)
/install-recovery.sh (file)
/su (file)
/Superuser.apk (file)
- /SYS/
/block
/bus
/class
/dev
/devices
/firmware
/fs
/kernel
/module
/power
/tf_driver
- /SYSTEM/
/bin (but it is empty, when I actually mount SYSTEM, it is then replaced with the contents of my external SD Card)
- /TMP/
/recovery.log (file) ... I think this was an attempt to use TWRP command button to "Copy Log to SD"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I know recovering from this is a major long shot, but the good news is, I have all the data backed up, so nothing is actually lost. Granted I have brick, but it's a brick that I can actually play with, and ADB still partially works. I was wondering about manually installing busybox, fixing mount points, etc, so that I could get back to a state of flashing the proper recovery and/or reflashing the bootloader to an older version.
Of course I'm noob enough to not know exactly where to start, with manually reviving busybox, fixing mount points, and using all this to actually push a bootloader or recovery without fastboot ... and I'm hoping desperately that someone will take a little pity (at least enough to see me squirm???)
I'll appreciate any advice at all to help me recover from my stupidity. I know this is a major long shot. Of course, I'm not above paying ASUS a pretty penny to fix it either, but I'd rather learn and better myself before I shell out money.
I've read a few things about letting the battery completely run out when trying to fix some cases of BRICK ... and supposedly that may get you fastboot back, but I'm holding off on that for the time being while it seems that I may still have a shot since I don't exactly have a 100% brick. My device won't stay on, I can shut it off... (i also read that device staying on all the time = brick??)
Click to expand...
Click to collapse
Hi there.
Buster99 kind of had the same problem, and he managed to unbrick it.
All credit goes to Buster99.
Here is his post:
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Hope this helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
You guys rock! I'll try that as soon as i get home!!
∫εทт ƒя๑๓ ๓γ αทδя๑ïD
Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!
Quote:
TheArkive said:
Successfully unbricked!!!
I can't thank you guys enough!
At the moment I'm able to run the stock 4.2.1. TWRP (the right one) is installed, and all seems to be working. When I did a backup of the stock ROM on TWRP it said FAILED up top, but everything else seemed to go ok. There were 2 other error messages too:
Code:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
I know usually the recovery and boot aren't messed with when running a custom recovery, so I didn't really worry about it, but I figured I'd post it here just in case.
Now I'm messing around with a few versions of CyanogenMod. I guess I'll try the "failed" backup if neither version of CM wants to work. Since I have fastboot back I can of course re-load the blob from the 4.2.1 stock update.
Seems like the latest stable CM (10.0.0) doesn't work so well on the 4.2.1 bootloader? Or should it matter? Now I'm trying the nightly (10.2) and it loaded up much quicker than CM 10.0
Thanks again guys!
Click to expand...
Click to collapse
Glad to have helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS
hatdrc said:
Buster,
Looking around you are the master with these tablets. I have a question. I am on CM 10.2 I flashed TWRP 2.6.3.0 In my hast I flashed the TF300TG recovery. My tablet always boots straight to recovery but I can't mount anything. I discovered that I can use ADB commands and have it boot to the bootloader. From there I can select the android operating system and the tablet boots and runs as normal. I then tried to flash the correct recovery the same way through terminal emulator on the tablet. It says that it pushed the recovery fine but no change was made. I then tried booting into fastboot and flashing through the computer. As soon as I hit enter the green flashing box around RCK stops flashing and the computer says it was successful but it just sits there. I have to force the tablet to reboot. Reboots right to recovery with no change and I have to use ADB to get back to the bootloader in order to boot the tablet.
Is there another way to get recovery on the tablet? Do you think I'm going to have to redo the whole thing in order to get it working again? Not sure if it matters but in fastboot it says Key driver not found.. Booting OS
Click to expand...
Click to collapse
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
try fastboot erase recovery then reflash scannos latest twrp for kitkat from his omnirom thread. (also i think that 2.6.3.0 and above are kitkat recoveries)
this way you are at least sure that your recovery partition is clean.
also I use @scanno omni rom as my daily driver try it. (but bear in mind that without a jb backup you will have to do some work getting jb running again)
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I went into fastboot and and erase recovery. Did it. Then I tried to flash recovery and again it locks up. Rebooted and it went straight to CM 10.2 Tried flashing recovery with terminal emulator. Said it was copied. Rebooted went back to CM. Rebooted again to recovery but it went back to CM. Booted to fastboot again and selected RCK. now it says
Booting Recovery kernel image
Booting failed
Unrecoverable bootloader error (0x00000000)
It does boot to CM but now I have no recovery. OmniRom was the one I wanted to flash but at this point I'm thinking im going to have to start from square one. I just don't understand why it doesn't want to flash a recovery
Thank you for your help, you are the man
strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
strange, which recovery did you try to flash just now? what is the output in fastboot when you flash the recovery there?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was trying to flash the most current blob from the twrp site. I get the following:
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.965s]
finished. total time: 1.965s
fastboot -i 0x0b05 flashe recovery twrp.blob
sending 'recovery' (6448 kb)...
OKAY [ 2.561s]
writing 'recovery'...
OKAY [ 2.394s]
finished. total time: 4.955s
When I erase recovery the green flashing box on the tablet keeps flashing. When I try to flash the recovery the box just stops on what ever shade of green it was on when I hit enter. Also after if I do fastboot devices I get:
???????????? fastboot
hatdrc said:
fastboot -i 0x0b05 flashe recovery twrp.blob
Click to expand...
Click to collapse
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app
Buster99 said:
flashe?
please try scannos version via fastboot.
gl
buster
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry, typo. Should have been flash.
So i unzipped the recovery.img file and placed it in my fastboot folder. I get the same results.
fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' (6892 KB)...
OKAY [ 2.445s]
writing 'recovery'...
OKAY [ 2.477s]
finished. total time: 4.922s
The green box stops flashing as soon as I hit enter
Could it be that my recovery partition as gotten messed up, would formatting it help you think. Guess there's only one way to find out.
EDIT: Never mind, can't format a 'basic' filesystem
huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
huh?
fastboot erase recovery
then
fastboot reboot bootloader
then
fastboot flash recovery scannostwrp2.6.3.1
fastboot reboot
then boot into recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Still a no go. The only recover on there was a flashable zip file. That's why I was trying to get anything on it so I could flash that. I'm at the end of my knowledge. I've always had Samsung so I got use to odin. Never had to use fastboot. I really appreciate your help. Guess its going to have to run CM10.2 and hope it doesn't have a problem
Sent from my SGH-T999 using Tapatalk
odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
odin is a bastardisation of standards set by google.
please check the tf300 forum. there is a how to for noobs or smth like that with a script that does all. mb you have more luck with that
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will take a look, and I thank you for the time you have spent with me! If all else fails at least its running and usable for now.
Sent from my SGH-T999 using Tapatalk
Buster99 said:
Hi,
well with wrong twrp it only means your mount points are wrong - so as long as you dont wipe/erase anything within twrp your PITs should be ok.
and with twrp loading you still be able to issue adb commands - have you tried "adb reboot bootloader" while in twrp?
you said you can't boot into fastboot with pressing the keys but using the adb command it should boot into something. Also have you tried getting to fastboot using the reset button?
Whatever you do - do not issue any erase/wipe command while in the wrong recovery.
plaese check if you can get to fastboot either via adb command or reset button. if yes - first flash the correct recovery then i would suggest to see if you can flash stock rom blob to make sure all PITs are ok. from then you can go and flash a custom rom.
and don't try fixing the mount points manually - since they have been changed around a bit by asus from every which version. only if someone has a solution for your FW version you were running you could try it - but i haven't seen one yet for the newer FWs. (i think i remember one for 4.0.4 but that would likly result in a more severe brick than now)
gl
cheers
-Buster
Click to expand...
Click to collapse
Hi Buster,
I have a similar problem, but I cant reach the fastboot. I tried to reset and push volume down, connect tablet to PC with volume down pushed, turn off and start the tablet with the volume down pushed, but nothing. My recovery is corrupted, because it doesnt recognize any file in the SD. I tried to type adb reboot bootloader from the pc, but it says "erro: device not found".
Do you have any idea?
Help
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
+needle wont do anything for me cos mine boots to twrp logo and stay there for ever until battery is drained :/ hellp
It's not the exactly the same problem... For me ADB doesnt work.....
ConsoleFreak said:
this problem looks similiar to mien can you pls read my problem and help me? why no replies? I had a feel that the devs of this site are the best but no one helped me
http://forum.xda-developers.com/showthread.php?t=2755322
Click to expand...
Click to collapse
Hi,
Sorry for my english... I'm French.
I have a tf700 with bootloader 10.6.1.14.10.
I can run the recovery, but he said: Unable to mount Data.
What can i do for repair the tablet ?
thx
You need to provide more information. Which recovery and ROM do you have and what did you do when this happened?
I have the rom "CrombiKK",for re-install the tablet => I do Full Wipe, dalvik cache, format Data.
After 2 hours format Data, i have turn off the tablet (bad idea). Now, i have error mount Data and Data/media in recovery, and bootloop when i turn on my tf700.
I have access at FastBoot, recovery ( I can install Trwp or CWM)
Boot to recovery.
You should have adb access in recovery, check it with
Code:
adb devices
Then, if you have adb (if not you'll have to install adb recovery drivers on your PC) run these commands
Code:
adb shell
make_ext4fs /dev/block/mmcblk0p8
adb reboot-bootloader
Boot to TWRP again and flash the rom. It should work now.
Good luck
Thx for the answer, I test this tonight when i go home.
I have tried to format with TWRP but after 1 hour, the progress bar don't move...
angel46 said:
Thx for the answer, I test this tonight when i go home.
I have tried to format with TWRP but after 1 hour, the progress bar don't move...
Click to expand...
Click to collapse
Yep, TWRP 2.7.+ can take 90 minutes or more to complete the format. If you interrupt it, you get what you have now