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
Related
hi all
just wanted to star a discussion about this topic..
anybody know, how's the progress in getting a CWM for MediaPad?
thanks a lot
Backup works, but restoring a backup doesn't restore every setting. So i would say it's a WIP. But maybe segler11 or brainmaster can tell more about it.
Eagerly awaiting for this to be done.
Androod-hilfe.de has a clockwork RECOVERY.
Gesendet von meinem HUAWEI MediaPad mit Tapatalk
Is there a way to get a hold of this?
Sent from my HUAWEI MediaPad using XDA
I would love to break my tablet in the name of getting it to work
Sent from my HUAWEI MediaPad using XDA
@cosmique
Like I said, it's a WIP and restoring a Backup doesn't work 100% afaik... But if someone wants to try it here, go ahead. I'll upload it.
€dit: Done
Original Thread: here.
WARNING: I'm not responsible for any damage on your devices. This has only been tested on a european Huawei Mediapad and is based on the 2nd Preview of ICS
Code:
fastboot flash recovery recoveryxxxx.img
fastboot flash recovery2 recoveryxxxx.img
Important: If you want to restore a backup use
Code:
wipe data/factory reset
wipe cache partition
first !
After a "wipe data/factory reset" and "wipe cache partition" the first boot could take at least 10 minutes.
If you want to flash AddOns like GApps.zip no wipe is needed
After restoring a Backup, ALL apps are restored but not all app-settings.
Remember: It's a BETA-Release !
Click to expand...
Click to collapse
All credits go to DS7005, segler11 and brainmaster
Just a helpful hint: Titanium Backup can now restore app data directly from nandroid backups. So if the biggest issue right now is failure to restore app data, in a pinch Titanium can fill in the blanks.
Sent from my Galaxy Nexus using Tapatalk
Recovery flashed successfully but when I perform a backup, it says that the backup path can't be mounted. This is on a Springboard running ICS Beta 2.
Bump. Any further progress?
So it has been quite some time since I have heard anything about CWM for our device. Does anybody have an update? What the heck ever happened with the folks working on it over in Germany?
rkwhyte2 said:
So it has been quite some time since I have heard anything about CWM for our device. Does anybody have an update? What the heck ever happened with the folks working on it over in Germany?
Click to expand...
Click to collapse
Last time I tried the download at post #7 it worked for the basic. As described by Rumbi it may not restore widgets and some setting.
The downside is that you have to reinstall original "boot.img" and "recovery.img" to be able to update to next version, every time
I think that as things get stabilized on the ICS firmware there will be more work for it !
Question: Is there any recovery.img available that would be equivalent to stock recovery on a Springboard?
In other words... if I upgrade a Springboard to MediaPad ICS... then later revert to 3.2 from a nandroid backup, is there a recovery.img that I can flash so that OTA updates will work again?
Okay I flashed the CWM img successfully in fastboot on my Springboard...
But what I'm confused about is, how do I boot into recovery now? I have tried every combination and I always get either fastboot or regular boot.
Do I have to already have ICS for this recovery to work?
Update: Ok I managed to figure out the trick is to hold the volume down button, press power for 2 seconds until it vibrates, let go of power and continue holding the volume until recovery starts.
The problem is I always get stock recovery, which gives me a FAIL message.
I discovered that on my Springboard I have the May 2012 OTA update already installed, which included the dreaded /system/recovery-from-boot and /etc/install-recovery files. This means any time it boots successfully into the OS, it reinstalls the stock recovery.
So now I have a paradox because I'm still not rooted yet. I can install CWM from fastboot, but there is no way to cleanly power down the tablet. I have been unable to force it from fastboot directly to recovery, because the only way to get it out of there is to hold down the power button which... yup, starts rebooting into the OS. I can hold down power during that reboot cycle, but again it just initiates a reboot and not a power down.
So how do I get into recovery after flashing CWM in fastboot... without letting it boot the OS before I get there?
So far the only idea I have remaining is to flash CWM in fastboot and then just leave it on the fastboot screen, stick it in a box somewhere, and come back in a day or so when the battery has died. Charge it up and then boot it into recovery. A little extreme?
Boot into fastboot normally pressing power and VOL-
When in fastboot press the power button for 10 sec to reboot and then keep pressing the VOL+ button, it'll show the mediapad logo twice and the you will be in the cwm.
Hope it helps.
dark_fighter said:
Boot into fastboot normally pressing power and VOL-
When in fastboot press the power button for 10 sec to reboot and then keep pressing the VOL+ button, it'll show the mediapad logo twice and the you will be in the cwm.
Hope it helps.
Click to expand...
Click to collapse
I tried that. It just booted into the OS.
Also the Springboard firmware has an annoying loud T-Mobile startup chime, so to be considerate with my roommate, the moment I see it booting into the OS I have to wrap it with my duvet in order to muffle the sound
Is it possible this CWM just isn't compatible with the Springboard on Honeycomb?
Just a question... if you want to update to ICS but stock, why don't you use the official rom from Huawei? and If you don't like it you can always flash back a HC rom from Huawei.
Sorry if I didn't get something and this is a stupid suggestion
Huawei doesn't offer any stock ROM files for the Springboard. I would like to install and run CWM from the Springboard while leaving the T-Mobile Honeycomb intact, in order to root it without any other modifications.
Sent from my Galaxy Nexus using Tapatalk 2
UPDATE: I did not notice at first that I had to flash both recovery *and* recovery2.
Even after noticing this, I was unable to leap from fastboot straight into recovery. However, I left it in fastboot this morning after flashing, to drain the battery. Then I got home and plugged it in to charge for about 5 minutes. I unplugged it, used the recovery key combo, and FINALLY made it into CWM! I used an SD adapter to copy su.zip onto the microSD, plugged in, remounted /sdcard and installed that zip. I have plugged it back in to charge, and I am doing a nandroid backup of stock rooted.
First thing I will have to do once booted is install Root Explorer and rename the offending files that keep replacing CWM. Then I'll be off to the races.
EDIT: The backup stalled during the system partition. Don't know why. Maybe something different about the layout of Springboard vs. MediaPad.
Also, adb in recovery does not work (unless there is a driver I am missing? but ADB works for me booted into the OS). That's unfortunate - this is an incredibly useful feature of CWM that should get fixed up ASAP.
I also noticed that a 10 second press of the power button actually shuts it down from CWM, as opposed to the reboot I get from fastboot or anywhere else in the OS.
EDIT again: Oh crap crap crap. Now it just bootloops when I try to start it up! This does not bode well. All I did was install a superuser zip, and attempt a nandroid backup.
FINAL edit once more again: Okay well now I'm back to square minus one. I wiped userdata and it still bootlooped. So then I tried flashing the system img from this thread:
http://forum.xda-developers.com/showthread.php?t=1550694
No more bootloop. It's booted up. The firmware is now an older one than what I received it with. Oddly when I did "fastboot erase userdata" from fastboot it did NOT actually wipe anything! It still remembers my desktop, wifi passwords, installed apps etc.
On the bright side - the dreaded recovery-reinstalling files are not in this system.img.
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
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer
I have a SGP311 and started to root by following the guide at http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377. Works prefectly! Unlocked using the guide at http://wiki.cyanogenmod.org/w/Install_for_pollux_windy which also worked.
But once I flashed the boot.img it start bootlooping. The option "backup and restore" isn't visable in the recovery mode. I can't find install from zip either. I can install from external storage, but that doesn't work either.
I managed to get in to the tablet again by replacing the boot.img to another boot.img, but that doesn't help me to get CyanogenMod 12 though.
I'm new to this, so I might have made something wrong here, please tell me if so
I have a little problem of my own also when I try to unlock the bootloader following the Sony web page everything looks ok but when I boot the tab it's stuck in a bootloop at the xperia logo.....
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
skift said:
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
Click to expand...
Click to collapse
it seems that you just haven't unlocked you bootloader or using boot.img with broken recovery.
The bootloader was unlocked fine. Went through Sony to get the code and unlock it. I was even able to flash Previously using flashtool. I re ran the flashing to get back to where I was and tried it again and it seemed to work. The only way I could reboot was to hold power and volume up till I got the 3 flashing lights. Then I could get into recovery.
Hey guys I need some help. I have a Verizon Galaxy S4 with NK1. I rooted it by flashing back to NC5 and then rooting then flashing back to NK1, that part worked perfectly fine. I then wanted to install a recovery so I used the CWM app and thats where things went wrong. After doing so it said it did it successfully but when I clicked boot into recovery so I can install CM12 it did not boot into recovery it instead booted straight to the Odin screen with the Android logo in the middle and below it saying "Downloading", and also has the text in the top left corner.
I am hoping someone has an answer on how to fix this.
Thanks!
Also to add onto that I am able to boot up my phone normally its not that its stuck in a boot loop where I can't get past that point. It only happens when I try to go into recovery mode that it take me to the Odin screen. When I do the steps for booting into Recovery it shows the samsung logo and then the blue text that usually comes up in the top left corner flashes for a millisecond and then the screen transitions to the Odin screen
No cm based roms & only safestrap for custom recovery. Spend some time reading what you can & can't do to your phone
rrrrrrredbelly said:
No cm based roms & only safestrap for custom recovery. Spend some time reading what you can & can't do to your phone
Click to expand...
Click to collapse
Is there any other way I can factory reset my phone and wipe it completely because I can't go into recovery mode.
Have you installed safestrap?
rrrrrrredbelly said:
Have you installed safestrap?
Click to expand...
Click to collapse
Yessir I installed it, what would be the next step?
Read how to use it. If you installed the recovery (not just the apk), reboot your phone and you'll see the screen and directions how to enter ss recovery.
From there you'll be able to wipe your phone.
Not sure how it'll work with you trying to install cwm. If this doesn't work, odin'ing back to stock and starting over might be your next option (unless someone else can suggest something)
Aslo, if you're stuck in that boot, you can pull the battery,
then hold the volume down, home and power to get the the download screen,
choose restart the phone
this worked for me when I was in a boot loop
This won't fix your recovery mode issue though, but you'll be able to use your phone in the mean time