What I have:
A LOCKED Bootloader, TF201 Transformer Prime in reboot loop at the ASUS inspiring innovation Persistent Perfection -----------Powered by NVIDIA TEGRA
What else it can do:
Vol down + PWR =
android cardhu-user bootloader <1.00e> released by "US_epad-10.4.2.18-20121122" A03
And the 4 icons
At ther RCK icon :
Booting recovery kernel image
Siignature match
and inmediatly the dead android with the red tringle
I have triyed to flash the original recovery included in WSG Unbricker v1.03 That when ran it appears to be the v1.02 version (its files are appeareantly from the .15 ROM) the flashboot proccess looks like complete OK, but nothing diferent happens, I also triyed to flash the TWRP 2.5.0.0 with the same result.
At the ANDROID Icon it restarts in the same loop
At the USB Icon:
it goes to the fastboot mode and looks like it receive commands, (BOOTLOADER IS NOT Unlocked)
The fastoboot devices gives: 015c7d7a4743f807 fastboot
At this point i have ran the WSG Unbricker v1.03 commands (in its menu, and manually) and the same result : Looks like it receive fastboot commands like write system, recovery, bootloader but always stucks on the same ASUS screen. Receives the erase user data command,
I also have flashed the blob file inside US_epad-user-10.4.2.18.zip file downloaded from ASUS support page
I triyed to ran the update using a FAT32 freshly formated micro sd (It just did nothing) don't even try to start the process( i triyed many signatures: US, WW, .18, .17)
I triyed using those commands:
fastboot -i 0x0b05 flash staging <blob file> . The result is:
sending 'staging' (537604 Kb) ...
Okay [68649 s]
writing staging' ...
Okay [0.081s]
Finished total time: 68.735s
Also triyed the fastboot -i 0x0b05 flash :
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 flash system system.img
Erasing Current Recovery.img
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 flash recovery recovery.img
Flashing Bootloader
fastboot -i 0x0b05 flash bootloader bootloader.bin
Flashing Kernel
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 flash boot boot.img
I triyed the blob file inside the US_epad-user-10.4.2.18.zip, the blob, and other files comming from the WSG Unbricker V1.03,
At the WIPE DATA Icon: It starts the process, the android appears for a second and inmediatly the dead andy apperars. And nothing else happend.
I'm sorry for my english, in a spanish spoken LA.
Being said that, I wanna know what my chances are?
Please give me some advice to bring back the Prime to live.
Thank You
Javier
I have seen something............... After sending a fastboot command, the tf201 looks like not receiving more commands, If I flash some area, and then try to send another command, the tf201 do not respond, not even a reboot command.
The reboot command sometimes gives an OK status but the divice do not reboots. But the write commands gives a write error after a previous write intent
I have an unlocked tf201 running hairybean 2.2, is there a way to copy the OS from it and place it somehow on my bricked one?
please help
Any advice would be really appreciated
thx
I think this is a very good case for a tech guru, i don't wanna give up easily, may be adb commands or a console can help placing the Operating system
jmontalvo1 said:
Any advice would be really appreciated
thx
I think this is a very good case for a tech guru, i don't wanna give up easily, may be adb commands or a console can help placing the Operating system
Click to expand...
Click to collapse
Unfortunately I am on holidays at the moment but if no one has fixed you in the next 2 weeks I will try and help you over google talk.
flumpster said:
Unfortunately I am on holidays at the moment but if no one has fixed you in the next 2 weeks I will try and help you over google talk.
Click to expand...
Click to collapse
Thank you, your help will be very appreciated. No one else seams to have the knowledge or want to help
jmontalvo1 said:
Thank you, your help will be very appreciated. No one else seams to have the knowledge or want to help
Click to expand...
Click to collapse
If you are able to resolve this issue please post how you accomplished this! I have a similar issue. Thanks
aman99 said:
If you are able to resolve this issue please post how you accomplished this! I have a similar issue. Thanks
Click to expand...
Click to collapse
I hope someone could help me
jmontalvo1 said:
I hope someone could help me
Click to expand...
Click to collapse
sahilcc7 kindly gave me the info I needed to fix my issue! Check out the end of this thread. Hope this solves your problem as well.
http://forum.xda-developers.com/showthread.php?p=42998646&posted=1#post42998646
I'd be more than happy to assist if you were unlocked, or had nvflash enabled.
Scribbled from my Note II
www.projectintercession.blogspot.com
andrewjt19 said:
I'd be more than happy to assist if you were unlocked, or had nvflash enabled.
Scribbled from my Note II
www.projectintercession.blogspot.com
Click to expand...
Click to collapse
I yes, lash enabled would b excellent, but it is not unlocked at least. I don't know what to do
flumpster said:
Unfortunately I am on holidays at the moment but if no one has fixed you in the next 2 weeks I will try and help you over google talk.
Click to expand...
Click to collapse
Hi, now you have some time to try to help me?
I really need some
jmontalvo1 said:
Hi, now you have some time to try to help me?
I really need some
Click to expand...
Click to collapse
I found this thread that resolved the problem for me at least.
http://forum.xda-developers.com/show....php?t=1916952
If it helps you thank me.
jmontalvo1 said:
Hi, now you have some time to try to help me?
I really need some
Click to expand...
Click to collapse
404 Page Not Found
The page you requested was not found. Use the search tool below to find content on our site.
I also have a locked and unrooted prime. It was working fine and then yesterday I tried to wake the screen - nothing happened. I held down the power button and the system restarted but got stuck at the ASUS splash screen.
I have tried using power vol -, but when I select RCK it gets to 'Signature match' and does nothing. I tried the android icon on this screen too, but it also sticks at signature match. I do not get any dead androids or androids with guts out!
I have tried completely draining the battery, charging and then booting but it does not help.
Next steps I intend:
1. Erase data from the 4 icon screen and re-try boot
2. Try to use firmware from Asus site on an SDcard via RCK icon and re-try
3. ??
4. RMA?
Anyone have any advice? Do my next steps seem sensible? Should I be doing anything else? I am a complete newbie so please speak slowly
Related
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Thank you sooo much. This brought life back to my tablet!
jmonster141 said:
Thank you sooo much. This brought life back to my tablet!
Click to expand...
Click to collapse
I'm really glad to hear it! I almost thought I had posted this for nothing.
Yea man. I was set on me having a $500 paper weight. You're my tablet's savior. Thanks again
Sent from my myTouch 4g using xda app-developers app
thank you
i wanted to thank you so very much i was at my wits end stayed up for hours trying to fix a simple mistake and you saved the day with this if you where standing here i think i would prob kiss ya cause im that happy that i didn't mess up my only real toy i have
:good: I can't thank you enough, I've been working on mine for a few days now, bad rom download messed it up, then one click fix made things worse, was starting to think hardware issues when nothing was saving or taking, you just saved my tab and made my day than you
Happy to hear it. Have fun with custom roms! I'm on cm10 jellybro, I highly recommend it.
Sent from my Transformer Prime TF201 using xda app-developers app
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Did you download the stock .28 rom and take out the system blob? Have you checked the MD5's to make sure they're downloaded without any corruptions?
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Assuming you have access to adb, put the rom file in your adb folder you have been working from, in windows, right click the rom file, go to properieties, copy the name of the file.
In your adb command box you opened from within your adb folder (pressand hold shift while right clicking select command prompt here) type adb push then right click and paste the name of the rom you copied followed by .zip
This should take about 5 minutes to transfer, go get a coffee or something.
Once done, boot into recovery (twrp)
Under install you should see the rom, install, after the reboot you should be good....
i got stuck in a bootloop trying to unbrick, i can boot into recovery using this but when i try to transfer a rom with adb it gives an error that /sdcard is read-only so i cant put my rom on it. i tried using the stock .28 blob but im still in the same bootloop. not sure what else to
Deleted... whew!
Thanks guys for the help. I'm back up and running
Sent from my Transformer Prime TF201 using Tapatalk 2
Thank you soooo much. I have a working tablet again!
Worked!!
geo.z said:
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Click to expand...
Click to collapse
:good::good: Thank you soooo much..My prime is alive !! very much appreciated!!!
Dead link
The link for the ubuntu for android kernel is dead...
Can someone post it back please ?
When I attempt to flash the blobs through fastboot it gives me FAILED unknown error. Anyone help me please? The recovery flashes fine but the boot image gives me the failed error. When i try to access recovery it gives me unrecoverable bootloader error
im trying to flash main kernel i get error that says fastboot.exe has stopped working. Any help?
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash recovery twrp.blob
sending 'recovery' (7462 KB)...
OKAY [ 2.037s]
writing 'recovery'...
OKAY [ 1.006s]
finished. total time: 3.045s
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash boot prime-sdlinux.blob
error: out of memory
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
tomolewis said:
I have the same issue, I swapped the settings.apk and settingprovidor.apk from the wrong custpack and not its stuck in a boot loop.
I have the original files but can't add them back to the phone
anybody?
Click to expand...
Click to collapse
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
chronic8000 said:
Can you not ADB PUSH them back to the phone with it in recovery mode? might fix your issue possibly.
Click to expand...
Click to collapse
look this
http://www.forum-generationmobiles.net/f447-one-touch-idol-s
Any news on this?
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
chronic8000 said:
Hi,
I am having really bad issues with my Alcatel One Touch Idol S OT-6034R and need to reflash it back to stock. On Sammy phones their is an option as everyone probably knows of emergency firmware recovery. Not so with Alcatel. i tried their "One touch upgrade" software but it says it is already the latest version, which yeah I know it is but I want to reflash it. I tried calling Alcatel and they said it must be sent off. Really? For something I could fix myself if only they just provided the stuff to do it. If anyone has any ideas where I could get the stock zip file that I can flash with stock recovery or other files I could grab to force the flash then please help with anything you may have.
Many thanks, I know never to buy Alcatel again but until I can afford another phone I am stuck with this one.
Click to expand...
Click to collapse
reflash
pmarkov said:
Hello, I'm in the same position with 6034R - need to reflash but the application says I'm already on the latest version. Did anybody found a solution on this?
Click to expand...
Click to collapse
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
gabcs said:
This worked for me:
system.img - mega.co.nz/#!HBIF3KzY!R6roKuvEeVYCcPFphY0fPi7FoMll0WqRaCZQLoroP_w
custpack.img - mediafire.com/download/hccfk2bqq81m3oi/custpack_modifier.img
recovery.img - mediafire.com/download/vdl78u0fhov6xhl/idolscwm6.0.3.7.img
boot.img - shared.com/vkk89d3d6b?s=l
reflash:
adb reboot bootloader
fastboot -i 0x1bbb erase boot.img
fastboot -i 0x1bbb erase recovery.img
fastboot -i 0x1bbb erase system.img
fastboot -i 0x1bbb erase custpack.img
fastboot -i 0x1bbb flash boot boot.img
fastboot -i 0x1bbb flash recovery recovery.img
fastboot -i 0x1bbb flash system system.img
fastboot -i 0x1bbb flash custpack custpack.img
fastboot -i 0x1bbb reboot
Links and commands from: forum-generationmobiles.net/t74868-tuto-transformer-ultym4-en-idol-s
and big thanks for dams161 :good:
Click to expand...
Click to collapse
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Root Alcatel
Hello everyone, Esque quelqun could tell me when will esqu'on rooter The alcatel one touch idol 2 mini S android 4.3 please
zlamar said:
Hi, everyone!
I have the same problem. Everything worked fine untill I changed some values in build.prop. Since then the phone freezes on operator logo when I try to boot.
I can boot to CWM and restore previously made backup, but no results, can't boot to system.
When I try with ADB; "fastboot -i 0x1bbb erase boot.img" it tells me that partition table is missing..... Is it possible to restore partition table informations? Any further thoughts?
Click to expand...
Click to collapse
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
gabcs said:
Leave the erase command, just boot into cwm, format the system, custpack, reboot to bootloader and flash the files Will working too
Click to expand...
Click to collapse
pmarkov said:
The custpack file seems to be wrong. I've managed to flash the files but this version of custpack leads to bootloop. I found another version custpack on the french forum and with it booted successfully but... NO WIFI, NO GSM. And the "Baseband version" is Unknown.
Click to expand...
Click to collapse
Try this: shared.com/7dwx96a1yy?s=l
This is from the french forum - I already tried exactly this image with no success.
gabcs said:
Try this: shared.com/7dwx96a1yy?s=l
Click to expand...
Click to collapse
pmarkov said:
This is from the french forum - I already tried exactly this image with no success.
Click to expand...
Click to collapse
your phone is 6034 or 6035? i tried on 2 phones (6034r) and the custpack is work. one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
gabcs said:
one of these roms maybe help...this is my last idea
mediafire.com/folder/628vrfsah9mbs/recovery#44uztz6cagnl7
Click to expand...
Click to collapse
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
zlamar said:
Can you please explain us more about this last resource?
In folder BS472 there are 3 files... isn't "custpack.img" to small? And should we rename "boot-bs472.img" and "recovery_bs472.img" to "boot.img" and "recovery.img" before flashing?
And about two ROMs; first is just 70 Mb in size and the other is 233 Mb? Are they both working as standalone ROMs or something else? Should we flash it with CWM?
Maybe flashing ROM will resolve all problems?
What about other folders and files within?
Sorry for lot of questions, but this phone is a frustrating experience for me...
Click to expand...
Click to collapse
Sorry, but my english is bad. But yeah, i know, i spent 3 days (0-24) to fix this phone. For me the reflash custpack, boot and system img worked from my first post. From mediafire folder need just the 2 roms. the first 70mb is only the system. The orange rom i think the full rom. Yes, every two are cwm flashable. Try to flash the img-s in bootloader mode after flash the 70mb rom with cwm. If dont work make a factory reset with cwm and flash the 233mb orange rom. This phone's software like a nightmare. No source code, everything is different like in other phones and nobody knows the different between the 6034 and 6035. I better like my OT-991 with MTK soc...
@gabcs
Unfortunatelly, after no success in searching for solution (couldn't find the ROM), two weeks ago, I gave up and sent my phone to service center and I hope that they will resolve the problem. Big and frustrating issue was that I couldn't get to bootloader any more, so the phone couldn't recieve adb commands, only thing that worked was CWM...
Service center will resolve that for 20 euros, and I will resolve my nerves
Anyway, thank you for your time and your help.
@zlamar,
what happened with your phone? Did you managed to have it repaired/restored? My phone is still bricked and It seems the problem is to find the appropriate custpack image as the french versions don't work for other countries.
Still nothing.... Service center where I gave it for repair isn't authorised and they didn't resolve the issue.
Does anybody have a full CWM backup image, and is willing to share it and upload it somewhere?
It has nothing to do with authorization, they just don't have alcatel service access.
There is special alcatel service flasher, that works online, and is intended for Qualcomm platform.
I played with it, and re-flashed my 6016x (MSM8210 - Qualcomm Snapdragon 200).
If you were somewhere closer, I would repair it for 20€ very fast and effiecent
@pmarkov ... I have original files but they are useless, because no any flasher to use them.
b.r.
ALex
Hi Alex,
Thanks for the clarification. Obviously this magic flashing tool is only internaly available for authorized service providers. Today I contacted the official local partner of Alcatel and they were positive they can handle the reflashing for approx. 20 EUR. Let's hope they really will fix it.
BR
Hi all,
Just followed the instructions below to get a new rom on my TF201.
Now I have Teamwin recovery booting showing V2.6.3.0 and asking for a password.
Teamwin does not show data in external or internal sdcards.
I am unable to get into fastboot mode, using power and vol down.
It has failed since running this line fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
I have all of the nvflash blobs etc.
Any ideas how to recover from this point?
Thanks
RR
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is 'upgrade_tf201_to_tf300t.zip'
CROMBI 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push CROMBI-KK onto your tab
Code:
adb push cm-11.0-2014xxxx-crombi-kk-tf201t.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
ADB interface working
Ok, lots of playing this morning tells me that the adb interface is working when the teamwin recovery is showing.
adb devices gives <number> recovery
Any ideas how to proceed from here, apart from carefully
RangeyRover1 said:
Ok, lots of playing this morning tells me that the adb interface is working when the teamwin recovery is showing.
adb devices gives <number> recovery
Any ideas how to proceed from here, apart from carefully
Click to expand...
Click to collapse
When on the twrp screen .....
Does the command .....
Code:
adb reboot-bootloader
Do anything ??
Thx Josh
Hello I was having a tough time trying to Flash Crombi KK rom. At 1 point I had to use a recovery blob because I was stuck. I started from there upgraded bootloader and twrp 2.5. Flashed twrp 2.8 and Crombi KK rom kept showing fail. I eventually gave up and tried to go from 2.8 TWRP back to 2.5 with JB Bootloader. Bad move I know. Whenever I pressed up to go to recovery it would get stuck. Then eventually I tried wiping data from Bootloader screen. Now the 3 options, recovery, coldboot and wipe data wont show. Stuck at Asus screen "The Device is Unlocked".
I downloaded naked drivers and android ADB drivers.. however I cannot get them to install on windows 7. I'd appreciate any help to try to this back running again
Lyvewire said:
Hello I was having a tough time trying to Flash Crombi KK rom. At 1 point I had to use a recovery blob because I was stuck. I started from there upgraded bootloader and twrp 2.5. Flashed twrp 2.8 and Crombi KK rom kept showing fail. I eventually gave up and tried to go from 2.8 TWRP back to 2.5 with JB Bootloader. Bad move I know. Whenever I pressed up to go to recovery it would get stuck. Then eventually I tried wiping data from Bootloader screen. Now the 3 options, recovery, coldboot and wipe data wont show. Stuck at Asus screen "The Device is Unlocked".
I downloaded naked drivers and android ADB drivers.. however I cannot get them to install on windows 7. I'd appreciate any help to try to this back running again
Click to expand...
Click to collapse
Do you have your nvflash blobs backed up ?
Thx Josh
lj50036 said:
Do you have your nvflash blobs backed up ?
Thx Josh
Click to expand...
Click to collapse
No blobs. I 've had this device since day one. Rooted it, bricked before but never this. I remember having a hard time making a NVFlashbackup for the same reason of my device showing up and eventually gave up. Any other suggestions?
Lyvewire said:
No blobs. I 've had this device since day one. Rooted it, bricked before but never this. I remember having a hard time making a NVFlashbackup for the same reason of my device showing up and eventually gave up. Any other suggestions?
Click to expand...
Click to collapse
No nvflash blob, no fastboot, no adb ....
There is nothing that can be done if the above statement is true ......
Thx Josh
lj50036 said:
No nvflash blob, no fastboot, no adb ....
There is nothing that can be done if the above statement is true ......
Thx Josh
Click to expand...
Click to collapse
Thanks for replying
I tried using this http://forum.xda-developers.com/showthread.php?t=2588979 to install ADB. It got to waiting for device and of course nothing. Is there something else needed to get the ADB to read the device? I downloaded the naked drivers as well but nothing showed up in device manager. No executable file to run. Am I missing something?
WooHoo
lj50036 said:
When on the twrp screen .....
Does the command .....
Code:
adb reboot-bootloader
Do anything ??
Thx Josh
Click to expand...
Click to collapse
Why, yes. yes it does Thanks.
Ok I have the RCK, Android,wipe data icons.
fastboot devices on this screen now gives <number> fastboot
Woot!
I'm keen to have specific instructions on how to recover from this point back to stock, then take a deep breath and try to get to custom.
My concern is that a lot of the threads with guidance for recovery and flashing are old, and I don't want to brick this thing.
So, is there a thread for recovery to stock from this point?
I have found this thread discussing recovery. http://forum.xda-developers.com/transformer-prime/help/guide-t2864946
am waiting for full charge of tablet at the moment.
Thanks for all the help so far.
RR
RangeyRover1 said:
Why, yes. yes it does Thanks.
Ok I have the RCK, Android,wipe data icons.
fastboot devices on this screen now gives <number> fastboot
Woot!
I'm keen to have specific instructions on how to recover from this point back to stock, then take a deep breath and try to get to custom.
My concern is that a lot of the threads with guidance for recovery and flashing are old, and I don't want to brick this thing.
So, is there a thread for recovery to stock from this point?
Thanks for all the help so far.
RR
Click to expand...
Click to collapse
You need the blob from the stock frimware downloaded from the Asus website ....
It will be in a zip file that needs unzipped twice ...... Make sure you get the correct 'SKU' for your tablet ......
Then follow this guide, skip to the first fastboot command and go from there .....
http://forum.xda-developers.com/showthread.php?t=2538028
Thx Josh
FIXED
lj50036 said:
You need the blob from the stock frimware downloaded from the Asus website ....
It will be in a zip file that needs unzipped twice ...... Make sure you get the correct 'SKU' for your tablet ......
Then follow this guide, skip to the first fastboot command and go from there .....
http://forum.xda-developers.com/showthread.php?t=2538028
Thx Josh
Click to expand...
Click to collapse
Thanks, thats got me back to square one.
Maybe a new thread detailing the pain to get to Custom rom!
Cheers Josh.
RR
tf300 update required?
Ok, i seem to be failing when i apply neowin tf300 update, when following the crombikk instructions on post #4. The system does not now boot into recovery. Is this step absolutely required for the newer roms?
Thanks
RR
Hey guys, after receiving my new Kindle Fire (ariel running 4.5.3) I followed steps 1-3 outlined here and managed to get TWRP installed and my Kindle rooted. Things started going wrong in step 4 however, when I followed the instructions linking to here, which then linked to here. Steps 6-8 of DeLooper's instructions are where I started to run into problems.
I installed the 4.5.4 update and then the SuperSU update and clicked reboot. I didn't see the "updating message" referred to in the instructions, instead the device just went into a boot loop. During this boot loop, I was still able to get the device into adb mode, and from there back into the TWRP recovery. I tried flashing the same file (with and without SuperSU) several more times with the same results. I also tried wiping the cache as well as doing a factory reset and still nothing.
After going back to the second link above (bibikalka's post), I downloaded the 4.5.4 update file he linked to from Dropbox in "Update 3" (which was different than the 4.5.4 update linked to by DoLooper). I then installed this file using TWRP and rebooted. At this point, my device went back into a boot loop, but now I am unable to access ADB or my recovery.
I still can get the device into fastboot, so I don't believe this is irrecoverable. I tried issuing the following:
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
however, the command just hangs and nothing happens as far as I can tell.
My guess is that my recovery/bootloader file(s) are to blame for my problems? I'm still fairly inexperienced with all of this, so any wisdom or direction anyone could provide would be GREATLY appreciated. Thanks!
So here's some additional information -
Like I mentioned above, I can get the device into Fastboot mode, but once I get there I can only send one "successful" command. The first command supposedly works but the second will just hang. Occasionally on the second command I'll get the following
ERROR: could not clear input pipe; result e0004051, ignoring...
ERROR: could not clear output pipe; result e0004051, ignoring...
Click to expand...
Click to collapse
So from here I can run
Code:
fastboot -i 0x1949 boot boot.img
and I get
downloading 'boot.img'...
OKAY [ 0.204s]
booting...
Click to expand...
Click to collapse
and that's where it sticks. I've also tried doing the same with the TWRP recovery image I've got and the same thing happens.
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
greenie01 said:
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
Click to expand...
Click to collapse
Sorry you're dealing with this. @bibikalka will have to give you a hand. Just wanted to mention that the difference between the two TWRP_ready update zips is not significant. (Explained here: http://forum.xda-developers.com/showpost.php?p=61771073&postcount=28 ) I linked to mine while b's was briefly unavailable.
Early on a couple people flashed update zip into recovery partition, but I'm not sure how that happened or if it could be the problem. Hang in there. Bibikalka can advise.
greenie01 said:
So here's some additional information -
Like I mentioned above, I can get the device into Fastboot mode, but once I get there I can only send one "successful" command. The first command supposedly works but the second will just hang. Occasionally on the second command I'll get the following
So from here I can run
Code:
fastboot -i 0x1949 boot boot.img
and I get
and that's where it sticks. I've also tried doing the same with the TWRP recovery image I've got and the same thing happens.
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
Click to expand...
Click to collapse
If you cannot boot into TWRP, I think you are done (Pwr & Vol+ during boot up). I wonder if somehow you have 4.5.4 bootloaders in there (instead of 4.5.3), because these would prevent you from booting into TWRP.
Try to get into TWRP, if not, call Amazon.
**XT2041-4**
hey folks,
i have the gpower/g8power (XT2041-4) and i was able to unlock the bootloader and i have been able to do the fastboot commands but it fails when i do the fastboot system, product, vbmeta commands for the crdroid, lineage and havok. i got into twrp and tried installing the zips for those roms but those failed too.
i got to the android OS start screen but the touchscreen is unresponsive. i have looked through a lot of the threads for this device and can't find anything that works.
any help will be much appreciated because this is my daily driver.
edit: title should be XT2041-4
your best option would be to connect an otg cable, ( best is to make sure you can have a double connection, one for mouse , on connected to the pc) then get into the phone with the non-touchscreen booted rom, connect it to LMSA , and extract the boot.img image that comes with the rom LMSA downloads. you should have a working touchscreen with the version LMSA downloads .
Reason you need a double connection: you need to accept the connection to your pc from the phone
you could also browse to the settings --> about this phone and take a look at the exact ROM that is installed, and find that image on lollinet , then extract and boot the boot.img from that rom.
Hey, I'm having the same problem but I found a workaround.
you can either go in fastboot mode and enter
fastboot set_active b
or go in TWRP and change the active slot to B then proceed to boot up the phone.
In my case, it showed warning saying "cannot boot into system......file maybe corrupted" etc etc, just choose "factory reset" on that screen and your phone should boot into slot B with stock ROM.
That way you can have a functional phone while waiting for the developers to figure out the kernel problem
Cheers
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
Chosimise said:
waiting for the developers to figure out the kernel problem
Cheers
Click to expand...
Click to collapse
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
I had a completely different issue with the exact same model. I made a post here asking if anyone had an easy fix, but my guess is that these are just growing pains. Give it a couple months and the roms will likely be much more stable. One of the reasons I bought this phone in the first place is because it usually gets official Lineage OS support at some point. With time, I'm sure things will work great. If you use Windows, going back to stock everything is pretty dead simple with the Lenovo Rescue and Recovery tool, so you can kind of experiment safely if you back everything up.
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
After some tinkering, I actually figured out my problem. There's a big difference between "fastboot mode" (the one you enter by pressing power and vol-) and "Fastbootd" mode.
I did all my flashing in "fastboot mode" and I got no touch screen afterward.
Then there's another hiccup for me (which is why I didn't go in "fastbootd" mode in the first place): When I type in the command in regular "fastboot mode"
Code:
fastboot reboot fastboot
I got an error message saying "reboot fastboot" is not a valid destination or something down those lines.
The problem being, they only added that option in fastboot version r30, so I had to update my ADB and fastboot environment.
And I ran into yet another problem, no matter what I do, the fastboot command is still run with the older version. I guess I messed up the previous installation and the pathing got messy. I ended up using my work laptop for a clean installation of all drivers and it finally solved my problem. I guess I'm saying you need to clean up previous adb and fastboot drivers before using the new ones, especailly if you installed it systemwise.
Anyways, after I booted into "fastbootd" mode and flashed everything with the latest version of fastboot driver, the phone worked flawlessly.
Hope it helps!
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
uglyaf said:
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
Click to expand...
Click to collapse
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Beetle84 said:
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Click to expand...
Click to collapse
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
uglyaf said:
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
Click to expand...
Click to collapse
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Beetle84 said:
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Click to expand...
Click to collapse
ok thanks i did that and got version 1.4.3 it sees my device but when i did the fastboot reboot fastboot i got
fastboot: usage: unknown reboot target fastboot
and nothing happened. does anyone know what that means?
ok yes indeed im a huge idiot. i finally got into fastbootd because i downloaded ADB version R30. THATS the most recent adb version and that did the trick! now i got the fastbootd recovery screen!
regardless, thank you all SOOOOO much for taking the time to respond. much appreciated.
im so excited to get flashing!
peace and love
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
brucedroid031 said:
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
Click to expand...
Click to collapse
good look thank you