Database Info

Question about instaling CM10

Ive looked around the internet, and here, and cant really figure something out. Do I have to install CM10 from fastboot or can I just install the zip using TWRP?
I ask because I tried installing the stable version of CM10 using TWRP and when I reboot I just get the spinning Cyanogenmod logo for a long time. Nothing ever happens.
Am I doing something wrong?

Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app

area51avenger said:
Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot. I will do that right now. Appreciate the help.
Is flashimagegui an android app? Thats the only reference to it I can find.

Yes it is. There is a donation version on play store. Or there's an xda free version if you search the forums
Sent from my HTC One XL using xda app-developers app

Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?

JohnnyDanger said:
Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?
Click to expand...
Click to collapse
what version of hboot is on your device? if it is one of the later ones (1.12+) then you'll need to flash the boot img seperately. If this is the case, (and it sounds like it , as the same thing happened to me and the symptoms where the same).
Extract it from the ROM that you are flashing (open the zip file and drag out the boot.img). Then while TWRP is running, connect the USB cable to your comp and fire up a terminal (you'll need ADB/fastboot set up and working - search google or XDA for how to do it in your operating system).
Once you have adb/fastboot working and TWRP running -> at a terminal (or command prompt on windows) use adb to push the rom onto the sdcard, and then reboot to bootloader and select fastboot.
run "fastboot flash boot boot.img" without the quotes. This should write the kernel image to the boot partition, and then you should be able to load TWRP to (wipe cache/dalvik and then) reflash cyanogen mod.
Good luck

If you can still boot into recovery, you're fine. Manually flash the CM10 boot.img with fastboot, do a full wipe in TWRP and then reinstall the CM10 zip + gapps. Should be good after that.

Thanks for the info, from both of you. Im going to try that right now.

Im trying to flash the boot.img file, but I keep getting an error. Any ideas?
Heres what I get
C:\adt-bundle-windows\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (5248 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse

did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.

codeprimate said:
did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.
Click to expand...
Click to collapse
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.

JohnnyDanger said:
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.
Click to expand...
Click to collapse
can you get into TWRP? if you can, go to the mount menu and see if you can unmount and then remount the sdcard. If you can do this, then you have no need to do the team-nocturnal sdcard fix.

I was able to unmount and then remount the sdcard. Actually, when I went into Mount menu in TWRP to begin with it gave me the option to Mount, then unmount. Is that the same thing? Does that mean my sdcard is not mounted and should I mount it in TWRP?

I was finally able to flash the boot.img. I then went into TWRP to install CM10. It installed and now is back into the spinning logo. Im ready to give up on this. Any more suggestions?
Just a thought, should I be removing the boot.img from the CM10 zip Im trying to install?

No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app

area51avenger said:
No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.

JohnnyDanger said:
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.
Click to expand...
Click to collapse
No worries man, good luck with your One X, I hope the worst is behind you now.
If you are feeling confident, there is a method to downgrade your hboot so you don't need to stuff around flashing the boot image separately. This however does involve bricking and then de-bricking your device, and you'll need a linux computer to pull it off, so this isn't for everyone.

Phone won't boot...need help quick!

I was running CarbonROM and wanted to try out a TW ROM. I booted into my recovery (TWRP), backed up Carbon, went to wipe options, did a Factory Reset, pushed the button to wipe system, it started but after a couple seconds the phone rebooted. I try boot back into recovery by holding down the power, VOL up, and home button. I get the "Samsung" splash screen and it says "recovery booting....", then the TWRP screen will show for a couple seconds, then my phone will reboot. I can't boot into the phone because I did a factory reset.
So I can't get into the phone and only get the start screen for TWRP but can't actually get into TWRP. Any help?

I found out I can boot into download mode. I should be able to find a stock rooted image there, right? Not sure how to do that though.

Had the same problem a little while back.
It;s been a few weeks since this happened to me so it's a little hazy so bear with me.
You are going to want to use ODIN to flash a rom with root, and once you get that you are going to want to reinstall a recovery pronto. (I suggest EZ-recovery 1.2)
A quick search will give you a few tutorials, just basically start like you are coming from a stock firmware and are rooting through ODIN.
Hope this helps!

schmaltzy said:
I found out I can boot into download mode. I should be able to find a stock rooted image there, right? Not sure how to do that though.
Click to expand...
Click to collapse
It sounds like you TWRP might be broken. I'd try Odin first and pda push the newest TWRP again. If That fails then I'd push the newest CWM in Odin and see if that works. After getting CWMI to boot if you want to go back to TWRP again, pda it over thru Odin. If these fail then push a stock ROM from Odin and start all over again.
Sent from my SCH-I535 using Tapatalk HD

Sounds like a soft brick I did once too. I believe what I did was use Odin to go back to factory defaults, then I rerooted my phone
Sent from my SCH-I535 using Tapatalk 4 Beta
---------- Post added at 05:13 PM ---------- Previous post was at 05:08 PM ----------
Try googling "boot looping"
Sent from my SCH-I535 using Tapatalk 4 Beta

[Q] TF700 bricked...?

Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!

Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??

lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo

nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??

lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?

nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/

lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!

Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app

lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays

So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?

First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.

berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery

Hope this worked

s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???

berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?

s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.

OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.

s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?

The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it

s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !
I recently rooted my Motorola Moto G3 and it worked.... ish, when I opened my phone from it being turned off I was greeted with the message telling me that it was super duper dangerous to root your phone and I could damage my phone, that normally goes as it is just a mandatory thing that they have to say, I waited for a while and it didn't go, I waited for a day and it didn't go. So I let it run out of charge and tried to boot it again, this didn't work, I was still seeing the same white screen with red and black writing. I then let it run out of charge and open it in fast boot mode by pressing the power button and volume down, this did work and from there I have managed to open the team win recovery project but whenever I do anything from then, it will go back to the error page and then will never load. I have even reset the phone to factory settings. If I hold the power button it will turn off the phone but very shortly after automatically turn itself back on to this same image.... please help!

How did you end up rooting it? Have you tried flashing a factory image?

If I were you, I would try to reflash stock firmware with factory reset

@Artyb52
hi, what did you do to Root ??
check these , if you have done evrything :
1) USB debugging enabled, allow OEM unlocking Enable ( developer options )
2) install ADB and fastboot. ( in PC)
3) Unlock bootloader in Fastboot mode .. (After unlocking did you PowerOn your phone, and check ? did it ON with out any problems? )
4) Installing a recovery , by following proper commands and choosing right version ..
5) flashing SuperSU with that Recovery.
If you have done everything Right, then Do onething.. Change CustomRecovery Version ( if on TWRP ) ,
else Goto Fastboot.. press POWER OFF, so that your phone gets SHUT DOWN, then On it normally ..
i have seen a problem where REBOOT function causes Bootloops..

