Hi,I have a transformer prime which was running on Energy Rom ICS 4.1.
Yesterday I thought of updating it to Energy JB rom.
The post said it needs updated bootloader as well so I downloaded the bootloader package (TWRP 2.5) but did not know that it formats the tablet completely.
So I flashed it but when it restarted the tab I saw Asus logo & blue progress bar & on top left it said formatting internal storage so I forced shutdown the tab by keeping power key pressed.
But now I am unable to install any ICS rom as it flashes the rom but gets stuck on the boot animation.
I tried installing Energy JB & Androwook JB rom but has lot of force close issues, camera doesnt work.
I tried installing TWRP 2.5 using fastboot but my laptop says usb device not recognised.
Downloaded naked universal usb driver but dont know what to do with them as there is no setup (exe or msi) file in that zip.
I even tried flashing older ics version of bootloader & repeated the whole procedure but doesnt help.
PLEASE HELP ME OUT. I CANNOT POST IN THE ENERGY ROM'S POST AS IT DOESNT ALLOW ME
ergauravpro said:
Hi,I have a transformer prime which was running on Energy Rom ICS 4.1.
Yesterday I thought of updating it to Energy JB rom.
The post said it needs updated bootloader as well so I downloaded the bootloader package (TWRP 2.5) but did not know that it formats the tablet completely.
So I flashed it but when it restarted the tab I saw Asus logo & blue progress bar & on top left it said formatting internal storage so I forced shutdown the tab by keeping power key pressed.
But now I am unable to install any ICS rom as it flashes the rom but gets stuck on the boot animation.
I tried installing Energy JB & Androwook JB rom but has lot of force close issues, camera doesnt work.
I tried installing TWRP 2.5 using fastboot but my laptop says usb device not recognised.
Downloaded naked universal usb driver but dont know what to do with them as there is no setup (exe or msi) file in that zip.
I even tried flashing older ics version of bootloader & repeated the whole procedure but doesnt help.
PLEASE HELP ME OUT. I CANNOT POST IN THE ENERGY ROM'S POST AS IT DOESNT ALLOW ME
Click to expand...
Click to collapse
You messed up by forcing shutdown but I think you know that now..
The only thing I can suggest is if you can still use TWRP then first go to wipe menu and format data, wipe system, wipe dalvik and then wipe cache.
Now try to install your rom.
If this still does not work then try getting the downgrade.zip from the hairybean thread and flashing it in twrp and then restarting and letting it fill all the blue line this time.
At this point you should be able to install a 4.1.1 rom so just try Hairybean 1.51 for now doing all the same wipes as before.
If this works then go and follow the same Energy rom instructions before but without killing the install.
Thanks but I have allready tried that
Hi, I have already tried downgrading bootloader from both Energy Rom thread as well as Androwook thread.
TWRP is still working on my tab & when I flashed downgrade.zip from Hairybean thread,it says successful but does'nt ask for restart,even after rebooting from twrp menu,it again restarts into twrp & i tried androwook ics rom but gets stuck on bootanimation same as Energy Ics based rom.
Any advice????
ergauravpro said:
Hi, I have already tried downgrading bootloader from both Energy Rom thread as well as Androwook thread.
TWRP is still working on my tab & when I flashed downgrade.zip from Hairybean thread,it says successful but does'nt ask for restart,even after rebooting from twrp menu,it again restarts into twrp & i tried androwook ics rom but gets stuck on bootanimation same as Energy Ics based rom.
Any advice????
Click to expand...
Click to collapse
First of all please stop flashing things. You are mentioning ICS and Jellybean and the new bootloader and different versions of TWRP that are only compatible with certain bootloaders. You will brick it if you are not careful if you haven't already.
Power off and then hold down the power button and volume down the same time. You should get into the bootloader menu with icons.
At the top left of the screen there should be some writing with a long number.
Tell me what that number is please and also tell me what icons are on the screen.
flumpster said:
First of all please stop flashing things. You are mentioning ICS and Jellybean and the new bootloader and different versions of TWRP that are only compatible with certain bootloaders. You will brick it if you are not careful if you haven't already.
Power off and then hold down the power button and volume down the same time. You should get into the bootloader menu with icons.
At the top left of the screen there should be some writing with a long number.
Tell me what that number is please and also tell me what icons are on the screen.
Click to expand...
Click to collapse
Hi, every time I switch on my tablet now, it goes into TWRP by default, even on pressing power + volume down buttons it does not show me any icons but straightaway boots into TWRP, I tried installing Androwooks JB Rom (which was buggy before but atleast working), but it again reboots into TWRP recovery by default, I did all the wiping before installing as well.
When I power on my tab, all I see is ASUS logo in middle & on top left it says "device is unlocked", then straight into TWRP recovery.
I think I have screwed up big time.
Please help
Related
So as the title suggest, I am in a boot loop. I was running TWRP project 2.2.1.4 (I think or something like that) and downloaded the latest blob from TWRP's website (openrecovery-twrp-2.2.2.1-tf201-JB.blob) and booted into fastboot mode and flashed it through terminal. It said everything was good and I rebooted no problem. I hit the menu to reboot into Recovery (from the Power button menu) and it threw me into a bootloop at the startup screen. I can't get into recovery, but I think I'm able to get into APX mode. I have gone through the entire procedure of nvflash and have everything backed up numerous times... Any ideas on how I can get my Prime back up and running? I currently have Androwook JB edition installed and was about to install the latest deodexed stock ROM listed in the Development section.. Please help.
andrewjt19 said:
So as the title suggest, I am in a boot loop. I was running TWRP project 2.2.1.4 (I think or something like that) and downloaded the latest blob from TWRP's website (openrecovery-twrp-2.2.2.1-tf201-JB.blob) and booted into fastboot mode and flashed it through terminal. It said everything was good and I rebooted no problem. I hit the menu to reboot into Recovery (from the Power button menu) and it threw me into a bootloop at the startup screen. I can't get into recovery, but I think I'm able to get into APX mode. I have gone through the entire procedure of nvflash and have everything backed up numerous times... Any ideas on how I can get my Prime back up and running? I currently have Androwook JB edition installed and was about to install the latest deodexed stock ROM listed in the Development section.. Please help.
Click to expand...
Click to collapse
Follow these steps... http://forum.xda-developers.com/showpost.php?p=32535307&postcount=2
Then install TWRP for JB & flash the ROM...
I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Official CM10 nightlies are still made for the ICS bootloader, as you discovered. Until they update, you're better off downloading the unofficial builds here.
thefsfempire said:
I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Click to expand...
Click to collapse
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
foxhound08 said:
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
Click to expand...
Click to collapse
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Voyager2k said:
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Click to expand...
Click to collapse
No i can't access anything.
foxhound08 said:
No i can't access anything.
Click to expand...
Click to collapse
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
dunngh said:
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
Click to expand...
Click to collapse
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
eec_ said:
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
Click to expand...
Click to collapse
same here as well so at least you guys arent alone does show up as an apx device but not sure how useful that could be at the moment its just a paper weight just need someone to write an automated recovery from apx mode to flash the appropriate files if thats even possible
Exact same problem. Still no fix?
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
swatsbiz said:
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
Click to expand...
Click to collapse
Your problem was different to theirs and you have been fixed in the Androwook thread. Yours was caused by the pad firmware not installing properly the first time and freezing your screen and buttons.
I have the same problem...
hbhorat said:
Exact same problem. Still no fix?
Click to expand...
Click to collapse
any fixes to this ?
sraghav20 said:
any fixes to this ?
Click to expand...
Click to collapse
Me too.. looking for a fix on this with no luck so far
Hi, recently I Flashed my iconia a500 with cm10 jelly bean 4.1.2 bootloader v8. After one weel of awesome performance my tab is now dead, when I try to reboot it is stopping at the first screen from the bootloader without charging the os. In the recovery menu everithing is working perfect but when I try to reboot is always showing me the same : "skrilax_cz's bootloader v8 booting primary kernel image".
Could please some body help me?
Thanks!
momotizzati said:
Hi, recently I Flashed my iconia a500 with cm10 jelly bean 4.1.2 bootloader v8. After one weel of awesome performance my tab is now dead, when I try to reboot it is stopping at the first screen from the bootloader without charging the os. In the recovery menu everithing is working perfect but when I try to reboot is always showing me the same : "skrilax_cz's bootloader v8 booting primary kernel image".
Could please some body help me?
Thanks!
Click to expand...
Click to collapse
Something is wrong with the kernel boot in your setup. It can be anything, for example a weird looping script in init.d, corruption in the kernel partitin, whatever.
What I would do (I have a Iconia a500 in my household that I don't actively flash anymore) is the nuclear option: boot to recovery, wipe everything and reflash the rom. Maybe also refash the kernel if that isn't in the rom zip.
Zatta said:
Something is wrong with the kernel boot in your setup. It can be anything, for example a weird looping script in init.d, corruption in the kernel partitin, whatever.
What I would do (I have a Iconia a500 in my household that I don't actively flash anymore) is the nuclear option: boot to recovery, wipe everything and reflash the rom. Maybe also refash the kernel if that isn't in the rom zip.
Click to expand...
Click to collapse
HI Zatta, I reflashed different time some different rom and kernel but the result is not changing, I'm still in front of the starting screen but the rom is not charged. Any other suggestion? If I try to flash a new bootloader with nvflash is stop at the half of the procedure. Also if I try to restore an hold backup is not working. How can I fully restore the tab?
Ohoh, what made you think the bootloader was the problem?
Anyway, if you can boot to recovery, use that. Else, browse the forum to find help, for example in this thread :
http://forum.xda-developers.com/showthread.php?p=28777415
Taptalked u see .. əəs n pəʞlɐʇdɐʇ
I tried to reflash bootloader different time but no way. Now the Tab is start always/just in apx mode.
Any suggestion for a full reset or restore from apx mode?
You ****ed something up. Anyway, if your really can't boot into recovery anymore, follow this guide:
http://forum.xda-developers.com/showthread.php?t=1622425
and do the manual method. I hope you have saved you CPUID and SBK somewhere.. Further questions can better be asked in that thread also as I am not fully involved in that device anymore.
Hi there,
I downloaded the latest MIUI ROM available in the Development sectionand installed when i was on ICS, but it only booted and the BOOT.iMG was not flashed by fastboot because the hboot version was not sufficient for the MIUI jelly bean ROM. My phone was rooted earlier and i was running Sense Revolution 5 but after it was degrading i decided on installing your ROM.
Now, after long hours I updated the stock version via the OTA so the hboot version has now increased. But the problem now I am facing is that after flashing your ROM [After doing a factory reset which consists of Wiping cache,data and dalvik cache] and flashing the boot.img separately is that my Desire X is booting into stock jelly bean ROM even though i have wiped everything. I have tried this thing like for 2-3 times and my bootloader shows UNLOCKED. The phone starts like it has come from factory. Also during 3rd time i noticed that I got a message that Xiaomi Framework has closed. There are some apps of MIUI installed like Weather and gallery etc out of which few work and few don't. I did not get any kind of errors while installing your ROM as well. I have verified the md5 as well but it is not working.
also when I boot into bootloader, i get a green message
SD CARD CHECKING
PM66diag.zip no or wrong image
something like that.
Could you guys please help me out for this one?
Regards,
Pranav
Blueelvis_RoXXX said:
Hi there,
I downloaded the latest MIUI ROM available in the Development sectionand installed when i was on ICS, but it only booted and the BOOT.iMG was not flashed by fastboot because the hboot version was not sufficient for the MIUI jelly bean ROM. My phone was rooted earlier and i was running Sense Revolution 5 but after it was degrading i decided on installing your ROM.
Now, after long hours I updated the stock version via the OTA so the hboot version has now increased. But the problem now I am facing is that after flashing your ROM [After doing a factory reset which consists of Wiping cache,data and dalvik cache] and flashing the boot.img separately is that my Desire X is booting into stock jelly bean ROM even though i have wiped everything. I have tried this thing like for 2-3 times and my bootloader shows UNLOCKED. The phone starts like it has come from factory. Also during 3rd time i noticed that I got a message that Xiaomi Framework has closed. There are some apps of MIUI installed like Weather and gallery etc out of which few work and few don't. I did not get any kind of errors while installing your ROM as well. I have verified the md5 as well but it is not working.
also when I boot into bootloader, i get a green message
SD CARD CHECKING
PM66diag.zip no or wrong image
something like that.
Could you guys please help me out for this one?
Regards,
Pranav
Click to expand...
Click to collapse
Install a recovery meant for the JB hboot
GtrCraft said:
Install a recovery meant for the JB hboot
Click to expand...
Click to collapse
Thanks a lot dude. I tried the beta recovery from TWRP and it got flashed finally
Thanks and sorry for being such a noob.
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
Did you hold the button combinations when your phone is off for more than 4 seconds? If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom. Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
gsstudios said:
Did you hold the button combinations when your phone is off for more than 4 seconds?
Click to expand...
Click to collapse
Yes, I almost got blisters on my fingers, thats how often (and long) I tried it. Also released the power button but continued to hold vol-up+menu as soon as the boot screen showed up.
If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom.
Click to expand...
Click to collapse
Does sound a little crazy indeed, but it also makes sense to add such a feature (i.e. boot into recovery if rom isn't present). Any particular suggestion for a KitKat kernel or should I just pick one of those mentioned here?
Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
Click to expand...
Click to collapse
Nope, no recovery, ergo no factory reset (or is there another way with a softbricked phone?)
Anyway, that would delete the userdata from the phone as well (e.g. photos), correct? Or are they already gone due to my rom flashing etc.? Oh wait, there is this difference between internal memory and internal usb storage, right?
Update
So I could not decide which one of Kitkat Kernels mentioned here to take. But I tried flashing the CWM recovery files, both GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar and CWM-KitKatCompatible-i9100.tar, with Odin. Flashing went fine, but on boot I only see the bootlogo and then the screen went black.
Any suggestion on what other kernel I could try would be welcome.
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
summerchild said:
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
Click to expand...
Click to collapse
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash CM11 from the CWM, not through Odin).
dapperdanman said:
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash km from the CWM, not through Odin).
Click to expand...
Click to collapse
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
summerchild said:
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
Click to expand...
Click to collapse
I don't have a backup of the original ROM, but I can flash a stock ROM and that still gets stuck on the animated Samsung logo.
Anybody else with an idea?