Related
Well, i tried to root my TF300t today, from 4.2.1 official ROM.
I installed TWRP 2.5.0.0 then 2.6.3.0 as well as some root files. Then i installed this rom,with the root file included as well as 2.6.3.1 TWPR.
I entered the OS, but i could not get WIFI.Then i rebooted to TWPR and since then i cannot do anything.
Firstly, TWPR asks me for some password which i have no clue what kind of pass it might be.
Then i pressed back, and i entered the TWPR menu, where i found out that i don't have access to and kind of memory.Neither internal or external SD as well as i can't log into OS.
Also, when i tried to do some wipes, i could not wipe dalvik cache.
When i go to restart to OS from TWPR, i get a message "No OS Installed! Are you sure you wish to power off?" message.
Also, i get this message: "Install SuperSU? your device does not apear to be rooted. Install SuperSU now?This will root your device"
This is doing absolutely nothing.It does not instal Root.
UPDATE: Ok.I managed to get ext SD card to be mounted.In ext sd card i have some android 4.4 (see above which version on the link) but i am unable to instal it.
Error Message : "Unable to open zip file."
When i try to instal root i get a Success Message but it keeps saying to me that no root installed.
Any idea what is wrong?
Probably the version of your bootloader does not match the version of TWRP you installed.
Can you get to the bootloader screen to check the exact version number on the top-left?
Sent from my TF300T using Tapatalk
f69m said:
Probably the version of your bootloader does not match the version of TWRP you installed.
Can you get to the bootloader screen to check the exact version number on the top-left?
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Bootloader screen has these:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
TheoKondak said:
Bootloader screen has these:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
Click to expand...
Click to collapse
OK, that is the latest version.
Did you pick the TWRP with -42 in the name or scanno's version from the OmniROM thread?
The latter should be used for 4.4-based (kitkat) ROMs.
Neither the -ics nor the -jb versions work with your bootloader.
Sent from my TF300T using Tapatalk
f69m said:
OK, that is the latest version.
Did you pick the TWRP with -42 in the name or scanno's version from the OmniROM thread?
The latter should be used for 4.4-based (kitkat) ROMs.
Neither the -ics nor the -jb versions work with your bootloader.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
I used the 4.4-based TWPR.
Well, i think that the problem occured when i cleared the System Data.Now system data shows 0mb (Internal Storage (0mb) ).Also, if i try to wipe System or data or internal storage i keep geting a "failed" message.
E: Unable to wipe '/data' probably because i don't have access to it.
You need to reboot fully into android after flashing recovery. That's why twrp doesn't work and asks for password when u don't.
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4
I loged into Android, but could not get Wifi to start, so i rebooted into TWPR and did a system wipe and i believe that that caused all the problems.
So right now,i don't have an OS to load into.What should i do to get out of this situation?
TheoKondak said:
I loged into Android, but could not get Wifi to start, so i rebooted into TWPR and did a system wipe and i believe that that caused all the problems.
So right now,i don't have an OS to load into.What should i do to get out of this situation?
Click to expand...
Click to collapse
Thats a ME301 ROM you linked too. Did you mean the tf300t version of it?
TheoKondak said:
I loged into Android, but could not get Wifi to start, so i rebooted into TWPR and did a system wipe and i believe that that caused all the problems.
So right now,i don't have an OS to load into.What should i do to get out of this situation?
Click to expand...
Click to collapse
Try erasing most partitions via fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot erase misc
fastboot erase recovery
Then reflash TWRP and try again.
Somewhere in the threads is a list of all partitions you can erase, but above list should be a good start.
EDIT: Instead of flashing TWRP, you might first flash Asus ROM via fastboot and boot that.
Then reflash TWRP, wipe and flash custom ROM.
Sent from my TF300T using Tapatalk
Thank you very much.
I did wipe all these couple of times.Some of them deny access or there are no data at all to delete so i get a failed message.
So, let me sum what i have to do.
1. Install Stock Asus 4.1.1 http://forum.xda-developers.com/showthread.php?t=1893714
2.Install a new TWRP openrecovery-twrp-2.6.3.0-tf300t-ICS.blob
3. Go in TWRP do a data wipe, cache wipe
4.Flash a new custom rom.
5. Flash latest TWRP.
Please confirm that these are the correct steps.I got chills after this adventure!Even though i am familiar with android rooting and ROM flashing, TF300t seems to be a whole new chapter.
TheoKondak said:
Thank you very much.
I did wipe all these couple of times.Some of them deny access or there are no data at all to delete so i get a failed message.
So, let me sum what i have to do.
1. Install Stock Asus 4.1.1 http://forum.xda-developers.com/showthread.php?t=1893714
2.Install a new TWRP openrecovery-twrp-2.6.3.0-tf300t-ICS.blob
3. Go in TWRP do a data wipe, cache wipe
4.Flash a new custom rom.
5. Flash latest TWRP.
Please confirm that these are the correct steps.I got chills after this adventure!Even though i am familiar with android rooting and ROM flashing, TF300t seems to be a whole new chapter.
Click to expand...
Click to collapse
Yeah, thanks to Asus for all those incompatible bootloader versions.
Those steps look basically right to me, just some remarks:
Pick the latest Asus ROM 10.6.1.27.5. If you don't find it in the tread, download from Asus web site.
According to your bootloade version, make sure it is the "WW" version (not "US" or "JP", etc.).
After step one, before flashing TWRP, actually boot into the Asus ROM once.
Step 5 should not be necessary, as flashing a custom ROM should leave your recovery untouched.
Sent from my TF300T using Tapatalk
Well!I am happy to anounce that i am in my 4.4.2 ROM!Not sure if this is the best Kitkat outhere, but at least my device is not bricked!Thanks all for the help!
I followed the sequence of moves as i posted it above!Thanks everyone for helping!
During normal use of the Asus it will freeze. The screen stays frozen until I shut down the tablet manually. When I start the tablet again it boots up and works normally but it is only a matter of time before it freezes again.
I have tried to cold boot it but all that happens is I hold the volume and power buttons down it vibrates but the screen just stays black and there seems to be no affect.
I have limited knowledge with these kind of things but any help is greatly appreciated, thank you in advance.
What's your situation?
Are you on stock? Which version?
Rooted?
Custom rom/recovery? Which one?
If you're on stock it seems to be time for a factory restore from Settings.
Backup everything you care about off the tablet (you can use Asus Backup for this), then go to Settings > Backup & reset and reset the tablet.
Reboot and restore the backup. If you get the same behaviour, do the factory reset again but install your apps a few at a time from the Play Store and test the tablet in between. One of them could be the culprit.
berndblb said:
What's your situation?
Are you on stock? Which version?
Rooted?
Custom rom/recovery? Which one?
If you're on stock it seems to be time for a factory restore from Settings.
Backup everything you care about off the tablet (you can use Asus Backup for this), then go to Settings > Backup & reset and reset the tablet.
Reboot and restore the backup. If you get the same behaviour, do the factory reset again but install your apps a few at a time from the Play Store and test the tablet in between. One of them could be the culprit.
Click to expand...
Click to collapse
It is running android 4.2.1.
Yes it is rooted.
It is a custom recovery. The Recovery is Team Win Recovery Project v2.7.1.1
The Kernel Version is 3.1.10-03bcdcb1 [email protected]#1 Fri Mar 29 17:0432 CST 2013
The Build is JO4OD.WW_epad-10.6.1.14.4-20130329660
I have successfully done the factory reset but it froze in the setup area. I did eventually manage to get through but it still freezes as usual.
Kaij said:
It is running android 4.2.1.
Yes it is rooted.
It is a custom recovery. The Recovery is Team Win Recovery Project v2.7.1.1
The Kernel Version is 3.1.10-03bcdcb1 [email protected]#1 Fri Mar 29 17:0432 CST 2013
The Build is JO4OD.WW_epad-10.6.1.14.4-20130329660
I have successfully done the factory reset but it froze in the setup area. I did eventually manage to get through but it still freezes as usual.
Click to expand...
Click to collapse
Should have elaborated I guess....
Do not do that factory reset from Settings or the bootloader again with a custom recovery installed! You can end up in a nasty forced reboot to recovery loop...
Ok, you are on a current recovery, your bootloader is up to date enough for JB based roms but I would not try to run KitKat roms on it.
Did you ever run a custom rom? Just to confirm your bootloader version, boot with Power and Volume Down buttons and read the tiny script.
That's the only sure way to determine your bootloader version.
If you are on 10.6.1.14.4 you can head over to the Development section and download CROMi-X 5.4.
Boot to TWRP, choose Wipe and just swipe the button to prepare your tablet for a clean installation of CROMi-X.
Once that is done flash CROMi-X 5.4 in TWRP.
If you want to run a KitKat based rom you should update your bootloader first.
berndblb said:
Should have elaborated I guess....
Do not do that factory reset from Settings or the bootloader again with a custom recovery installed! You can end up in a nasty forced reboot to recovery loop...
Ok, you are on a current recovery, your bootloader is up to date enough for JB based roms but I would not try to run KitKat roms on it.
Did you ever run a custom rom? Just to confirm your bootloader version, boot with Power and Volume Down buttons and read the tiny script.
That's the only sure way to determine your bootloader version.
If you are on 10.6.1.14.4 you can head over to the Development section and download CROMi-X 5.4.
Boot to TWRP, choose Wipe and just swipe the button to prepare your tablet for a clean installation of CROMi-X.
Once that is done flash CROMi-X 5.4 in TWRP.
If you want to run a KitKat based rom you should update your bootloader first.
Click to expand...
Click to collapse
[/CODE]
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
[/CODE]
This is what it says in the boot loader screen.
I have wiped the stock ROM through TWRP and installed Chromi-X 5.4.
Once I boot into android the screen freezes after a short while in setup.
Kaij said:
[/CODE]
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
[/CODE]
This is what it says in the boot loader screen.
I have wiped the stock ROM through TWRP and installed Chromi-X 5.4.
Once I boot into android the screen freezes after a short while in setup.
Click to expand...
Click to collapse
I think it would be worth you flashing the bootloader and twrp package in the first post of CROMi-X Reboot once after then flash the rom again.
Hello,
My TF700T is pretty laggy and I'm trying to workout if there's something under the covers that I can remedy.
Looking through the logcat (as attached), I can see some disturbing recurring items that might be contributing to these issues:
Failed on audit_set_pid with error: Protocol not supported
Caused by: libcore.io.ErrnoException: connect failed: ECONNREFUSED (Connection refused)
I'm on TWRP v2.8.0.1, and believe that I'm on BL 10.6.1.14.10 (based on the contents of device_info.txt).
Looking at the following, it's suggested to update the bootloader:
http://forum.xda-developers.com/showthread.php?t=2668805
However looking at the following it seems as though I have the most recent version of the BL?
http://forum.xda-developers.com/showthread.php?t=2425383
Can anyone advise help point me in the right direction? Apologies for the newb questions, I'm just getting nowhere fast!
You find your bootloader version on the bootloader menu screen (Power and Volume Down) and you seem to be on the latest 10.6.1.14.10.
When's the last time you did a clean install?
I would do a factory wipe in TWRP and reflash the rom.
You can restore your apps from a TiBu backup, but should not restore any system settings.
Also backup your launcher and restore it after the flash and you shoud be minutes away from your ususal setup.
2257
Hmmm ... I tried a TWRP Factory Reset and installed cm-11.0-20140403-CROMBikk4.4.2-tf700t_Signed.zip that I already had ready to go, and it is now hanging on the CROMBi-KK prompt when I reboot (stuck for at least half an hour). Have downloaded cm-11.0-20140921-tf700t-crombi-kk-R1_signed.zip and will try to install this, hopefully this resolves.
Ok, I'm back up with the latest Crombi-KK goodness, but the system is still pretty laggy and there are still some disconcerting logcat messages as below. Any suggestions on how to resolve?
Sent from my GT-I9505 using Tapatalk
Sorry, adding attachment, link was rejected when I tried posting from device.
RedDemon said:
Ok, I'm back up with the latest Crombi-KK goodness, but the system is still pretty laggy and there are still some disconcerting logcat messages as below. Any suggestions on how to resolve?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Did you check you bootloader version by booting into it?
berndblb said:
Did you check you bootloader version by booting into it?
Click to expand...
Click to collapse
Looks like you may be on to something, bootloader displays the following. I'm assuming it needs updating based on this output? If so, what is recommended?
Key driver not found ... Booting OS
Android cardhu-user bootloader <1.00e> released by "WW-epad-10.6.1.14.4-20130329" A03
Starting USB fastboot USB download protocol
The following message has also appeared a couple of times. Have select "I'm Feeling Lucky" both times, I wonder what's causing this and if there's a more permanent fix?
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
RedDemon said:
Looks like you may be on to something, bootloader displays the following. I'm assuming it needs updating based on this output? If so, what is recommended?
Key driver not found ... Booting OS
Android cardhu-user bootloader released by "WW-epad-10.6.1.14.4-20130329" A03
Starting USB fastboot USB download protocol
The following message has also appeared a couple of times. Have select "I'm Feeling Lucky" both times, I wonder what's causing this and if there's a more permanent fix?
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
Click to expand...
Click to collapse
Yep, your bootloader is just a touch too old. The .4 boots the KK rom, but it doesn't seem to run it well.
Head over to the CROMi-X 5.4 thread in the Development section. Scroll down in the OP until you see the 10.6.1.14.10 bootloader/TWRP package and download it.
Flash that package in your current TWRP and reboot.
Then boot to recovery and check the version. sbdags kind of promised just yesterday to update the package to include TWRP 2.8.0.1, and lj kind of promised to take care of it also. But I don't know if they did already - there was a lot of banter about "lazy bastards" going back and forth [emoji12]
If you see that you got TWRP 2.6.0.1 after the package flash, just flash 2.8.0.1 in fastboot and you should have no further trouble.
I don't think you will see the inconsistent system UI message again, but if you do, clean install CROMBi again.
BTW, where did you get that 'device info' file? I suspect it pulled the bootloader version from Software Information > Build Number. The only way to really tell your bootloader version running custom software is from the bootloader screen.
berndblb said:
Yep, your bootloader is just a touch too old. The .4 boots the KK rom, but it doesn't seem to run it well.
Head over to the CROMi-X 5.4 thread in the Development section. Scroll down in the OP until you see the 10.6.1.14.10 bootloader/TWRP package and download it.
Flash that package in your current TWRP and reboot.
Then boot to recovery and check the version. sbdags kind of promised just yesterday to update the package to include TWRP 2.8.0.1, and lj kind of promised to take care of it also. But I don't know if they did already - there was a lot of banter about "lazy bastards" going back and forth [emoji12]
If you see that you got TWRP 2.6.0.1 after the package flash, just flash 2.8.0.1 in fastboot and you should have no further trouble.
I don't think you will see the inconsistent system UI message again, but if you do, clean install CROMBi again.
BTW, where did you get that 'device info' file? I suspect it pulled the bootloader version from Software Information > Build Number. The only way to really tell your bootloader version running custom software is from the bootloader screen.
Click to expand...
Click to collapse
Lol ... love the banter, on the contrary, you guys are doing a stellar job helping others make the most of their devices, keep up the great work!
Thanks heaps ... have uploaded the bootloader to 10.6.1.14.10 using the following:
http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
The bootloader now says "Android cardhu-user bootloader <1.00 e> released by "WW-epad-10.6.1.14.10-20130801" A03", so looks like I'm on the right version now.
However, even after installing the same CROMBikk zip, I can't boot into the OS anymore (have tried a few installations to no avail).
Instead, I get the following (not sure if this is a problem or just a new feature of the latest bootloader), after which always returns to TWRP:
[4.xxxxxx] preinit ######### starting #########
Detecting filesystems...
mmcblk0p8 /data on internal (UDA) -> ext4
mmcblk1p2 /data on microSD (for Data2SD/ROM2SD) -> not present
mmcblk1p3 /system on microsSD (for ROM2SD) -> not present
4.xxxxx fm34: [fm34_config_DSP] DSP ACK, read 0xc0:1
4.xxxxx fm34: [fm34_config_DSP] Load TF700T DSP parameters
After this it reboots and enters TWRP.
Am I doing something wrong? Have I missed anything? Are there any additional steps I need to follow to ensure the integrity of the install?
It has also reverted back to TWRP v2.6.1.0 which you'd preempted, and in the past I've usually used the ADB / Terminal method to install TWRP to my device. However, given that I can't boot into my device, I can't do that anymore. So I've entered "Fastboot USB download protocol", and I have the option of "RCK", "Android" or "Wipe Data". I can't see any options to "select the usb icon and hit volume up to confirm" as per http://teamw.in/project/twrp2/105, and I can't even see the device anymore from the PC fastload utility. If I can get the OS up and running this wouldn't be such an issue, and I'd simply use the "ADB / Terminal method" as I have in the past.
I note that after the install, I get the following prompt in TWRP which I haven't seen before. Doesn't seem to matter if I opt to fix or not, I still can't boot into the OS.
Fix Superuser Permissions?
Root permissions appear to be lost.
Fix root permissions now?
(Fixes permissions on su binary and app)
BTW, where did you get that 'device info' file? I suspect it pulled the bootloader version from Software Information > Build Number. The only way to really tell your bootloader version running custom software is from the bootloader screen.
Click to expand...
Click to collapse
The device info file was created by CatLog, it seemed like the easiest way to determine the bootloader, but in retrospect it was inaccurate. Lesson learnt!
Mhhh, so you flashed CROMBi-KK with TWRP 2.6.0.1?
That might be the problem here.
The Teamwin instructions are a little outdated. You are in fastbot mode when you are on the screen with the 3 icons.
If you need more instructions on flashing the recovery in fastboot, check this guide:
http://forum.xda-developers.com/showthread.php?t=2688891
Thanks, great post. I'll use it to do some further troubleshooting and let you know how it goes
Sent from my GT-I9505 using Tapatalk
berndblb said:
Mhhh, so you flashed CROMBi-KK with TWRP 2.6.0.1?
That might be the problem here.
The Teamwin instructions are a little outdated. You are in fastbot mode when you are on the screen with the 3 icons.
If you need more instructions on flashing the recovery in fastboot, check this guide:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
You're spot on again, after upgrading to TWRP 2.8.0.1 and reflashing the ROM, all is well in the world again (OK, at least on my tablet), doing a TiBU restore as we speak!
Thanks again for a fantastic guide. Tried a number of things despairingly and as a last gasp tried connecting the cable to another USB port. They're both USB 2.0 and both work fine for everything else so can't see why it would be an issue, but in the new USB port it works a charm. Thanks again so much, highly appreciated!
In my excitement of having resurrected my tablet, I didn't really comment on the end goal, which was to improve tablet efficiency and remove/reduce lag. Happy after playing around for a couple of days that things are much smoother with the latest bootloader and ROM. I can still see "Failed on audit_set_pid with error: Protocol not supported" frequently occur in the catlog, but I guess if the tablet is otherwise functioning well it isn't an issue. Thanks again for your help.
The ROM did unfortunately corrupt itself overnight when the device ran out of battery and it kept hanging on the Crombi-KK splash screen. After trying a few things I reflashed the ROM and restored again. A bit annoying, but not sure how it could be avoided (other than keeping it charged in like I'd usually do, although I'd like to think that things wouldn't so easily be corrupted).
The 5.1 OTA didn't work for me besides removing all the usual stuff that might get in the way.
So i decided to just flash the factory image from: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
All flashs came back okay, but after rebooting I got stuck on the 'Bootloader unlocked' screen.
Tried downgrading to 5.02 again but it only displayed the android figure on it's back with the error sign.
I can still access the bootloader but i'm not sure what the best way to deal with this is now.
Any suggestions would be greatly appreciated!
AntiDisco said:
The 5.1 OTA didn't work for me besides removing all the usual stuff that might get in the way.
So i decided to just flash the factory image from: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
All flashs came back okay, but after rebooting I got stuck on the 'Bootloader unlocked' screen.
Tried downgrading to 5.02 again but it only displayed the android figure on it's back with the error sign.
I can still access the bootloader but i'm not sure what the best way to deal with this is now.
Any suggestions would be greatly appreciated!
Click to expand...
Click to collapse
Probably you didn't flash system.img_sparsechunk0. Or maybe you flashed the system files with dots when they are named without dots, or viceversa. (i.e. flashing system.img_sparsechunk1 when the name is system.img_sparsechunk.1)
I'm pretty sure I did this part right, because I first forgot the dot and got an error message. Flashed parts 0-3, that's all there were.
In the meantime I flashed TWRP recovery and it says no OS installed. If I try to wipe the different partitions I get 'failed to mount system' and the same for the cache.
AntiDisco said:
I'm pretty sure I did this part right, because I first forgot the dot and got an error message. Flashed parts 0-3, that's all there were.
In the meantime I flashed TWRP recovery and it says no OS installed. If I try to wipe the different partitions I get 'failed to mount system' and the same for the cache.
Click to expand...
Click to collapse
Can you copy here all that you write and all that the console returns while flashing the firmware?
I feel real stupid right now. I used fastboot and not mfastboot.
Took a few hours to remember there is actually a reason why you have to use mfastboot.
Thanks for your help nevertheless.
Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?