i tried that and it didnt work :/
@nandakis4 shame it didn't work. Do you have any other tips, I would be really grateful

@Acetyloaceton how do you do that ? sorry for sounding like such a noob, i'm new to the game

l3ones said:
How did you end up rooting it? Have you tried flashing a factory image?
Click to expand...
Click to collapse
@13ones I tried flashing the TWRP image, is that different to the factory image ?

The same thing happened me when I rooted my phone. To fix it I downloaded cm 13 then placed it on internal storage and flashed it (and gapps) from twrp and it worked fine.

Acetyloaceton said:
If I were you, I would try to reflash stock firmware with factory reset
Click to expand...
Click to collapse
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Artyb52 said:
@13ones I tried flashing the TWRP image, is that different to the factory image ?
Click to expand...
Click to collapse
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.

l3ones said:
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.
Click to expand...
Click to collapse
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this

Try this
Using adb sideload on twrp
1. Flash supersu 2.62, then
2. Flash supersu 2.65
Command : adb sideload supersu.xx.zip
In my case, it works.

Artyb52 said:
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this
Click to expand...
Click to collapse
If I'm not too late, sure. What model do you have?

Help! OP6 stuck in 'the boot loader is unlock and software... etc' screen!

So i tried flashing blu-spark twrp.. and magisk up until the moment i had to reboot after installing magisk... now the phone is stuck in this screen i dont know what do, help

What screen? Pictures would help others give feedback and information to assist you. I have yet to update to Android Pie because I am waiting for an official TWRP release myself and I like to gather as much information as I can before I make a leap into the next update

dgunn said:
What screen? Pictures would help others give feedback and information to assist you. I have yet to update to Android Pie because I am waiting for an official TWRP release myself and I like to gather as much information as I can before I make a leap into the next update
Click to expand...
Click to collapse
thanks, sorry dont have another phone to take a picture of this but its basically the screen we get when first booting that shows the device has an unlocked bootloader... the 'warning screen'
edit: **** the link was wrong
edit2: this one but in our device http://i.imgur.com/88NcI2K.jpg

+1 same procedure and same problem.
No connection to PC possible and no "reset-buttons" work.
---------- Post added at 11:18 AM ---------- Previous post was at 10:52 AM ----------
Okay, I managed to get my phone booting up again.
1. Turn off phone by holding just the power-button
2. Boot phone into fastboot-mode by holding vol-up and power-button
3. In Fastboot-mode connect phone to pc
4. get stock OxygenOS-boot.img (Stock boot-recovery images) from here
5. flash the boot.img via fastboot: "fastboot flash boot stockboot.img"
After that my phone booted up again. TWRP is removed through that procedure. I will wait a while before testing it again.

Got the same as you. Booted back into Blu Spark TWRP, wiped Dalvik and cache and then selected the other boot partition. Booted up for me.

lal000r said:
+1 same procedure and same problem.
No connection to PC possible and no "reset-buttons" work.
---------- Post added at 11:18 AM ---------- Previous post was at 10:52 AM ----------
Okay, I managed to get my phone booting up again.
1. Turn off phone by holding just the power-button
2. Boot phone into fastboot-mode by holding vol-up and power-button
3. In Fastboot-mode connect phone to pc
4. get stock OxygenOS-boot.img (Stock boot-recovery images) from here
5. flash the boot.img via fastboot: "fastboot flash boot stockboot.img"
After that my phone booted up again. TWRP is removed through that procedure. I will wait a while before testing it again.
Click to expand...
Click to collapse
Did this wipe anything when you flashed the stockboot.img? Just data or internal too?
ptoner said:
Got the same as you. Booted back into Blu Spark TWRP, wiped Dalvik and cache and then selected the other boot partition. Booted up for me.
Click to expand...
Click to collapse
Sorry, can you clarify your last bit about selecting the other boot?

habylab said:
Did this wipe anything when you flashed the stockboot.img? Just data or internal too?
Nothing was wiped. All data remain in place.
Click to expand...
Click to collapse