Hey guys, sorry that this is my second thread since I registered, and both are help threads, but this website came highly recommended.
Anyway, I bought an Asus TF201 tablet that came rooted, unlocked, and with CM10 loaded on it. I wiped everything I could in the pre-OS Tweaker thingy and installed an official Jellybean ROM on it that I downloaded from Asus's website. The funny thing is that the tablet was in Chinese upon first boot. Another weird thing is that the Tweaker tool that allowed me to install stuff disappeared.
All that's on there is on the screen is, in this order, RCK (which when selected shows an Android figure with his chest opened and an orange triangle w/ an exclamation mark on top), Android (which boots into the JB ROM), a USB sign (which starts a "Starting Fastboot USB download protocol"), and a Wipe Data sign (which I haven't had the balls to select).
There's also this on the top left corner:
Press (Volume Down) to select, (Volume Up) for selection move
Android cardhV-user bootloader (1.00 e) released by "CN_epad-10.4.2.17-20121018" A03
OS will cold boot in 10 seconds if no input is detected
The Vol Down and Vol Up functions are reversed for some reason.
I don't know what was done to the tablet before I bought it, and I don't know what I did when I wiped the data and installed a new ROM onto it. I'm normally decent with following custom ROM installation guides, but this time I honestly don't know what to do. The only problem with the tablet in its current state is that I can't get Play Store on it, and Asus said that because it's rooted/unlocked, they won't support it.
I'm hoping someone can walk me through a step-by-step process and get this tablet back to as close to factory settings as possible, with Play Store installed.
Sorry I'm asking so much, but I have nowhere else to go.
androidbrownie said:
Hey guys, sorry that this is my second thread since I registered, and both are help threads, but this website came highly recommended.
Anyway, I bought an Asus TF201 tablet that came rooted, unlocked, and with CM10 loaded on it. I wiped everything I could in the pre-OS Tweaker thingy and installed an official Jellybean ROM on it that I downloaded from Asus's website. The funny thing is that the tablet was in Chinese upon first boot. Another weird thing is that the Tweaker tool that allowed me to install stuff disappeared.
All that's on there is on the screen is, in this order, RCK (which when selected shows an Android figure with his chest opened and an orange triangle w/ an exclamation mark on top), Android (which boots into the JB ROM), a USB sign (which starts a "Starting Fastboot USB download protocol"), and a Wipe Data sign (which I haven't had the balls to select).
There's also this on the top left corner:
Press (Volume Down) to select, (Volume Up) for selection move
Android cardhV-user bootloader (1.00 e) released by "CN_epad-10.4.2.17-20121018" A03
OS will cold boot in 10 seconds if no input is detected
The Vol Down and Vol Up functions are reversed for some reason.
I don't know what was done to the tablet before I bought it, and I don't know what I did when I wiped the data and installed a new ROM onto it. I'm normally decent with following custom ROM installation guides, but this time I honestly don't know what to do. The only problem with the tablet in its current state is that I can't get Play Store on it, and Asus said that because it's rooted/unlocked, they won't support it.
I'm hoping someone can walk me through a step-by-step process and get this tablet back to as close to factory settings as possible, with Play Store installed.
Sorry I'm asking so much, but I have nowhere else to go.
Click to expand...
Click to collapse
First up you have installed a Chinese rom onto it.
You have lost your recovery because you installed an official rom which overwrote your recovery.
Go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the instructions to install TWRP ( the normal one ). This will give you a recovery back that you can install a rom from.
Then go to post 1 and follow the instructions to install HairyBean 1.51 or if you want install a different Jellybean based rom.
flumpster said:
First up you have installed a Chinese rom onto it.
You have lost your recovery because you installed an official rom which overwrote your recovery.
Go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the instructions to install TWRP ( the normal one ). This will give you a recovery back that you can install a rom from.
Then go to post 1 and follow the instructions to install HairyBean 1.51 or if you want install a different Jellybean based rom.
Click to expand...
Click to collapse
Thanks for the prompt response. I just want to know beforehand whether or not there's anything I need to worry about when reinstalling TWRP to it, because of what has possibly been done to it in the past. Barring the possibility of me messing up, if I follow the directions explicitly, would everything be okay? I wouldn't cause a permanent brick by overwriting any necessary files or anything?
androidbrownie said:
Thanks for the prompt response. I just want to know beforehand whether or not there's anything I need to worry about when reinstalling TWRP to it, because of what has possibly been done to it in the past. Barring the possibility of me messing up, if I follow the directions explicitly, would everything be okay? I wouldn't cause a permanent brick by overwriting any necessary files or anything?
Click to expand...
Click to collapse
The way people normally hard brick is by flashing a version of twrp or cwm not meant for their bootloader (ie. flashing a Jellybean Twrp onto an ICS bootloader.)
I can tell by your numbers you posted that you are on the Jellybean bootloader and if you want to make 100 percent sure look at where the nvidia logo is when you turn it on. If it is down the bottom center it is ICS, If it is bottom right it is Jellybean.
The Twrp I linked you to on that page is for Jellybean only.
The only thing that might stay with you is the chinese bootloader but I don't think that will effect anything in the rom. If you really wanted to get rid of that also, after you flash twrp and have it working you could follow the instructions in that second post for "Upgrade instructions for ICS"
Even tho you are on Jellybean now those instructions just flash a version of the Jellybean bootloader that I took out of the world wide release, but I wouldn't do that unless there is some unforeseen problem with having the chinese bootloader.
Thanks! Tablet is all good to go now.
Related
No CWM for me? Primo not going into CWM recovery any way I try
So I unlocked the prime after realizing root was not the only thing I needed to start flashing ROMs.. TRUE
I rooted using Sparky's method, so easy too. I also tried to root with viper mod one time when apparently Sparkys wasnt working again after I did something like un-root for fun. But Vipermod failed due to drivers that weren't installed and still haven't, reason: could not figure out how or what part was the driver to be installed nothing i clicked on (in XP) worked to download the drivers. however XP does recognize the prime after Windows Media Player update 11 . it said flash complete or successful . I've flashed CWM from the app itself but the only real function I have from it is fixing permissions...
So should someone like me who just reads downloads and flashes (like a madman flasher) to just wait for a newer version that is fully functional so I dont mess things up and need to learn hours of great knowledge to unbrick the TFP/???
I've read that its not really working all the way is this true???
and another ?Q: I want my web to be speedy like Speedy Gonzales so what do I delete from it and what is the best web browser for speed surfing... this prime was crawling around untill I deleted some things that were uselessly running it seems to have worked a bit but not enough a delete list would be rad. Also one other question was it my order of operations which led to a faulty CWM? though I ve reflashed it several times to no better result.. And also if you are still reading (and thank you very much if you are) I dont know how to manually give CWM a go or how to manually get into recovery--- volume up and down plus power seems to soft brick the Prime untill I hold down the power button for a while untill it vibrates for a second then release and push it again to turn it on....and I held power plus volume down but such small print showed up on the upper left corner that i couldn't really know what to do... I also saw the symbols one was a USB symbol,Q: What is this function? WHat would happen should I push the USB symbol ???... ALso can I get updates from Asus after the unlocker app has been used EDIT: DON"T need them however I will find out how to turn these FOTAs off . And Q: does anybody know how to keep the Logitech keyboard connected it times out so when you go back for it it can take a good thirty seconds recovering from its nap... any fix? thanks alot I cant wait to start flashing better ROMs than stock, mine is fairly buggy
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Juggernaut 5.0
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Thanks
tedr108 said:
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Click to expand...
Click to collapse
Im giving it a go now thanks for the CWM instructions that part is solved however I asked like ten questions though and am thankful for your answers
I just did a backup in CWM thanks a lot I' d hit thank you again but its gone THANKS!!!
*If I helped hit thanks*
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Darkside
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
I had a similar problem. Bought my Prime from Amazon in the USA and it came preloaded with Honeycomb - imagine that!!! Anyways I struggled as a result to flash a recovery...I seemed to get root quite easily using NachoRoot and ViperMod methods but flashing a recovery and trying to boot into recovery had me ending up with an exclamation marked Android on boot! 1 day of persistent trying and searching high and low, and am glad to report I finally have a rooted Prime with working recovery (just about to flash Touch Recovery now and then a custom ROM...) running ICS 4.0.3...
My steps:
Trying to flash a custom recovery on HoneyComb really was the show-stopper here, using NachoRoot, Memphi*, nor ViperMod...it just wouldn't work using ADB, fastboot etc
So after 1 day of trying and almost dreading having to send the device back to the US for a swap out, I decided to focus instead on upgrading my firmware to 9.x.x.15 (just below the .21 version which has no root tool at the moment!)
So downloaded a pre-rooted ICS 9.x.x.15 custom ROM from somewhere (google is your friend here) and then followed this tutorial here: http://forum.xda-developers.com/showthread.php?t=1492887
Once I was on ICS, it was then easy to use ViperMod (excellent tool!) to quickly get rooted and successfully flash CWM
Great work to the devs of the different tools I have come across and used.
great
fyi, you only need root to flash cwm FROM rom manager, otherwise you can use fastboot to flash cwm manually.
Sent from my TF201
[FIXED]
Got some help on the forum;
downloaded asus firmware, unpacked blob, fastboot flash staging blob; fastboot reboot
Prime is now back to fully operational!
Many thanks to @kkdm
[/FIXED]
Hello,
I have looked around the various threads (including the 'how to unbrick your prime' one) but have not seen this issue mentioned.
I have a strange issue where if I factory reset (i.e. to Asus) the device will simply keep looping at the ASUS EEE logo, with device is unlocked in the top left hand corner. If however I install CM10 or another MOD, it seems to work as normal and boot into the homescren.
Having read around, there was an issue with an Asus update where it appeared to do something similar to this, is it perhaps that I am on that version and thus am getting the same error? Would a simple download and copy of the latest ASUS ROM fix that? I am unsure on how to do this exactly, but have read this was an issue, but I find it unlikely as everything was fine before I unlocked etc.
Is it perhaps the bootloader has become corrupt in some way with the ICS/JB difference? This is just a guess on my limit knowledge...
The reason for putting back the ASUS stock ROM is selling the device, having upgraded to the Infinity, and do not particularly want to send it with CM10 on.
Any help would be greatly appreciated,
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
It turns out there is no ROM on the internal storage anymore (I must have selected the format option on my last attempt at installing Androwookie), as a result I cannot access the sdcard by plugging the thing into my PC.
Is there a way of installing this via the micro SD card slot?
flumpster said:
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
Click to expand...
Click to collapse
Hello,
Just to clarify, I can get into recovery without issue, it just won't boot after factory reset and now hangs at ASUS logo.
Is there a way around this at all? :--(
Hello,
Latest problem is having ASUS Transformer Prime ADB Interface listed in Device Manager, but not being able to use the adb shell.
I get either 'device not found' or occasionally something about /system/sh not being found, in either case this is obviously not good.
I can still get into TWRP 2.1.3 though, surely there must be a way round this?
Now fixed, see first post
I'm relatively new to the process of rooting and flashing so please be gentle senpai. Overall, my question is, how do I get either restored to my back-up, or to a better cleaner ROM. What motivated my tampering was that bluetooth wasn't working in Cyanogenmod 10.1
I received a TF201 tablet from my brother who is fairly experienced with the process of flashing roms and working in the world of rooted devices. He lives a while away so to have him look at it with me is a challenge but I've discussed the status of the tablet with him and he's hopeful that there's a solution.
When I received the tablet it was running the following:
Cyanogenmod 10.1 (according to the settings)
twrp 2.5
JB bootloader (at least this is the best I can conclude since the nvidia insignia is in the bottom right at the splash screen.)
As a side note, when I'd power on while pressing the down volume, in order to get to fast boot I had to select the USB signal option. This changed later. (unsure when.)
The status of the tablet now seems to be (emphasis on seems since I've tried many things while attempting to get a working rom) the following:
Successfully ran restore back-up to Cyanogenmod 10.1 (success being that it ran the data and seemed satisfied when completed with no error codes or issues.)
Running Hairybean 2.31 and twrp 2.5 ( I think, not sure how hairybean fits into the functionality of the recovery but the whole UI is hairy still.)
JB Bootloader (again because the bottom right nvidia)
Fastboot is default and only 3 selections available in recovery mode. While on this screen at the top left it says "Key driver not found . . Booting OS.
When trying to boot to the restored back-up I get a regular ASUS logo with nvidia symbol at bottom right, and "the device is unlocked" at top left. This screen sits for a moment, then goes black (as if it's trying to do the right thing) and then the screen returns and the tablet stays there indefinitely.
In recovery mode, when I select "mount" I'm able to see that "system" has a red switch (so it's not mounted.) I can turn it on, and it stays on persistently while in the recovery mode, but when I've attempted to reboot the tablet either to the ROM or directly back to recovery, the "system" is unmounted again.
This is a summary of what I've done to the tablet, at first I was just trying to get the katkiss ROM according to the thread referenced below. After a few steps I realized I was in trouble and started trying to fix the tablet with anything that would work.
http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
Here is the log I made of what I did to the tablet. Maybe something here will explain the issues I'm having.
It's not completely comprehensive since I realized too late that I should have documented everything I did.
Backed up in TWRP
Flashed Hairybean http://forum.xda-developers.com/showthread.php?t=2407248
Updated TWRP to 2.6.3 as suggested #543 http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919/post56681951#post56681951
Tried to flash katkiss http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
When katkiss failed, tried grimlock kernal according to #543 http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919/post56681951#post56681951
That seemed successful.
Rebooted to twrp recovery (password required)
Searched about password, clicked cancel, attempted to format data but failed.
Attempted to clear data through fastboot according to: http://android.stackexchange.com/questions/89182/bricked-my-tf300t-how-to-re-partition-internal-storage-to-get-it-back
Couldn't get any ROM to work
Decided to try from square 1 to get virtuous prime to work according to http://sitr.us/2012/05/12/installing-a-custom-rom-on-the-transformer-prime.html
Cleared data through fastboot in system, recovery, userdata, boot, misc, and cache.
Flashed clockworkmod
Flashed virtuous prime with fastboot -i 0x0b05 flash system
fastboot -i 0x0b05 reboot
Would not boot to OS, or recovery,
"key driver not found . . booting OS" at top left
After this, I again cleared data through fastboot system, recover, userdata, boot, misc, and cache.
I flashed the default ASUS TF201 kernel from https://github.com/namidairo/android_kernel_asus_tf201
Installed a twrp.blob that I got from a page flumpster recommended it (I can't find it now.)
Able to get to recovery, but received "unable to mount" errors whenever I did any formatting in the recovery mode.
Thank you for your help. I'm open to trying whatever you think will work. I know this is a sensitive product and apparently prone to bricking but I'm really REALLY hoping that I didn't brick my new toy. I don't know if there are other diagnostic tools I'm not aware of that would give me a better read on what the status of my tablet actually is to try to pinpoint the issue or if the only way to do that is to clear everything on it and start over to be sure of what's running.
You guys are phenomenal. Thank you in advance.
aamcc
aamcc said:
I'm relatively new to the process of rooting and flashing so please be gentle senpai. Overall, my question is, how do I get either restored to my back-up, or to a better cleaner ROM. What motivated my tampering was that bluetooth wasn't working in Cyanogenmod 10.1
I received a TF201 tablet from my brother who is fairly experienced with the process of flashing roms and working in the world of rooted devices. He lives a while away so to have him look at it with me is a challenge but I've discussed the status of the tablet with him and he's hopeful that there's a solution.
When I received the tablet it was running the following:
Cyanogenmod 10.1 (according to the settings)
twrp 2.5
JB bootloader (at least this is the best I can conclude since the nvidia insignia is in the bottom right at the splash screen.)
As a side note, when I'd power on while pressing the down volume, in order to get to fast boot I had to select the USB signal option. This changed later. (unsure when.)
The status of the tablet now seems to be (emphasis on seems since I've tried many things while attempting to get a working rom) the following:
Successfully ran restore back-up to Cyanogenmod 10.1 (success being that it ran the data and seemed satisfied when completed with no error codes or issues.)
Running Hairybean 2.31 and twrp 2.5 ( I think, not sure how hairybean fits into the functionality of the recovery but the whole UI is hairy still.)
JB Bootloader (again because the bottom right nvidia)
Fastboot is default and only 3 selections available in recovery mode. While on this screen at the top left it says "Key driver not found . . Booting OS.
When trying to boot to the restored back-up I get a regular ASUS logo with nvidia symbol at bottom right, and "the device is unlocked" at top left. This screen sits for a moment, then goes black (as if it's trying to do the right thing) and then the screen returns and the tablet stays there indefinitely.
In recovery mode, when I select "mount" I'm able to see that "system" has a red switch (so it's not mounted.) I can turn it on, and it stays on persistently while in the recovery mode, but when I've attempted to reboot the tablet either to the ROM or directly back to recovery, the "system" is unmounted again.
This is a summary of what I've done to the tablet, at first I was just trying to get the katkiss ROM according to the thread referenced below. After a few steps I realized I was in trouble and started trying to fix the tablet with anything that would work.
http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
Here is the log I made of what I did to the tablet. Maybe something here will explain the issues I'm having.
It's not completely comprehensive since I realized too late that I should have documented everything I did.Backed up in TWRP
Flashed Hairybean http://forum.xda-developers.com/showthread.php?t=2407248
Updated TWRP to 2.6.3 as suggested #543 http://forum.xda-developers.com/tra...opment/rom-t2817919/post56681951#post56681951
Tried to flash katkiss http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
When katkiss failed, tried grimlock kernal according to #543 http://forum.xda-developers.com/tra...opment/rom-t2817919/post56681951#post56681951
That seemed successful.
Rebooted to twrp recovery (password required)
Searched about password, clicked cancel, attempted to format data but failed.
Attempted to clear data through fastboot according to: http://android.stackexchange.com/qu...-re-partition-internal-storage-to-get-it-back
Couldn't get any ROM to work
Decided to try from square 1 to get virtuous prime to work according to http://sitr.us/2012/05/12/installing-a-custom-rom-on-the-transformer-prime.html
Cleared data through fastboot in system, recovery, userdata, boot, misc, and cache.
Flashed clockworkmod
Flashed virtuous prime with fastboot -i 0x0b05 flash system
fastboot -i 0x0b05 reboot
Would not boot to OS, or recovery,
"key driver not found . . booting OS" at top left
After this, I again cleared data through fastboot system, recover, userdata, boot, misc, and cache.
I flashed the default ASUS TF201 kernel from https://github.com/namidairo/android_kernel_asus_tf201
Installed a twrp.blob that I got from a page flumpster recommended it (I can't find it now.)
Able to get to recovery, but received "unable to mount" errors whenever I did any formatting in the recovery mode.Thank you for your help. I'm open to trying whatever you think will work. I know this is a sensitive product and apparently prone to bricking but I'm really REALLY hoping that I didn't brick my new toy. I don't know if there are other diagnostic tools I'm not aware of that would give me a better read on what the status of my tablet actually is to try to pinpoint the issue or if the only way to do that is to clear everything on it and start over to be sure of what's running.
You guys are phenomenal. Thank you in advance.
aamcc
Click to expand...
Click to collapse
1. do you have now a working recovery?
2. What version?
3. What partitions do mount, what not?
4. Notice 'no keydriver found' is normal with HB but what numbers (bootloader version) are beside this notice?
What I conceive from your report's last readings is, that you 'cleared' (erased?) partitions trough fastboot. So it is clear, that they cannot be mounted, because they are not formatted.
There are several ways to fix this:
1. flash stock ROM (backlash: you will be set back to stock BL, 'recovery', boot, system and data).
2. Try to flash any custom ROM (for a start: KatKiss 4.4.4) if this don't work:
3. Find unblobbed blobs of tf300t stock ROM (search in XDA; I forgot where to find. If you don't find them, I could try to dropbox you some of mine) and flash them one after the other trough fastboot: 'boot', 'system', 'data'. Advantage of this procedure is, that you don't lose Hairy Bean bootloader, which is essentially the tf300t bootloader and enables you to load any kernel and ROM for tf300t.
Crucial is, that you have the right recovery. Namidairo's 2.5 had it's merits, but it is outdated. If you are really in Hairy Bean, then take 2.8.4.0 from here: http://www.techerrata.com/browse/twrp2/tf300t.
das chaos said:
1. do you have now a working recovery?
2. What version?
3. What partitions do mount, what not?
4. Notice 'no keydriver found' is normal with HB but what numbers (bootloader version) are beside this notice?
Click to expand...
Click to collapse
1. Yes I do
2. It appears to be hairybean but I flashed a twrp 2.5
3. When I format data and the system now that I've attempted the restoration of my back-up the "unable to mount" errors don't happen.
However, in the recovery menu when I select mount, the "Mount System" selection is off. I can turn it on but if I reboot to try to run the ROM, or even directly to the recovery again, the switch is turned off again when I check it.
4. At the recovery screen I have the following lines of text
Key driver not found . . Booting OS
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.1-20130711" A03
Starting Fastboot USB download protocol
aamcc said:
1. Yes I do
2. It appears to be hairybean but I flashed a twrp 2.5
3. When I format data and the system now that I've attempted the restoration of my back-up the "unable to mount" errors don't happen.
However, in the recovery menu when I select mount, the "Mount System" selection is off. I can turn it on but if I reboot to try to run the ROM, or even directly to the recovery again, the switch is turned off again when I check it.
4. At the recovery screen I have the following lines of textKey driver not found . . Booting OS
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.27.1-20130711" A03
Starting Fastboot USB download protocol
Click to expand...
Click to collapse
PLZ read my last post again (I edited it).
So you are on the right (tf300t) bootloader. That is fine. But you have the wrong TWRP. So go on and flash the recommended recovery (TWRP 2.8.4.0) and try mounting again. If it works, you can wipe boot, system and data an flash a custom ROM of your choice. Report back. Good luck!
das chaos said:
What I conceive from your report's last readings is, that you 'cleared' (erased?) partitions trough fastboot. So it is clear, that they cannot be mounted, because they are not formatted.
There are several ways to fix this:
1. flash stock ROM (backlash: you will be set back to stock BL, 'recovery', boot, system and data).
2. Try to flash any custom ROM (for a start: KatKiss 4.4.4) if this don't work:
3. Find unblobbed blobs of tf300t stock ROM (search in XDA; I forgot where to find. If you don't find them, I could try to dropbox you some of mine) and flash them one after the other trough fastboot: 'boot', 'system', 'data'. Advantage of this procedure is, that you don't lose Hairy Bean bootloader, which is essentially the tf300t bootloader and enables you to load any kernel and ROM for tf300t.
Click to expand...
Click to collapse
Isn't this a problem? Do I need to downgrade first like the disclamer on http://forum.xda-developers.com/showthread.php?t=2407248 which is where I went to get the hairybean recovery in the first place. It said that I have to downgrade before trying to upgrade my recovery.
das chaos said:
PLZ read my last post again (I edited it).
So you are on the right (tf300t) bootloader. That is fine. But you have the wrong TWRP. So go on and flash the recommended recovery (TWRP 2.8.4.0) and try mounting again. If it works, you can wipe boot, system and data an flash a custom ROM of your choice. Report back. Good luck!
Click to expand...
Click to collapse
Is the tf300t bootloader compatible with my tf201? Would it be better to track down the tf201 bootloader?
Solved!
Thank you so much!
I didn't entirely do what you directed me to but what you said set me on the path to fixing my problem.
First, I downgraded hairy bean with the downgrade zip at http://forum.xda-developers.com/showthread.php?t=2407248
This took me back to the twrp I had prior to installing hairy bean (which was actually 2.4.3)
I restored my original back-up.
After completing, I restarted the tablet and it started up the original Cyanogenmod 10.1-20140217-nightly-tf201
This will work for now. Another weekend I may give it another try but I'm too relieved to go for it again. My bluetooth will probably still not work so I'll likely be in the market for another new ROM soon.
Huge thanks for your quick response and your suggestions!
aamcc
aamcc said:
Thank you so much!
I didn't entirely do what you directed me to but what you said set me on the path to fixing my problem.
First, I downgraded hairy bean with the downgrade zip at http://forum.xda-developers.com/showthread.php?t=2407248
This took me back to the twrp I had prior to installing hairy bean (which was actually 2.4.3)
I restored my original back-up.
After completing, I restarted the tablet and it started up the original Cyanogenmod 10.1-20140217-nightly-tf201
This will work for now. Another weekend I may give it another try but I'm too relieved to go for it again. My bluetooth will probably still not work so I'll likely be in the market for another new ROM soon.
Huge thanks for your quick response and your suggestions!
aamcc
Click to expand...
Click to collapse
Glad I could help you, even when you reverted to a stone age ROM; this is J for Jelly Bean and now we have L for Lollipop; and that is running really fast on tf201.
das chaos said:
Glad I could help you, even when you reverted to a stone age ROM; this is J for Jelly Bean and now we have L for Lollipop; and that is running really fast on tf201.
Click to expand...
Click to collapse
Yeah, I definitely think my tf201 is laggy in a lot of places it shouldn't be and there are some bugs I'm not a huge fan of. If you have one off the top of your head or easily accessible, I'd be interested to be directed to a thread that would get me updated to lollipop. I'm a tad gun-shy to pursue ROMS I find on my own after what felt like a near miss with this fiasco.
aamcc said:
Yeah, I definitely think my tf201 is laggy in a lot of places it shouldn't be and there are some bugs I'm not a huge fan of. If you have one off the top of your head or easily accessible, I'd be interested to be directed to a thread that would get me updated to lollipop. I'm a tad gun-shy to pursue ROMS I find on my own after what felt like a near miss with this fiasco.
Click to expand...
Click to collapse
If you want to lollipop, you should read that:
http://forum.xda-developers.com/transformer-prime/help/katkiss-t2961256
Just an updat in case anyone stumble on this, I followed the thread supplied by daschaos and successfully installed katkiss.
Thanks for the help!
Sent from my TF201T using XDA mobile app
aamcc said:
Just an updat in case anyone stumble on this, I followed the thread supplied by daschaos and successfully installed katkiss.
Thanks for the help!
Sent from my TF201T using XDA mobile app
Click to expand...
Click to collapse
Have fun and don't be shy to ask in case of trouble.
Hi Everyone,
I unlocked the bootloader a while back, planning to root and install 3rd party roms, but I never ended up doing that.
I only played around with removing "Unlocked Bootloader" message, and that's all. It took a trip to Motorola and came back once, is it possible they removed recovery?
Anyway, is there anyway to revive the device? It boots fine but I am having issues with google play store, it keeps crashing so I wanted to do factory reset, that's when I realized that recovery is missing.
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
PseudoDev said:
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
Click to expand...
Click to collapse
Hi, it went to motorola because the SIM slot pins were bent, of course it came right back with a little note "sorry, bootloader unlocked, we won't fix it" basically bootloader unlocking also voids all physical/mechanical warranty as well, I understand, I shouldn't have unlocked the bootloader on day 1 and get the sim slot messed up on day two, ended up with $50 paperweight.
Thank you so much for the suggestions, I don't want to mess it up more than it already is.
It's a CDMA+GSM edition, supposedly identical to Verizon model. I think I already have adbfastboot, I should be safe following this video here, unless you have any other suggestions
https://www.youtube.com/watch?v=R4c0fO8Kr_Q
Thanks again.
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
xpmule said:
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
Click to expand...
Click to collapse
Thanks, I managed to get TWRP to work on the device using ADB Fastboot, and I got the phone rooted. I removed the old Google Play store manually, restarted, and then installed it from apkmirror, and now everything seems to work just fine, but somehow I think stock recovery image is gone, I don't think I have the factory image anymore.
I checked around but couldn't find it, would you happen to know what is the stock rom for XT1526?
Thanks.
Like i was saying just look it up as per your model number..
And glad you got it working.. that is all that really matters.
Plus that screen that shows the Droid Operation with the words "no command"
that is the stock recovery.. if you installed TWRP you should never see that booting recovery.
See what i mean ?
So check this page.. it's where a lot of us got our Firmware from.
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
But research your phone model first and see what people are saying.
Mine has a tab of little plastic cover paper that pulls out that shows my Model number.
Or get it from the bootloader screen then look around using search to see what people are saying.
Some of them have restrictions.. and some are GSM versions which are a bit different.
I am not too familiar with your phone version but i Google'd it and i see Sprint & Boost coming up..
Such as this topic..
http://forum.xda-developers.com/moto-e-2015/general/moto-e-2015-cdma-sprint-xt1526-custom-t3241117
Basically i don't want to say hey go flash firmware then see you have problems
And all i did was go to that Firmware page and search for the model number
by hitting ctrl+F with Firefox then cycle through them.
There is a few of them.. that follow a file name format.
XT1526_SURNIA_ACG_5.1
ACG would be the region part of it or provider such as Boost
So that page has 16 versions of Lollipop for your model number.
What i would do is ask guys on the firmware topic what one they used.
This is where i got the Filefactory link on post one (you can look in the Mega links too)
http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235
I would search through that topic and ask on that topic what others used.
Then search around the forum (General section or maybe help section) and then with Google too.
For example, i googled this "XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.8_cid9_subsidy-DEFAULT_CFC.xml.zip"
And it showed this topic..
http://forum.xda-developers.com/mot...nt-version-t3052844/post64438539#post64438539
Research.. better safe than sorry LOL
Thanks for all the info, sometimes was messed up because phone received an update from Google and when it attempted to update, it got stuck in recovery (would not update). Was there a notice somewhere that we shouldn't update the phone? Anyway, it kept trying to reboot the phone after it turns on but it gets stuck at TWRP and won't update.
I was able to get into the settings and wipe the phone, now I am trying to go through set up again, but I think my best bet is to flash stock firmware and start over. Next time instead of trying wipe, I can just reflash stock firmware over it.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.