Related
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.
sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it
akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.
sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!
sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.
rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!
sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...
Please does anyone have a solution to this? please help me
Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?
Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.
i did that but no response.
Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
PLEASE help : My phone stopped working after trying to change it to a L09 and now is dependent on the company's logo and does not accept any Software
You need to read about flashing from the bootloader using fastboot. You will be able to get it back working but you will need to get an extracted rom to flash the right parts.
Now I have a bit of time, I will tell you how I solved my issues. My phone was stuck with only the bootloader screen available or the eRecovery screen which would not find any suitable download. It said that the bootloader was unlocked yet I could not flash anything that I have extracted using the ROM extractor.
After much frustration I opened and ADB session and used Fastboot commands and re-entered the number in the Fastboot OEM Unlock command and it then confirmed that it was actually unlocked. It seems that although it said it was, it really wasn't.
Now that I knew it was unlocked, I could now start to flash parts of the extracted ROM.
I used the Huawei Rom Extractor tool to extract the Boot, Cache, Cust, Recovery, System and the Userdata image files of the ROM I needed and in this case it was the CRR-UL00470B110. I renamed the extracted files and removed the prefix numbers and put them in the ADB folder for ease of flashing.
I then used the Fastboot command to flash each part in the normal Fastboot format i.e. - Fastboot flash system system.img , and so on for each part. A reboot after brings it up in a nice new live usable phone. Well that is what I thought until I started to load the apps back on. I then noticed that I only had about 3gb left of my 64gb of memory! This took me a while to resolve and after more reading, more flashing of different ROMs I found the answer.
I had to flash the TWRP recovery using Fastboot, then format the data partition from TWRP. This restored the full size of the partition. Another flash of the correct recovery using Fastboot left me with a fully working unbricked Mate S.
I know that some of you may know all about this but I could not find any information and had to work through it myself and from various websites. I hope that this will help you to unbrick your phone.
I still think there may be something missing like the oeminfo file etc. but at least it works, you may just have to update it in future using adb and Fastboot if no OTA is available or works. Not too much of a worry now you know how to do it.
I should also add that if you ever get an 'Invalid Argument' when flashing in fastboot mode and some oparts flash while others dont, it will be your cable. Trust me, one cable workws well another gives you this Invalid Argument error! Strange but true and may catch you out.
Thank you(Sathelp) to help me to solve the problem of mate s mobile, but I found only three orders adb work when used fastboot screen, there are boot, recovery and cust but the system and other order give fault result in adb. Therefore the phone remain broken. ..sorry for language
Is it possible to provide me a complete backup copy of the phone to be downloaded to my phone via the twrp recovery , perhaps back to life again, I would be grateful to you
my p[hone is a U00 not a L09, so my back up will not work. Have you changed your cable, I had simular problem, changed cable and other ROM parts worked OK. If not, then you will need to ask for a L09 TWRP back up from here. May be someopne will make one for you.
Finally, the problem has been resolved and the phone returned to work and all this is due to the help of (Sathelp), which benefited greatly from his observations in this matter ,the issue has been resolved by updating the ADB and the execution of an order (FASTBOOT FLASH SYSTEM.IMG) , which i could not be implemented except adb updated, but the phone remained unresponsive for OTA updates and remained on the android 5. Thank to xda forums.
Glad it is now working
Huawei Mate S CRR-L09 bricked
Hi
I have a Huawei Mate S (CRR-L09) does not work and remains stuck on the android logo. Mention that is installed TWRP and I tried to "wipe data factory reset". I accidentally erased everything on it, including Systema. I did not back up your data and restore the system. I downloaded firmware B145 stock on which I copied to root your phone but, but can not flash TWRP. I entered the menu Update (Vol + Vol- and Power) but does not see that folder "dload". Can someone help me with a backup or a tutorial on how to flash TWRP firmware.
Thank you
Was using my tf701 the other day(running KatKiss - Nougatella #022)(which I've had no problems with) and my system restarted to the asus start screen then powered down now I can only get into the recovery.(twrp)
I can do things in twrp(have tried wiping and installing KatKiss - Nougatella #23, gapps and super su plus I repaired the system but trying to repair the data fails) but it is slow to load and restart though. I think something is wrong with the data since it is reporting nothing there(I could be wrong as well) but I can't find a way to fix whatever is the issue.
Any help would be greatly appreciated.
Since I have not had any suggestions yet I thought I would get into twrp and try a few things again.
First I tried to restore a backup and that failed then I tried to fix the data which failed as well.(not to surprised)
So I have added a pic taken with my phone in hopes that this will help solve this. first red is from the restore the second from the fix the data. Again any help would be greatly appreciated.
https://forum.xda-developers.com/attachment.php?attachmentid=4166710&stc=1&d=1496212872
Oakridgech said:
Was using my tf701 the other day(running KatKiss - Nougatella #022)(which I've had no problems with) and my system restarted to the asus start screen then powered down now I can only get into the recovery.(twrp)
I can do things in twrp(have tried wiping and installing KatKiss - Nougatella #23, gapps and super su plus I repaired the system but trying to repair the data fails) but it is slow to load and restart though. I think something is wrong with the data since it is reporting nothing there(I could be wrong as well) but I can't find a way to fix whatever is the issue.
Any help would be greatly appreciated.
Since I have not had any suggestions yet I thought I would get into twrp and try a few things again.
First I tried to restore a backup and that failed then I tried to fix the data which failed as well.(not to surprised)
So I have added a pic taken with my phone in hopes that this will help solve this. first red is from the restore the second from the fix the data. Again any help would be greatly appreciated.
https://forum.xda-developers.com/attachment.php?attachmentid=4166710&stc=1&d=1496212872
Click to expand...
Click to collapse
Looks as if you have a corrupted data partition. You will have to format it, losing any and all data on the tablet I'm afraid. Hopefully you one of those that know that data not backed up is data not yet lost....
Formatting /data in any recent version of TWRP takes an hour +. Do not interrupt it.
Afterwards you should be able to reflash the rom
berndblb said:
Looks as if you have a corrupted data partition. You will have to format it, losing any and all data on the tablet I'm afraid. Hopefully you one of those that know that data not backed up is data not yet lost....
Formatting /data in any recent version of TWRP takes an hour +. Do not interrupt it.
Afterwards you should be able to reflash the rom
Click to expand...
Click to collapse
Thanks for the reply. I had a few minutes before bed so I tried a few things.
First I formatted data as you suggested and only took about 3-4 minutes for what ever reason.(PIC below)
https://forum.xda-developers.com/attachment.php?attachmentid=4167685&stc=1&d=1496298521
Then I rebooted the tablet into twrp and installed rom, gapps, and supersu(successfully according to twrp)(log below)
https://forum.xda-developers.com/attachment.php?attachmentid=4167686&stc=1&d=1496298521
After the tablet sat at the Asus start screen for 6 minutes I rebooted into twrp and noticed this log below.
https://forum.xda-developers.com/attachment.php?attachmentid=4167687&stc=1&d=1496298521
Hopefully this gives some helpful info so you or someone else could steer me in the right direction.
Oakridgech said:
Was using my tf701 the other day(running KatKiss - Nougatella #022)(which I've had no problems with) and my system restarted to the asus start screen then powered down now I can only get into the recovery.(twrp)
I can do things in twrp(have tried wiping and installing KatKiss - Nougatella #23, gapps and super su plus I repaired the system but trying to repair the data fails) but it is slow to load and restart though. I think something is wrong with the data since it is reporting nothing there(I could be wrong as well) but I can't find a way to fix whatever is the issue.
Any help would be greatly appreciated.
Since I have not had any suggestions yet I thought I would get into twrp and try a few things again.
First I tried to restore a backup and that failed then I tried to fix the data which failed as well.(not to surprised)
So I have added a pic taken with my phone in hopes that this will help solve this. first red is from the restore the second from the fix the data. Again any help would be greatly appreciated.
https://forum.xda-developers.com/attachment.php?attachmentid=4166710&stc=1&d=1496212872
Click to expand...
Click to collapse
I had a very similar problem and a post from sdbags over in the TWRP thread helped me.
Enter TWRP Recover
Tap Advanced
Tap Terminal
Enter: make_ext4fs /dev/block/mmcblk0p14
Reinstall your ROM
jhermit said:
I had a very similar problem and a post from sdbags over in the TWRP thread helped me.
Enter TWRP Recover
Tap Advanced
Tap Terminal
Enter: make_ext4fs /dev/block/mmcblk0p14
Reinstall your ROM
Click to expand...
Click to collapse
Thanks for the reply.
Did as per your suggestion but still the same.
Oakridgech said:
Thanks for the reply.
Did as per your suggestion but still the same.
Click to expand...
Click to collapse
No change or is the cache partition the one that is now corrupted?
jhermit said:
No change or is the cache partition the one that is now corrupted?
Click to expand...
Click to collapse
Thanks for the reply. Not sure as I can not see any difference so it could be one or both. I have posted every pic I can think of(in previous posts) plus it takes about 3 min for twrp to load and shutdown. So other than those things(unless I'm missing something) I'm not really sure what is going on since I don't know much about these things. Any help would be greatly appreciated.(I miss having my tablet)
Oakridgech said:
Thanks for the reply. Not sure as I can not see any difference so it could be one or both. I have posted every pic I can think of(in previous posts) plus it takes about 3 min for twrp to load and shutdown. So other than those things(unless I'm missing something) I'm not really sure what is going on since I don't know much about these things. Any help would be greatly appreciated.(I miss having my tablet)
Click to expand...
Click to collapse
Try formatting /data in TWRP and do not interrupt it, it can take an hour+
If that doers not work the only thing I can think of is to try a buster99 = flashing the Asus firmware blob in fastboot. This has saved many soft bricked Prime, TF300 and TF700. Cannot say I ever read this done successfully on a TF701, but what have you got to lose???
berndblb said:
Try formatting /data in TWRP and do not interrupt it, it can take an hour+
If that doers not work the only thing I can think of is to try a buster99 = flashing the Asus firmware blob in fastboot. This has saved many soft bricked Prime, TF300 and TF700. Cannot say I ever read this done successfully on a TF701, but what have you got to lose???
Click to expand...
Click to collapse
Thanks for the reply. Ok will try formatting data again. What the heck is (try a buster99 = flashing the Asus firmware blob in fastboot) and how do I do that?
No nothing to lose at this point.
Oakridgech said:
Thanks for the reply. Ok will try formatting data again. What the heck is (try a buster99 = flashing the Asus firmware blob in fastboot) and how do I do that?
No nothing to lose at this point.
Click to expand...
Click to collapse
You would know if you googled the term - it has saved hundreds of tablets
But here's the short of it:
You download the latest Asus firmware from here: https://www.asus.com/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
You extract the zip twice until you find a blob file. Copy the blob into your fastboot folder.
Then you connect to your tablet in fastboot. If that is mystery to you read this and get fastboot set up on your PC: https://forum.xda-developers.com/showthread.php?t=2688891
Once 'fastboot devices' gets you a positive response, issue these commands one after the other, letting each one finish until you see the next prompt
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
The first 6 commands should finish fairly quick. Flashing the blob to /system could take a few minutes - let it finish.
As I said: I do not know of anyone trying this on TF701, so you do this on your own dime and good luck!
berndblb said:
You would know if you googled the term - it has saved hundreds of tablets
But here's the short of it:
You download the latest Asus firmware from here: https://www.asus.com/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
You extract the zip twice until you find a blob file. Copy the blob into your fastboot folder.
Then you connect to your tablet in fastboot. If that is mystery to you read this and get fastboot set up on your PC: https://forum.xda-developers.com/showthread.php?t=2688891
Once 'fastboot devices' gets you a positive response, issue these commands one after the other, letting each one finish until you see the next prompt
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
The first 6 commands should finish fairly quick. Flashing the blob to /system could take a few minutes - let it finish.
As I said: I do not know of anyone trying this on TF701, so you do this on your own dime and good luck!
Click to expand...
Click to collapse
Thanks for the reply. Thanks for simplifying it for me much appreciated. Only had to unzip once. Did all and got nothing. I don't think it worked cause twrp was still there after I did it.(But I could be wrong)
I'm really dumb founded that whatever happened happened and not sure why or how to fix it. I just tried flashing the old twrp that didn't work then booting from the old twrp image and formatting data and installing stuff but nothing worked. I don't know what caused my tablet to be so slow getting into twrp or why I can't seem to install or wipe anything. Again any further help would be greatly appreciated.
Well since it has been almost a month I will assume I'm sol but thanks to the two that tried to help.
A couple weeks ago I got a tf700 to hold me over till I got a fix or another tf701. The tf700 was used though not rooted so I rooted it and put twrp and KatKiss - Nougatella #023 on it but shortly after it became a issue(terrible lag and wouldn't download anything from the store) so I downgraded to KatKiss - KatshMallow #029 and have been good ever since.(except for the little lag)
My question is I just got a used and rooted tf701 today and am about to put a system on it but after my first tf701 and tf700 issues I'm worried about putting KatKiss - Nougatella #022(I don't think the rom was the issue but) on so should I be worried and put on KatKiss - KatshMallow #033 or should I be alright with KatKiss - Nougatella #022?(I just don't want a repeat so I have two none usable tablets)
Thanks in advance for any suggestions.
I've been running Katshmallow on it for months without a problem
berndblb said:
I've been running Katshmallow on it for months without a problem
Click to expand...
Click to collapse
Ok I will go with that then thanks.
I have had issues with my zenwatch 3 being crazy slow on android wear 2.0, and i read some possible solutions..
I also have an issue where whenever i turn my watch on it says "device software cannot be checked for corruption" and it makes it take an additional 10-15 seconds to boot up. This has been on the watch since i got it (i bought used and the bootloader was already unlocked, if thats why its doing that. When going through forums I also saw mention for disabling dm verity and wondered if that would get rid of that annoying screen.
I wanted to see if i could remove the zenfit stuff, cause i saw that some users claimed speed improvements, so i flashed twrp, and when i booted in i accidentally said to allow modifications (even though now i see that people say not too). I didnt make any changes while in here, but thought that might be important to state. In the instructions to remove zenfit i again saw to disable dm verity, so i moved onto that.
I then connected through adb and ran the command fastboot oem disable_dm_verity, but that didnt seem to do anything. I then ran the command "adb reboot "dm-verity enforcing" which i dont think was a good one to run, and i wonder if caused my issue. When i tried to boot back into twrp it would boot to a dead android.
I decided at this point that instead of screwing things up further, i would just flash to AW 1.5 and hope for speed improvement there. I downloaded the files, and through fastboot flashed the stock 1.5 boot, system, and recovery. using this thread https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
i rebooted the device and it went to the android wear screen and loaded for a while, and then to the upgrading android screen. when it got to step 7 it went back to the aw loading animation and then attempted to boot up and gave an error "unfortunately process android.process.acore has stopped" and started all over again trying to upgrade android and then getting to this point and failing. I then downloaded the images for stock 2.0 and flashed and got the same exact error.
I then tried to flash twrp again, and now if i try to flash 1.5 or 2.0 it just goes to a dead android screen. I can boot into twrp still with the boot adb command
I want to try flashing 1.5 or 2.0 through trwp, but my watch will not mount/connect at mtp to my PC while at twrp for some reason...
Any ideas or solutions? how can i flash everything straight back to default. Including whatever i may have done to the dm verity?
Please help
If ADB and Fastboot is working on your watch, try this
csrow said:
If ADB and Fastboot is working on your watch, try this
Click to expand...
Click to collapse
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Coltonbyu said:
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Click to expand...
Click to collapse
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
csrow said:
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
Click to expand...
Click to collapse
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Coltonbyu said:
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Click to expand...
Click to collapse
Glad it worked out.
If you want to stay at 1.5, you know what to do.