Hi people,
I need your urgent help!
My TF201 was running on hairy rom.
I wanted to update/change to CM10 latest nightly (I really dislike the asus crap).
I tried several times via TWRP and goo manager but it would boot up (only saw the asus logo).
Then I thought it might have been the recovery.
I booted in fastboot mode and flashed CWM (recovery-clockwork-touch-5.8.1.8-tf201.img and md5 was correct).
Looked fine.
Then I wanted to reboot into recovery but it simply did not.
Tried it 5/6 times but nothing.
So I booted up again in fastboot mode and flashed the latest TWRP (2.3.3).
Again I rebooted to recovery but it still failed.
I do not have NVflash because I bought this device 2nd hand and it was allready upgraded to JB bootloader so I could us NV.
Is my device bricked? Is there a way to solve this?
Please help me but keep in mind, I'm a "noob" (do know stuff but not very much).
Thnx in advance!
Ralph aka TwistedNL
Re: [Q] Help! can get in recovery!
I'm not sure but it sounds a little like you flashed rom for ics bl but I'm not sure as ypu can still get to recovery and fastboot. Btw post questions to Q&A!!!
Edit: What version of hairybean were you running? And did you wipe?
Sent from my sgs2
Makrilli said:
I'm not sure but it sounds a little like you flashed rom for ics bl but I'm not sure as ypu can still get to recovery and fastboot. Btw post questions to Q&A!!!
Sent from my sgs2
Click to expand...
Click to collapse
I can get in fastboot mode but can't get in recovery mode. The latest nightlies are JB roms right?
If I can get in recovery, I could restore nandroid I made before starting this journey.
Could the custom build TWRP version from hairy be the reason? As far as I know, the only difference are cosmetics (othe backgropund and buttons, like a theme)
Sorry about the wrong section for my question. Am to pissed atm so I did not look good where I should have asked this.
Can my question be moved by somebody?
Re: [Q] Help! can get in recovery!
Well I don't know about the CM10 nightlies. But most likely that custom twrp didn't do it. I'm not an expeet in any of this stuff. Also what happens when you go to recovery? And only mods can move threads to another section
Also I edited my first post but ypu answered too quickly What version of hairu bean were tou running and did you wipe when you flashed cm10?
Sent from my sgs2
twistednl said:
Hi people,
I need your urgent help!
My TF201 was running on hairy rom.
I wanted to update/change to CM10 latest nightly (I really dislike the asus crap).
I tried several times via TWRP and goo manager but it would boot up (only saw the asus logo).
Then I thought it might have been the recovery.
I booted in fastboot mode and flashed CWM (recovery-clockwork-touch-5.8.1.8-tf201.img and md5 was correct).
Looked fine.
Then I wanted to reboot into recovery but it simply did not.
Tried it 5/6 times but nothing.
So I booted up again in fastboot mode and flashed the latest TWRP (2.3.3).
Again I rebooted to recovery but it still failed.
I do not have NVflash because I bought this device 2nd hand and it was allready upgraded to JB bootloader so I could us NV.
Is my device bricked? Is there a way to solve this?
Please help me but keep in mind, I'm a "noob" (do know stuff but not very much).
Thnx in advance!
Ralph aka TwistedNL
Click to expand...
Click to collapse
There is not a version of CWM that is for the Jellybean bootloader. The quickest way to hard brick your device is to install a recovery meant for ICS onto Jellybean bootloader.
If you can still access fastboot then you have a chance, if you cannot still access fastboot then I'm sorry but flashing CWM has hard bricked you.
Then I'm a lucky bastard!
Managed to reflash stock TWRP (without the theme).
After 2 times flashing, I could boot in recovery again. The nandroid was copied to external SD which I could restore and the Prime is running again!
I think I'll keep it on Hairy (which runs fine on 1.7 kernel) and will wait to the promised update (around november 2012) of Asus to 4.2 cause I really like the multi user option
Thnx all for helping me out!
Related
Hi all,
Some background information, I was using team eos nightlies and I wanted to change the rom to see whether if others are any better, so i did cleared the cache/delvik cache and as well as did a factory wipe. Then i installed the the that I wanted to try out, the Energy rom, however, after flashing, I couldn't get past the asus spalsh screen, I can still go back to the twrp recovery though.
I tried flashing back my original team eos nightly.. and it booted without any problem.
Anyone knows if i'm missing any step to flashing a new rom?
ZeitiaX said:
Hi all,
Some background information, I was using team eos nightlies and I wanted to change the rom to see whether if others are any better, so i did cleared the cache/delvik cache and as well as did a factory wipe. Then i installed the the that I wanted to try out, the Energy rom, however, after flashing, I couldn't get past the asus spalsh screen, I can still go back to the twrp recovery though.
I tried flashing back my original team eos nightly.. and it booted without any problem.
Anyone knows if i'm missing any step to flashing a new rom?
Click to expand...
Click to collapse
Sounds to me like your on the older ICS bootloader and the other roms you've tried are using the JB bootloader (lucky you havnt bricked your device)
You need to upgrade the Bootloader first in order to install these roms but BEWARE, once you upgrade the bootloader, you cannot go back to the ICS bootloader or roms.
Unless you have backed up NVFlash and you restore your device/bootloader with NVFlash.
Now would be a good time to do your NVFlash backup if you havnt already, then go from there.
Click the link for a guide on upgrading the bootloader by Flumpster in the Androwook thread ... there is also a link for the NVFlash guide
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212
Danny-B- said:
Sounds to me like your on the older ICS bootloader and the other roms you've tried are using the JB bootloader (lucky you havnt bricked your device)
You need to upgrade the Bootloader first in order to install these roms but BEWARE, once you upgrade the bootloader, you cannot go back to the ICS bootloader or roms.
Unless you have backed up NVFlash and you restore your device/bootloader with NVFlash.
Now would be a good time to do your NVFlash backup if you havnt already, then go from there.
Click the link for a guide on upgrading the bootloader by Flumpster in the Androwook thread ... there is also a link for the NVFlash guide
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212
Click to expand...
Click to collapse
Ohhh is it. I don't remember anything about the bootloader so I just assumed that since I was on TeamEos JB nightlies, then I'm on JB bl.
I went to flash many other roms to tried too. Must've been really lucky then.
Thanks for the help, I'll go try it out.
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Twinning92 said:
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Click to expand...
Click to collapse
CWM is not compatible with Jellybean. Unfortunately you are hard bricked.
Why didn't you make a backup with NvFlash? If you did that you could restore your tablet.
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Manneman32 said:
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Click to expand...
Click to collapse
You didn't mention the version of Philz you were using. Anyway, the error 7 can be caused from 2 main reasons:
1- Older recovery version. Flash the lastest recovery available (6.15.4) and try again: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300
2- Corrupted rom download.
To your 2nd question- if it doesn't work with Philz, it will not work with any other recovery.
Well... when I asked about how to go about rooting just a week ago I got links to what I needed. And with that I got a link to Philz Recovery. But now I see that it was an old version (6.07.9)
I´ll try with the latest one and see where that takes me.
Edit:
Flashed the latest Philz and took a new backup just in case. It didn´t work. Still Status 7. So I re-downloaded the ROM just in case it was corrupted but still the same... aborted Status 7.
So... now what? Am I screwed?
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Manneman32 said:
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Click to expand...
Click to collapse
Worth the try
Here 2 relevant threads I found:
http://en.miui.com/thread-6429-1-1.html
Follow galnet post (page 7):
http://forum.xda-developers.com/showthread.php?t=1749392&page=7
Sent from my GT-I9300 using Tapatalk
So... the links refer to downgrading to a really old recovery used for rooting with CF or unticking the "disable signature check" ... feels strange.
Is there anyway to explain why this error occurs?
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Manneman32 said:
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Click to expand...
Click to collapse
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Hi, Guys.
I was trying to upgrade to a JB ROM, so I started following threads here and there. I got that I need to upgrade my bootloader to a JB one, since I still have the ICS Bootloader, and that I must have a TWRP Recovery (I still have Clockwork Touch).
I finally found a package containing both, so I flashed it. I have afterwords realized that it was for tf300 and not tf201.
My tablet is now stuck at Eeepad logo, but I can still access clockwork recovery holding power+volume down. I can't actually power off the device, 'cause it keep rebooting so I'm basically suck in the recovery. Tried do restore a nandbackup, but it does't boot because I have the wrong bootloader I guess. I've tried to find the correct JB bootloader to flash it, but all the links I've found are broken, so I actually can't do anything. I'm terrified to run totally out of battery (I don't know if it's charging or not at the moment) so I need to fix it ASAP.
Has anyone a link to the correct bootloader to flash? Do I need to change recovery? If so, why? How?
Can anybody post a link to the Androwook 1.3 rom release? It seems that it has the JB bootloader included, but I can't find it anymore.
Thank you very much!
Solved with the rom linked in the second post from this thread:
http://forum.xda-developers.com/showthread.php?t=1803557
Cheers.
Total newbie to all this. First time I've unlocked or rooted android.
I unlocked using the Asus unlocker. Rooted with motochopper. Then I installed fastboot and nvflash and flatline. Messed up here as I was planning to install CM11 and when I tried to install the ROM it failed. Should have read the small details. Soft bricked my tf201 and could only use apx.
Used nvflash to recover to stock jb. Re-rooted and tried to install CWM. Didn't work recovery would freeze in the loading recovery image. But I could still just boot normal into my device. Tried TWRP and had the same problem.
How do I get the recovery to work. Do I need to go back to the stock image and try all over again?
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
JoanneDisFan said:
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
Click to expand...
Click to collapse
Can you put SOLVED in the title of the thread..
Thx Josh