Related
Hello everyone,
My problem is this: I wanted to install a CM10 nightly on the device, so I root using the DebugfsRoot method, install rom manager, flash a recovery, try to install a ROM and it did not work. Rebooting into recovery got me the red triangle, but using the volume buttons allowed me to get in (only it did not have the option to install updates or anything. I think it was just he mounting and partition options)
Since I did not unlock the device before doing this, I chose to do so using ASUS's unlock utility. Once done, I tried booting into recovery, but the device would be stuck at "booting recovery kernel image" and won't budge. I tried flashing different version of CW but it did not seem to work.
Finally, for some reason, I chose the "wipe data" option from the bootloader and the device was stuck, again, at "booting recovery kernel image", only this time I can't boot into a ROM nor can I boot back into bootloader.
What happens when I boot using power and volume down is this:-
The device is Unlocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel image
and then everything's stuck.
Booting normally makes the device stop at "the device is unlocked" message because, I assume, there is no ROM flashed into the device.
Thanks for helping in advance.
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
ShiroiKage said:
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
Click to expand...
Click to collapse
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
buhohitr said:
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
Click to expand...
Click to collapse
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
ShiroiKage said:
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
Click to expand...
Click to collapse
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
okantomi said:
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
Click to expand...
Click to collapse
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
ShiroiKage said:
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
Click to expand...
Click to collapse
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
buhohitr said:
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
Click to expand...
Click to collapse
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
ShiroiKage said:
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
Click to expand...
Click to collapse
You can't install the ASUS firmware through custom recovery. It has to be stock. I believe there are signature checks that prevent it from installing otherwise.
Sent from my ASUS Transformer Pad TF700T
did you unzip the file? should be a zip within a zip. you flash the zip inside
lafester said:
did you unzip the file? should be a zip within a zip. you flash the zip inside
Click to expand...
Click to collapse
You know, I unzipped the file the first time I installed it to get Clean ROM to flash, I had the unzipped folder there yet I managed to forget to use the unzipped file. /InfiniteFacePalm
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
srk10 said:
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
Click to expand...
Click to collapse
not sure but it can be possible that some partitions are damaged.
run the latest ruu to restore all the partitions.
twrp 2.5.0.0 have some problems with custom roms,
try twrp 2.3.3.0, it seems that this version has mostly no problems with flashing roms.
do not forget to flash the boot.img after flashing the rom or you will get a bootloop.
before flashing a rom wipe 3x system 3x data 3x cache to be sure that your phone is clean of old system stuff.
here is the link for twrp 2.3.3.0
https://www.dropbox.com/s/pvspwkekl42zkqa/openrecovery-twrp-2.3.3.0-ville.img
Thanks so much for the reply. I downgrade to twrp 2.3 and managed to use the windows utility to reformat my sd card. Wasn't sure that wasn't going to shoot me in the foot, but it worked and I am back in business with a phone that boots.
Hi, I unlocked my TF300T sotck ICS 4.0.3 with the Asus app, I flashed CWM and the root_signed thingy without a problem. I then did a data wipe, cache and dalvik wipe and flashed CM10 stable build for TF300T and the Gapps zip. I reboot and it's stuck on ASUS screen. I'm currently doing a restore of the "nandroid". Will this restore my tablet to ICS? What did I do wrong? How do I get either Cm10 to work or return to the ICS? Also, if I need to flash something else, how do I do it? Does the CWM recognize msd cards? Because all I have on the internal memory is the CM10 which currently did not work for me. I'm a little desperate right now. Thanks.
EDIT: DAMN IT, I just got an error restoring data. What the hell do I do? Please!
i tried restoring again and reflashing cm10 and the gapps and still nothing changes. I did wipe again the caches and still nothing. Also I can't download other roms to the tablet because my computer doesn't recognize the tablet because it hasn't booted and the cwm won't recognize micro sd cards. So I think flashing something else isn't an option. Did I break my tablet completely? I'm almost in tears
I tried several things due to some searches on different forums but nohitng works. I tried wiping caches and reflashing Cm10, didn't work. I tried pluggin my tablet to my computer and sending the asus stock rom via ADB and flashing that, but CWM gives me an "installacion aborted" error. I just don't know what to do nor I understand what went wrong. I did everything according to multiple tutorials. Unlocking, flashing CWM and rooting went just fine. But installing CM10 ended up pretty much destroying my tablet. I wanna kill myself.
I think you have a brick??!! :'( cm10 is jellybean and you where on ics and you probably didn't flash the jellybean bootloader did you?
Sent from my ASUS Transformer Pad TF300T
Not a single tutorial said that I had to do that. Every tutorial says "unlock bootloader, flash cwm, flash root_signed, flash cmrom". I did just that. Are you telling me that my tablet is lost forever?
in most cm threads (except cm9) their is stated that you atleast need android 4.1.1 with it's bootloader or 4.2 with it's bootloader, what i suggest you try is to flash a bootloader and upgrade staight to 4.1.1 you can download the firmware from asus the links are on this guide: http://forum.xda-developers.com/showthread.php?p=39272826 FOLLOW THIS GUIDE CORRECTLLY OR YOU MIGHT PERMANENTLY BRICK YOUR TABLET!!!!
EDIT: if you get an error during flash it's probably the drivers or a fastboot flash brick wich is only fixable by replacing the motherboard!!
Sent from my ASUS Transformer Pad TF300T
If what you say is true, then you can't flash CM10 on a stock ICS tablet, and that goes against every freaking tutorial I've read before messing with my tablet.
What exactly is your bootloader version?
Sent from my ASUS Transformer Pad TF300T
I'm not sure what my answer is. The "bootloader" was unlocked by the Asus app from their website. I did that by downloading (I believe it was V7) the apk from their website and installing that and unlocking the tablet. From there on, I just followed did fastboot flashing CWM and rooting. I never read a tutorial that said "you should flash JB bootloader before installing cm10". In fact I thought that just by unlocking the tablet, rooting and flashing the custom recovery one could just install a custom rom regardless of wether it's JB or not. It's funny because I didn't want to upgrade to stock JB because it seemed buggy from a lot of reviewers, and CM10 was the classic option to have JB and a lot of great features and speed. So I google time and time again how to flash CM10 on a ICS stock ASUS. I just followed the tutorials for that.
is my tablet unrecoverably bricked? I also tried fastbooting and "flash system blob" with the blob for the ICS 4.0.3 firmware, after a while of "sending" the file in the command prompt, I got a blue progress bar in the fastboot screen on the tablet and then "FAILED". So I guess that doesn't work either.
Nothing will work?
Try entering fastboot reboot: does your tablet reboot or does it hang?
cm10 is android 4.1 it seems logical that it only runs on a 4.1 bootloader and not on an ics one! most posts must have said that you atleast need jelllybean 4.1.1
I was confused in the beginning aswell because my phone accepts any rom no matter what bootloader version!
Sent from my ASUS Transformer Pad TF300T
If it makes so much sense that CM10 with JB 4.1 only boots with the JB bootloader, then how the hell one can go from ICS to CM10?! Google tutorial flash cm10 on asus tf300t stock ics and you'll find a thousand tutorials not one of which says you need JB bootloader. I mean, I assume one could upgrade to the official JB rom and then unlock bootloader, etc, but I'm telling you, every tutorial that said "stock ics to cm10" did no mention the bootloader version issue. I'm not trying toblame anyone other than myself for "bricking" my tablet, but I read so many tutorials to ensure I wouldn't mess it up that I'm very upset about this.
I can use fastboot and adb commands. But I haven't been able to flash the ICS stock rom so far. First of all, it's not on the Asus website anymore, and the one I got from the web gave me this error on CWM "instaling update.. installation aborted". I also tried flashing the .blob via fastboot and it also failed. It seems nothing works. Any thoughts, anyone?
philos64 posted links to some old ICS ASUS firmwares in this post:
http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Maybe worth a try ? Never been on ICS myself - just thought I'd mention this source...sorry for wasting your time if this is what you already tried.
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
samus88 said:
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
Click to expand...
Click to collapse
We would like to know what bootloader you now have. You use the bootloader menu to get to cwm. Tell us how many ICONS you have and what they are. This way we will have more info to consider options if any.
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
samus88 said:
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
Click to expand...
Click to collapse
I reread the thread and I believe I would make a blob with just stock recovery (4.03) to match your bootloader. I know fastboot is failing on a complete blob but may process something as small as recovery. The blob could also be pushed to your tablet with adb and flash with that.
I made these choices as a place to begin since we need to match your bootloader.
Once stock recovery was in place we could use adb to push a once unzipped stock firmware (4.03) and get stock recovery to install it for us.
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
samus88 said:
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
Click to expand...
Click to collapse
With stock recovery in place go into bootloader and pretend you are going into cwm that activates stock recovery now. If android lays down we'll rename the zip to EP201_768_SDUPDATE.zip and try again.
I'll download 4.03 and make the recovery blob tomorrow so we'll be ready.
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
samus88 said:
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
Click to expand...
Click to collapse
No, there is the full blob in the factory firmware and that is what I'll use. It only takes a couple of minutes to extract the recovery image file which might flash and then re-blob just the recovery partition.
Downloading takes longer than everything else.
Update:
This zip contains stock 4.03 recovery as a blob and as an image file.
Unzip and try flashing the blob - if it fails try flashing twice more or until success. If it still fails try flashing the image file - three times if it fails.
Note:
These are to be flashed with fastboot or adb, not cwm.
Great, thanks man. Unfortunately, I won't have my tablet until at least wednesday because of the holiday on my country (independence day and such). But I'll give it a try and get back to you.
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.
So finally took the plunge and flashed Cromi-X 5,2,2. Current set up is bootloader 10.8, TWRP 2.5.0 unlocked and rooted. I was running fine for a couple of days and decided to try cromi control to turn of a couple of notifications.I didnt reboot from cromi control as I read there was a bug. I powered off using the power button and when powering back on I was stuck on boot animation. Options I chose on the original flash was _thatv4 10.8 with defaults. No ET / OV / OC / No tweaks. So i decided to dirty flash 5.2.2 again without formating data I got to upgrading apps and when it rebooted, back stuck on animation. I am going to try flashing my original stock asus nandroid.prior to 5.2.2 just to get it working for the evening.
Doing a search of the thread now... See this has been covered on 5.2.1. I may have to wipe / format data IDK
Any suggestions?
Thanks
Update
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
It is always good to have the latest bootloader and TWRP. What is your firmware or bootloader now? What do you want to achieve or usage on your device? _that v7 on Cromi X is a nice combo with speed and stability...
GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
Glad you got it working again. It's strange - what happened is typical for rebooting from the Cromi app, but you didn't.....
Did you do a factory wipe in TWRP before installing CROMi-X?
Also, it certainly wouldn't hurt to update your recovery. Just flash the bootloader/TWRP package in the CROMi-X OP and reboot to system.
My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!
GPWILL said:
My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!
Click to expand...
Click to collapse
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:
LetMeKnow said:
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:
Click to expand...
Click to collapse
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.
GPWILL said:
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.
Click to expand...
Click to collapse
I think that it would fine since you are running TWRP 2.5. Please be careful when you install custom recovery and bootloader. If you make a mistake, it could brick your device, just my two cents.. Please ask a lot of questions to be sure...
Note: From your TWRP 2.5, install 10.6.1.14.10 first and reboot so the blob can update your bootloader. When it boots into the system, then you need to reboot it back into your TWRP 2.5 and install the TWRP 2.6.1.0. When it is done, then you need to shut it down and use your power button and volume down to boot back into your new TWRP...Good luck..:fingers-crossed:
Always check your download "MD5 Sum" to verify that you have a good download....
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
I never use the method from cromi thread but I trust sbdags as a great developer and so many users used this method without a problem...
If you are still running stock firmware version 10.6.1.14.8, then you still can use goomanager to update your TWRP... If you prefer it that way, then goo still works for you...If you are on stock version 10.6.1.14.8, you are already on the latest bootloader unless you want the latest stock firmware V14.10 which you will update it with Cromi any way...
1. Use goo to update the correct TWRP, 2.6.3.0 or 2.6.1.0
2. Boot into your new TWRP and install the Cromi and follow the instructions that I wrote earlier
Good luck..:fingers-crossed:
GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
Not quite.
You cannot flash BL or TWRP separately from that package. It's either both or none.
But flashing the package would be the easiest and safest method to get you on a current recovery in my opinion.
GooManager: For a few weeks now Goo did not support flashing recoveries anymore. I've read it often enough that I consider that information confirmed - although I have not tested it myself.
Now - just yesterday I read a post where a user reported that Goo got an update and he flashed TWRP successfully. That's one report I know of - if you want to give it a try, go for it. It can't hurt.
The thing is, to use GooManager you have to root the stock rom you are running.
I don't know if the stock rom you are running is rooted, but why bother if you can just flash sbdags package??
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
Well goomanager didnt work for me. Just sits on "downloading" forever. only option was to upgrade to 2.6.3.1
Off to get fastboot working..
GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
_thatv7 is one of the kernel choices - changing a kernel does not do anything to the bootloader.
Look at these elements of the system as parts of an engine: If the bootloader is the starter motor, the kernel may be the distributor.....
Thanks for trying Goo, the score is 1:1
Anyway, to get fastboot working is worth the effort. It's great for troubleshooting or pulling logs and such. It's very helpful to have a working fastboot connection BEFORE you run into some trouble and really need it to work
I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.
GPWILL said:
I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.
Click to expand...
Click to collapse
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk
berndblb said:
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...
GPWILL said:
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...
Click to expand...
Click to collapse
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...
LetMeKnow said:
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...
Click to expand...
Click to collapse
It is running pretty nice. Stock browser and Chrome are a little faster than my stock setup with B2R. I have had a few " laucher has stopped" errors. This happened before I installed any apps with thatV7. Didnt get a single laucher error before on thatv4. Stock laucher. Nice and smooth on apps and such. Both stock browser and chrome are faster but not anything like "WOW". Just a little better. Nice to have it built in. I am going to give this a few more days and see if the laucher errors settle down. If it stablizes I will get another nandroid of it and try the ROM2SD to see if I can get the wow factor going.