Hello
I'm not sure if i bricked my tablet or not...i've spent the last 4hrs googling and surfing looking for answers but i can't seem to find anything definitive. Here's what i did
1) Was on CM10.1 nightlies and wanted to update to the newest ones on the JB Bootloader
2) downloaded all the necessary files (stock Asus, twrp2.5-42 and newest CM nightly)
3) went to go into recovery but accidentally hit Wipe Data (no idea how i managed that one)
4) tablet was wiped and rebooted into a fresh from the box Android install
5) went back into recovery and wiped data/cache and flashed stock Asus
6) rebooted and it hung at the Asus "loading screen"
I still have fastboot and recovery access...i fastbooted twrp 2.5-42 recovery on to the device and can flash roms they just don't boot
Is there a fix for the this or am i screwed...i should also point out when i go into the bootloader menu at the top it says "key driver not found.. Booting OS" before it tells me the bootloader and starting fastboot
Any help is appreciated
moosehead11 said:
Hello
I'm not sure if i bricked my tablet or not...i've spent the last 4hrs googling and surfing looking for answers but i can't seem to find anything definitive. Here's what i did
1) Was on CM10.1 nightlies and wanted to update to the newest ones on the JB Bootloader
2) downloaded all the necessary files (stock Asus, twrp2.5-42 and newest CM nightly)
3) went to go into recovery but accidentally hit Wipe Data (no idea how i managed that one)
4) tablet was wiped and rebooted into a fresh from the box Android install
5) went back into recovery and wiped data/cache and flashed stock Asus
6) rebooted and it hung at the Asus "loading screen"
I still have fastboot and recovery access...i fastbooted twrp 2.5-42 recovery on to the device and can flash roms they just don't boot
Is there a fix for the this or am i screwed...i should also point out when i go into the bootloader menu at the top it says "key driver not found.. Booting OS" before it tells me the bootloader and starting fastboot
Any help is appreciated
Click to expand...
Click to collapse
This is a link if you want more explenation! : http://forum.xda-developers.com/showthread.php?p=39272826
go to the stock asus site and download firmware for your sku
extract the zip in the zip flash the "blob" file to your tablet
reboot your bootloader
flash twrp 2.5.0.0 -4.2
that zip you extracted from that download? put it on your device and flash it
this should work!
about the "key driver not found.. Booting OS" it's normal everyone has it!
Sent from my Transformer Pad TF300T using xda app-developers app
noahvt said:
This is a link if you want more explenation! : http://forum.xda-developers.com/showthread.php?p=39272826
go to the stock asus site and download firmware for your sku
extract the zip in the zip flash the "blob" file to your tablet
reboot your bootloader
flash twrp 2.5.0.0 -4.2
that zip you extracted from that download? put it on your device and flash it
this should work!
about the "key driver not found.. Booting OS" it's normal everyone has it!
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I've tried flashing stock Asus a few different times either form fastboot, twrp or sideload none seem to work...given i can't boot should i be worried if i decided to wipe data, format system or just doing a factory reset before trying again
What error does it give when you try to flash?
Sent from my sensational HTC Desire C
noahvt said:
What error does it give when you try to flash?
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
no errors...i flash the ROM (in either TWRP or fastboot) and reboot...after the reboot i get to the ASUS "boot screen" (the one with the spinning circle under the Asus Logo) and it hangs there...have left it there "loading" for 30 minutes and nothing
scared of bootloader/fasboot access...can i wipe data/cache, format system and try again...would factory resetting in TWRP help maybe?
moosehead11 said:
no errors...i flash the ROM (in either TWRP or fastboot) and reboot...after the reboot i get to the ASUS "boot screen" (the one with the spinning circle under the Asus Logo) and it hangs there...have left it there "loading" for 30 minutes and nothing
scared of bootloader/fasboot access...can i wipe data/cache, format system and try again...would factory resetting in TWRP help maybe?
Click to expand...
Click to collapse
you forgot somethink (i think) after you have flashed it via fastboot you have to flash twrp 2.5.0.0 -4.2 then reboot bootloader then go to twrp and wipe everything! then flash via twrp!
Sent from my Transformer Pad TF300T using xda app-developers app
noahvt said:
you forgot somethink (i think) after you have flashed it via fastboot you have to flash twrp 2.5.0.0 -4.2 then reboot bootloader then go to twrp and wipe everything! then flash via twrp!
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
So flash the rom and twrp via fastboot and then reboot bootloader...then in twrp install cm?
I thought you needed to let the rom fully boot before adding the recovery so the new bootloader gets installed properly
Sent from my GT-I9000 using xda app-developers app
moosehead11 said:
So flash the rom and twrp via fastboot and then reboot bootloader...then in twrp install cm?
I thought you needed to let the rom fully boot before adding the recovery so the new bootloader gets installed properly
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Flash blob file from fastboot
Type fastboot reboot bootloader
Flash twrp
Type fastboot reboot bootloader again
Launch twrp and wipe /system /data etc
In twrp flash the zip where the blob was in
Reboot
That's how I did it! I downgraded and upgraded
Sent from my sensational HTC Desire C
noahvt said:
Flash blob file from fastboot
Type fastboot reboot bootloader
Flash twrp
Type fastboot reboot bootloader again
Launch twrp and wipe /system /data etc
In twrp flash the zip where the blob was in
Reboot
That's how I did it! I downgraded and upgraded
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
So you are flashing the stock asus rom twice?
Sent from my GT-I9000 using xda app-developers app
Let's just get the Asus stock ROM on there first. Do you get the blue bar after flashing it from twrp (make sure you flash the zip inside the Asus zip)?
sbdags said:
Let's just get the Asus stock ROM on there first. Do you get the blue bar after flashing it from twrp (make sure you flash the zip inside the Asus zip)?
Click to expand...
Click to collapse
Yes...after flashing the ROM in twrp and rebooting i get the blue bar
moosehead11 said:
Yes...after flashing the ROM in twrp and rebooting i get the blue bar
Click to expand...
Click to collapse
And what happens if you leave it for 20 mins to boot?
sbdags said:
And what happens if you leave it for 20 mins to boot?
Click to expand...
Click to collapse
reflashing as we speak...i've left it going for about 30min on one attempt and it just kept "loading"
i did notice that if i check the file verification before flashing it fails to verify the zip...is that normal?
UPDATE: Left it for 2hrs while i sent out to do something when i got back still "loading"
Try my method! First flash blob via fastboot then wait till blue bar is full then flash twrp then open twrp wipe /system /data /cache then install that zip in twrp
Sent from my sensational HTC Desire C
noahvt said:
Try my method! First flash blob via fastboot then wait till blue bar is full then flash twrp then open twrp wipe /system /data /cache then install that zip in twrp
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
is it normal for the zip to fail verification in twrp?
Yes it's normal disable that verification!
Sent from my sensational HTC Desire C
noahvt said:
Yes it's normal disable that verification!
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Well i tried your method and still no go
What would happen if i tried an older Asus rom from the 4.1 bootloader...would that maybe fix things
Sent from my GT-I9000 using xda app-developers app
you could try BUT REMEMBER AFTER FLASHING IN FASTBOOT: FLASH THE 4.1 TWRP!!!!!!
Sent from my Transformer Pad TF300T using xda app-developers app
Related
Hi!
Yesterday my friend asked me to I helped him with unlock, recovery and Custom ROM. I didn't have enough time to help him, so he does it himself. He succesfull unlocked, install TWRP 2.4.3.0 and install CROMI 3.4.4. When he finished install CROMI he reboot system. After 5 minutes he rebooted to bootloader menu (Vol- & Pwr) and from 4 icons (RCK, USB, Wipe Data, Android Logo) he choosed Wipe Data. It dindn't brick his device! He has got this on the newest JB 4.1.1 bootloader.
It's amazing! Does anyone can confirm this information?
Maybe Asus fix bootloader bug? Nobody know.
Hazard17 said:
Hi!
Yesterday my friend asked me to I helped him with unlock, recovery and Custom ROM. I didn't have enough time to help him, so he does it himself. He succesfull unlocked, install TWRP 2.4.3.0 and install CROMI 3.4.4. When he finished install CROMI he reboot system. After 5 minutes he rebooted to bootloader menu (Vol- & Pwr) and from 4 icons (RCK, USB, Wipe Data, Android Logo) he choosed Wipe Data. It dindn't brick his device! He has got this on the newest JB 4.1.1 bootloader.
It's amazing! Does anyone can confirm this information?
Maybe Asus fix bootloader bug? Nobody know.
Click to expand...
Click to collapse
Doing it on the latest boot loader with the latest TWRP is fine. The problems occur on an older bootloader with newer recovery or new bootloader with old recovery. By old and new I mean ICS and JB respectively.
He did JB / JB :good:
Hi
I made the mistake of accidentally wiping data in the bootloader when attemping to upgrade my bootloader from 4.1 to 4.2 using the latest Asus Stock ROM. It completed the wipe and booted into a fresh Andriod (CM10.1 nightly) install. Thinking everying was ok i went back into the bootloader and selected recovery to flash the new Asus Rom...i flashed the ROM and after rebooting it hangs (have let it sit from 30 min to 2hrs on different flash attempts) at the ASUS logo with the spinning circle...if i reboot i still have bootloader access so i can get into recovery or fastboot
Is there anyway to save my tablet?
Thansk
moosehead11 said:
Hi
I made the mistake of accidentally wiping data in the bootloader when attemping to upgrade my bootloader from 4.1 to 4.2 using the latest Asus Stock ROM. It completed the wipe and booted into a fresh Andriod (CM10.1 nightly) install. Thinking everying was ok i went back into the bootloader and selected recovery to flash the new Asus Rom...i flashed the ROM and after rebooting it hangs (have let it sit from 30 min to 2hrs on different flash attempts) at the ASUS logo with the spinning circle...if i reboot i still have bootloader access so i can get into recovery or fastboot
Is there anyway to save my tablet?
Thansk
Click to expand...
Click to collapse
If you have the Asus spinning circle yes it is saveable That is just stuck booting the ROM.
So please list which bootloader and recovery you have with versions.
The easiest way to fix for the 10.6.1.14.8 bootloader and TWRP 2.4.40 and up is download my rom. Do a factory wipe from TWRP and flash it.
sbdags said:
If you have the Asus spinning circle yes it is saveable That is just stuck booting the ROM.
So please list which bootloader and recovery you have with versions.
The easiest way to fix for the 10.6.1.14.8 bootloader and TWRP 2.4.40 and up is download my rom. Do a factory wipe from TWRP and flash it.
Click to expand...
Click to collapse
I have the bootloader from the most recent firmware update WW_V10.6.1.15.3 (sorry don't have my tablet in front of me) and i have twrp 2.4.4-4.2 for my recovery
moosehead11 said:
I have the bootloader from the most recent firmware update WW_V10.6.1.15.3 (sorry don't have my tablet in front of me) and i have twrp 2.4.4-4.2 for my recovery
Click to expand...
Click to collapse
I think you need to upgrade TWRP to the 2.5.0 0 JB4.2 version (make sure you grab the JB4.2). Then it should be a case of factory wipe and flash a stock based 10.6.1.15.3 based rom to get you back up and running.
Bootloader is ww_epad-10.6.1.15.3-20130416 a03
I've tried with 2.5-4.2 with no luck same issue
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 07:02 PM ---------- Previous post was at 06:58 PM ----------
sbdags said:
If you have the Asus spinning circle yes it is saveable That is just stuck booting the ROM.
So please list which bootloader and recovery you have with versions.
The easiest way to fix for the 10.6.1.14.8 bootloader and TWRP 2.4.40 and up is download my rom. Do a factory wipe from TWRP and flash it.
Click to expand...
Click to collapse
What is your rom that you are refering to by the wY
Sent from my GT-I9000 using xda app-developers app
Hello,
I was installed the latest firmware (10.6.1.8) and then I lost everything I had on internal hd, and I lost the right root.
Then (I do not know what was in my head) I executed the v8 unlocker (although I was already unlocked) and now the only access is APX mode function.
I can enter in TWRP 2.4.4.0 too (I catch to reinstall it before to do this crap) but he doesnt mount anything. I can't see the internal/external HD. I just see some system folders.
Is there any way to recover my tablet? To recover fastboot ?
Thanks in advance...
Nobody?
Sent from my LG-P500 using xda app-developers app
AFAIK, a fix has not been found for the TWRP bug, so you may be bricked. it sounds like you have the wrong TWRP, did you flash the patched one? Also since you bricked with the v8 unlocker, its hard for me to help you cuz your the first person to do that.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Well, probably not. In this case, I will wait for fixing. I don't have money in order to repair it at the service
Sent from my LG-P500 using xda app-developers app
Wait in your first post you said that you can get into recovery... have you tried mounting with abd? Also, if you can get into twrp, why can you not get into fast boot? You have to go thru fast boot protocol to get to recovery image.... unless your tab boot to recovery automatically (because you have no boot able os)
Sent from my YP-G1 using xda app-developers app
My tablet boot automatically in recovery,
If I start it she goes there. adb doesnt work. When trying adb (or fastboot) commands it says "devices not found/wait for devices"...
If i push the volum down and power button dont do nothing, she open the twrp afther 2 or 3 blinks.
Thanks
So you can't get to the boot loader menu? The screen with three options RCK, android, and wipe data. If you can get there open a command prompt in fast boot and type
fastboot reboot-bootloader
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
No, i cant go to bootloader. I cant use fastboot or adb unfortunately
Sent from my LG-P500 using xda app-developers app
I found a solution to access my sdcard.
If i go to mount option and mount system, then if i go to system folder i see my sdcard.
It was empty, but i was copying the firmware 10.6.1.8 and trying to flash ...
There is an error: unable to mount cache.
I was reading this thread and how i dont have fastboot to upgrade my twrp ... i am wondering if is there a way to flash the twrp421..
Is it?
Or ... is it another way to repar my tablet if now i can acces my sdcard??
Thanks
Any idee is welcome
Thanks
Well first of all, I'm still very unclear on what you did to make all this happen. Can you please elaborate in more detail on EVERYTHING you did leading up to bricking it. Then I might have a few ideas...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
OK...
First of all... A was running CleanROM Inheritance 4.1 and all was running very good.
Then, I was reading this thread and want to install the rom too...
There says:
YOU MUST BE ON JB 4.2.1 WITH THE ASUS STOCK BOOTLOADER 10.6.1.8 AND TWRP 2.4.4.0 BEFORE FLASHING THIS. THE BEST WAY TO DO THIS IS TO FLASH THE STOCK ASUS 10.6.1.8 FIRMWARE.
Click to expand...
Click to collapse
and i was downloading from asus site the firmware to flash it.
I was flash the firmware (10.6.1.8) and let the tablet to boot on official rom.
Here, all was running ok, but when i do a restart and want to access the recovery, it disappear.
I install it again with fastboot (twrp 2.4.4.0) and access it. But no root access, cant mout cache, sdcard, data.
Then I go back to rom ... and was downloaded the latest version of unlocker (v8) ... and run it (this was a big mistake)...
And from here i cant access bootloader menu. No fastboot, no adb...and the tablet it going automatically to twrp
I was scare and wipe cache, dalvik cache, system and factory reset (this was a big mistake too ) and try to install again the firmware
But i get an error: unable to mount cache
Because i was install the recovery, i have the recovery installed and the tablet go automatically on twrp.
As I said, I can access sdcard if I mount system, from mount option, but twrp is useless
(system is the only option that i can mount. No cache, sdcard and data)
I hope i explained in detail and you can help me with few ideas
Sorry for my mistake in grammar ( i'm not a good english speaker )
Thanks in advance...
Please ... have someone an idee?
LE:
Is there a way to reinstall bootloader from apx?
OK so I was having problems with my tablet's recovery and I was following this guide that told me to basically wipe all my .img s (boot.IMG, system.IMG , ect.) via fast boot. Then it said to flash the update zip. Well I tried downloading the firmware from Asus website and whenever I tried flashing that with fastboot it gave me an error saying it didn't have a android-info file. Then I tried installing not twrp and cwm and they installed but whenever I tried to go to recovery it just went straight to the fast boot screen. So basically now I just have a tablet that can only do fast boot. What should I do? Is there a different update.zip I should flash or am I basically screwed
Sent from my Nexus 4 using xda app-developers app
charger04 said:
OK so I was having problems with my tablet's recovery and I was following this guide that told me to basically wipe all my .img s (boot.IMG, system.IMG , ect.) via fast boot. Then it said to flash the update zip. Well I tried downloading the firmware from Asus website and whenever I tried flashing that with fastboot it gave me an error saying it didn't have a android-info file. Then I tried installing not twrp and cwm and they installed but whenever I tried to go to recovery it just went straight to the fast boot screen. So basically now I just have a tablet that can only do fast boot. What should I do? Is there a different update.zip I should flash or am I basically screwed
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your write-up isn't very clear. What is your current firmware version (Settings>About Tablet>Build Number) on stock ROM or reboot into bootloader and read it from the upper left text block. Did you install TWRP or CWM recovery? What recovery version? What update.zip? What guide were you following (provide link)?
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
pariahcomplex said:
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
Click to expand...
Click to collapse
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
I tried that right when I saw fast boot coming up, nothing would go through, I did fix it by using the method posted by Buster by using fast boot to systematically erase everything one by one then flash new firmware, just thought this info might be helpful, it's almost like twrp becomes a separate partition when you use asus wipe since everything is still there and bootable
kaos420 said:
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
Click to expand...
Click to collapse
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
It IS Lupus said:
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
Click to expand...
Click to collapse
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
kaos420 said:
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
Click to expand...
Click to collapse
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
It IS Lupus said:
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Buster99 said:
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Click to expand...
Click to collapse
This is how I ended up fixing mine, can't thank you enough Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
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!