Hi everybody,
when trying to install a custom ROM (PAC Nightly) on the TF201 to upgrade it from the stock 4.1.1, I first rooted and unlocked it and installed TWRP 2.6 and did a full backup.
Then I wiped Dalvik, System and Cache.
However, PAC did not get past its boot animation and when I tried to restore the backup from before, the tablet is stuck at the ASUS-Boot Logo (with "Device is unlocked" notification).
I am not sure what to do now. as the title says, TWRP still works and it does show up in fastboot.
Thanks in advance.
/e: I do have the impression that it was a lot easier on my Nexus S. :-/ The question is: is something broken and I have to try the unbrick solution or can i fix it by creatively wiping everything and just install some other ROM?
Well, another try and it worked. Strange. Phew.
Oh, brilliant. Now I have some questions about the ROM itself but may not post it inits thread. :|
If someone accientally reads this: I have no sounds (ring, notification etc), however they are displayed in the list.
Sound itself works, tested in the YT-app. Keybord clicks also.
Is this a matter of the PAC ROM or...well, where are they stored anyway? I suppose the files are floarting around the internet somewhere.
Related
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
Hi guys, so i decided to install the new CM10 so i already had root, i unlocked using the official tool, then installed CWM from Rom manager.
I then downloaded CM10 and GAAPS and kept them in a folder and also copied them to an sd card for safety.
I booted into CWM sucessfully, took a deep breath, then did a full wipe/factory restore, then wiped Cache, then wiped Dalvik Cache.
Then i proceeded to TRY to flash CM10.......... Firstly, CWM didn't list my external SD Card so i selected from the one i had saved on the internal storage.
It began to do the install then failed stating something about symlinks??? I retried the install and got the same thing.
I rebooted the Prime and now it's just stuck on the Eee Pad splash screen with "The Device Is Unlocked" written in the top left corner and it wont do anything else.............
I can reboot into CWM but how can i fix this and get CM10 installed??
PLEASE help!?!?!?!?!?
Thanks in advance.
Currently, no recovery can access external memory of any sort. Did you make a backup? Is it in the internal memory? Make sure you can flash back to your original settings BEFORE trying to flash something as experimental as CM10.
Please remember any Jelly Bean roms are highly experimental, and probably won't work correctly for everyone.
Read this thread for more help:
http://forum.xda-developers.com/showthread.php?t=1514088
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
Good to hear. One last advice is to use TWRP instead of CWM. CWM has issues with the prime while TWRP is more stable.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
so how many time had u gone back then tried it.... i have the same problem i tried it like 10 times but it still stuck
what step did u do
I'm stuck in the same predicament! Did you just keep trying, and it finally worked????
I've got a Galaxy S III and it worked more than perfect before I decided to get the JB update in Kies. Now the physical buttons happen to freeze all the time (the phone itself works), if the screen is on, I can touch everything, apps work, but back/home/menu/screen off don't. It's terribly frustrating to have such an expensive phone and having such an experience with it.
Anyway, I flashed from Sammobile every possible stock ICS and all of them get me stuck in the splash screen as if it's soft bricked, and ALL the stock JBs have the same button problem. Now I thought to myself the only way to go is CM.
The question is: how to I install CM (9, 10 whichever!) over my JB? Or better still (although I gave up on it) how do I get back to the good old flawless stock ICS?
Thank you in advance!
It's basic. Install a recovery, then grab your desired Rom (cm10 or whatever) then backup your apps with Titanium, and reboot in recovery, wipe all partitions (data, cache, dalvick, system) then flash your room, bit and restore your apps.
I did just that, but I get error status 7 when flashing with every version of CM10 i downloaded. When I googled the error I saw it has to do with the kernel not matching the ROM or something...
Strange as kernel provided with Rom is designedto work with. What version of cwm are you using? Try with twrp recovery.
I noticed I didn't have the last version of CWM so I installed it but got the same error. Then I tried TWRP and it worked like a charm! I especially like the touch version. Thanks a lot for your advice, help and everything!
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!
Hi
So I rooted my Gioneed Gpad G1 and CWM and everything was smooth until I got the idea of flashing a custom ROM using this idiot's post here
//needrom.com/mobile/gionee-gn800-custom-rom-leetsleek-v1-0//
So while I understand there is a probability that the phone would work perfectly are 50-50, mine falls in the unfortunate category.
I flashed the rom and the installation was succesful. However, upon reboot, my phone is stuck at the boot screen showing "Gionee". I can access the custom recover, and have tried cleaning cache, and the devlick cache, and formatting the phone. Nothing works.
Since this was my first experience with rooting, I had no idea about the nandroid backup, until I saw the posts later on, albeit too late.
So, my question is, is there any remote possibilty that I can get my phone back in working condition? Any kind of response would be appreciated.
PS: I write under this forum since paranoid android is one the best custom roms there is, and unfortunately, neither this nor any other rom is available for Gionee.