Related
I have a 16GB Nook Tablet that had the software 1.4.2 on it. I rooted it using the sd card method and installed CM7. Rom ran perfectly. I turned off boot animation. I held down power button to restart and now it won't turn on. I boot into clockwork mod to try and reflash something but get an error.
Can you still boot into your CM7 SD ROM?
Solar.Plexus said:
Can you still boot into your CM7 SD ROM?
Click to expand...
Click to collapse
I don't think so. I formatted the sd card so I could put pictures ect back on. I then re-made sd boot disk but still doesn't work.
Tried [UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery and it gets stuck at "writing all zeros to MLO"
Noob needs some assistance, haha
I successfully booted CM7 off of sd card. Are the partitions screwed up?
afastyzfr1 said:
I successfully booted CM7 off of sd card. Are the partitions screwed up?
Click to expand...
Click to collapse
Try to find the Barnes and Noble factory image in the Development subforum.
I can't remember where it is but you write the image to an SD card and just power on the device with the card inside and observe a complete restore.
Sent from my R800x
Solar.Plexus said:
Try to find the Barnes and Noble factory image in the Development subforum.
I can't remember where it is but you write the image to an SD card and just power on the device with the card inside and observe a complete restore.
Sent from my R800x
Click to expand...
Click to collapse
Are you referring to something different than the Ubuntu Recovery? I'll look but if anyone has the link, please post it
afastyzfr1 said:
Are you referring to something different than the Ubuntu Recovery? I'll look but if anyone has the link, please post it
Click to expand...
Click to collapse
This is what I used for a problem NT a while back, post #8 by CRE (props); hope this helps.
http://forum.xda-developers.com/showthread.php?t=1562130
LMN8R said:
This is what I used for a problem NT a while back, post #8 by CRE (props); hope this helps.
http://forum.xda-developers.com/showthread.php?t=1562130
Click to expand...
Click to collapse
I tried post #8 and it appeared to work but after shutting down and removing sd card, it still just bootloops on the n screen
afastyzfr1 said:
I tried post #8 and it appeared to work but after shutting down and removing sd card, it still just bootloops on the n screen
Click to expand...
Click to collapse
Check this tutorial by raywaldo http://www.youtube.com/watch?v=ZIrgkjen8ro (props); this time you should get your NT to boot properly, & hope it works out for you.
LMN8R said:
Check this tutorial by raywaldo http://www.youtube.com/watch?v=ZIrgkjen8ro (props); this time you should get your NT to boot properly, & hope it works out for you.
Click to expand...
Click to collapse
I have tried this and raywaldo is trying to help me through pm's.....but this is what I get when device starts up with sdcard:
Note the red x in upper right hand corner that doesn't appear on his:
I don't get a green check. Instead I get this screen. Then I remove sd card and try to turn the nook on and it just shows the n screen and turns off
Can anyone help?
I somehow screwed up my partitions recently. Couldn't get out of bootloop. Let me look for the method I used. Brb
ok. to begin, here's how i screwed mine up. i was running cm9 with cyanoboot and twrp. i was running through several backups and compressing them. after one, i ended up in a bootloop with cyanoboot that continuously went to recovery. i do not know what all was wrong with the device specificly, but i tried adamoutlers ubuntu, and various other steps. nothing worked. i found my solution using several different threads. ultimately, this is what worked....
i can not claim any responsibility if this screws up your device more than it already is.
read all of this and these links before performing anything. fully charge your device beforehand!
get SDFormatter to have properly a properly formatted sdcard
my NT is a 16gb, and i use a windows 7 pc.
first, create a bootable cwm sdcard. NOTE: i was able to get both steps below onto the root of the sdcard.
second, run this zip to clear the boot count... you may or may not need this. i dont see where it would hurt starting fresh.
http://www.mediafire.com/?lybnkrvgjnqc65b
(original post- http://forum.xda-developers.com/showpost.php?p=26570960&postcount=18)
third, replace partition 1-4 and 6. i presume this restores the b&n recovery. run this zip...
http://www.mediafire.com/?z2n5h3k81a0nsy8
(original post - http://forum.xda-developers.com/showpost.php?p=26575066&postcount=20)
fourth, restore the stock 1.4.2 rom, unrooted.
i used this method: http://forum.xda-developers.com/showpost.php?p=26329581&postcount=1
you may already have a copy of the stock rom, but if you are getting errors, i would download another. CHECKSUM!!!!! i have dicked up more devices than i care to count because of a bad download. i now use MD5_SHA-1 Utility. google it for download.
then i re-rooted using this sdcard method: http://forum.xda-developers.com/showpost.php?p=21275927&postcount=1
again, i can not claim any responsibility if this screws up your device more than it already is. i do hope this helps. it fixed mine.
Sent from my NookTablet using xda premium
I followed your steps and still am in the same position
Tried to flash a ROM as well
afastyzfr1 said:
I followed your steps and still am in the same position
Tried to flash a ROM as well
Click to expand...
Click to collapse
i am having the same problem. i did the the same thing you did. please help lol
Any more help?
............
Pop into the IRC channel and see if someone can help ya out.
afastyzfr1 said:
............
Click to expand...
Click to collapse
I'm in the same situation. Did you find any resolution?
Thanks.
---------- Post added at 06:39 PM ---------- Previous post was at 06:21 PM ----------
frankvcs said:
I'm in the same situation. Did you find any solution?
Thanks.
Click to expand...
Click to collapse
I'm in the same situation. Did you find any solution?
Thanks.
frankvcs said:
I'm in the same situation. Did you find any solution?
Click to expand...
Click to collapse
Need to fix internal partitions but not sure how to easily do that yet
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
alias4ever said:
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
Click to expand...
Click to collapse
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Gage_Hero said:
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Click to expand...
Click to collapse
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Mine, the radio button for external is on, you could try the terminal under advanced button...command would be something like su then enter and then mount /staging or something like that.... you may want to check the command exactly, my terminal skills are limited...
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
tedr108 said:
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
Click to expand...
Click to collapse
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
tedr108 said:
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
Click to expand...
Click to collapse
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
the only way back to an ics bootloader it through nvflash... if you didn't do nvflash before you started with JB then you are stuck using jb roms only I think.....you could try hairy bean .....
tedr108 said:
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
Click to expand...
Click to collapse
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Then trying to install the Unofficial CM10 with the JB Bootloader? Anyone know if this would work?
alias4ever said:
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Anyone know if this would work?
Click to expand...
Click to collapse
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
@Alias -- I was really hoping the JB bootloader ROMs would do it for you.
This right here is excellent advice from Gage_Hero:
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Click to expand...
Click to collapse
If this does not work, I am at a loss of how to recreate the Staging partition (and perhaps others), but there is probably a way.
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
Click to expand...
Click to collapse
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
alias4ever said:
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
Click to expand...
Click to collapse
Glad to get you up and running again just do yourself a favor before you try cm10.... make a backup... or 2 I never used cm on my tab but did it on my phone.... when I restored... I had to do it twice... not sure if that is the case with the prime or not ... but if it is a JB bootloader then you should be okay... I like flashing through twrp though .. never did a rom through goo... but I am sure it works...
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
alias4ever said:
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
Click to expand...
Click to collapse
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Gage_Hero said:
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Click to expand...
Click to collapse
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
alias4ever said:
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
Click to expand...
Click to collapse
Good to hear.... not sure if your aware or not but with a decent backup ( I do one everytime I think I am going to try something foolish) even if you do a wipe, as long as you can reach twrp you can restore the prime to it's state before you started messing with it....
I feel like i've read every thread and tried everything.. hope some one can help?
The Problem:
I had a semi working JB rom and i tried to flash a new rom due to lag and stutter from the one that was on it now I cannot boot past the EEE Pad (asus/nvidia) screen - just sits here with the text on the left corner "AndroidRoot 9.4.2.28r01
The Hope:
I can access CWM, fastboot, ADB etc :silly:
The Attempt:
Almost everything i can find, erasing through fastboot, cwm, installing different roms etc. I've tried flashing a new blob from the official asus download through fastboot but i get an error when putting it through....
Any one have ideas on what it might be, is there hope? or is this money down the drain?
push
dylan.mfh said:
I feel like i've read every thread and tried everything.. hope some one can help?
The Problem:
I had a semi working JB rom and i tried to flash a new rom due to lag and stutter from the one that was on it now I cannot boot past the EEE Pad (asus/nvidia) screen - just sits here with the text on the left corner "AndroidRoot 9.4.2.28r01
The Hope:
I can access CWM, fastboot, ADB etc :silly:
The Attempt:
Almost everything i can find, erasing through fastboot, cwm, installing different roms etc. I've tried flashing a new blob from the official asus download through fastboot but i get an error when putting it through....
Any one have ideas on what it might be, is there hope? or is this money down the drain?
Click to expand...
Click to collapse
I believe you tried to flash a JB rom without the JB boot loader. If you have nvflash enabled then that's you're only recovery option. Other than that it's dead. Asus can fix it for a fee.
McJesus15 said:
I believe you tried to flash a JB rom without the JB boot loader. If you have nvflash enabled then that's you're only recovery option. Other than that it's dead. Asus can fix it for a fee.
Click to expand...
Click to collapse
He says he can access Cwm fastboot and adb so he is not dead.
I will help you when I am at my pc later.
Edit. Get me this info ready please. Power off prime. Hold down volume down and power. When the icons appear for fastboot etc look at the top left where the writing is and at the end is a long number. Does this number start with a 9 or a 10?
I am not talking about androidroot number but the one in the long line with bootloader in it.
flumpster said:
He says he can access Cwm fastboot and adb so he is not dead.
I will help you when I am at my pc later.
Edit. Get me this info ready please. Power off prime. Hold down volume down and power. When the icons appear for fastboot etc look at the top left where the writing is and at the end is a long number. Does this number start with a 9 or a 10?
I am not talking about androidroot number but the one in the long line with bootloader in it.
Click to expand...
Click to collapse
Ah my bad. Saw the Androidroot number thing and assumed it was the nvflash boot loader.
Sent from my Transformer Prime TF201 using xda app-developers app
So very sorry about the delay in a response and thank you very much for your replies!
I have attached a picture of (what i think) you are talking to. I believe what you are asking for is a 9.
Dylan
flumpster said:
He says he can access Cwm fastboot and adb so he is not dead.
I will help you when I am at my pc later.
Edit. Get me this info ready please. Power off prime. Hold down volume down and power. When the icons appear for fastboot etc look at the top left where the writing is and at the end is a long number. Does this number start with a 9 or a 10?
I am not talking about androidroot number but the one in the long line with bootloader in it.
Click to expand...
Click to collapse
Sent from my Samsung Chromebook.
dylan.mfh said:
So very sorry about the delay in a response and thank you very much for your replies!
I have attached a picture of (what i think) you are talking to. I believe what you are asking for is a 9.
Dylan.
Click to expand...
Click to collapse
You have the same problem as someone I fixed not long ago.
Please read thru the following thread and post back here if you get stuck at any point.
http://forum.xda-developers.com/showthread.php?t=2009284
flumpster said:
You have the same problem as someone I fixed not long ago.
Please read thru the following thread and post back here if you get stuck at any point.
http://forum.xda-developers.com/showthread.php?t=2009284
Click to expand...
Click to collapse
Thank you thank you thank yoououuu!!! WOW you are the best!!!!
for any one trying to figure this out, i looked up android wook 1.3 on the android dev upload site and got it through there!!
Thank you soo much! Can i donate $5 and buy you a beer?
dylan.mfh said:
Thank you thank you thank yoououuu!!! WOW you are the best!!!!
for any one trying to figure this out, i looked up android wook 1.3 on the android dev upload site and got it through there!!
Thank you soo much! Can i donate $5 and buy you a beer?
Click to expand...
Click to collapse
It's ok thanks mate, I have loads of beer
Enjoy your prime
dylan.mfh said:
So very sorry about the delay in a response and thank you very much for your replies!
I have attached a picture of (what i think) you are talking to. I believe what you are asking for is a 9.
Dylan
Sent from my Samsung Chromebook.
Click to expand...
Click to collapse
It looks like I have the exact same problem but my number starts with a 10. I would be eternally grateful if someone could help. I have searched for hours and have had not luck ;(
---------- Post added at 02:50 PM ---------- Previous post was at 02:40 PM ----------
How I did this...
I was running CM 10 with the jb bootloader and I figured I'd update before going on a trip.
I decided to try AndroWook but couldn't get it to boot. I couldn't get it to work or figure out why. When I recovered CM, no problem. So I decided to give it one more go and downloaded AndroWook 1.3 and installed as if I was updating the bootloader.
Been in ruins ever since ;(
I can get to fastboot and adb but can't boot into recovery! I tried flashing a new recovery through fastboot. I am either missing something or it is not working.
Thanks for anyone that can point me in a direction.
eyecubed said:
It looks like I have the exact same problem but my number starts with a 10. I would be eternally grateful if someone could help. I have searched for hours and have had not luck ;(
---------- Post added at 02:50 PM ---------- Previous post was at 02:40 PM ----------
How I did this...
I was running CM 10 with the jb bootloader and I figured I'd update before going on a trip.
I decided to try AndroWook but couldn't get it to boot. I couldn't get it to work or figure out why. When I recovered CM, no problem. So I decided to give it one more go and downloaded AndroWook 1.3 and installed as if I was updating the bootloader.
Been in ruins ever since ;(
I can get to fastboot and adb but can't boot into recovery! I tried flashing a new recovery through fastboot. I am either missing something or it is not working.
Thanks for anyone that can point me in a direction.
Click to expand...
Click to collapse
Just install the regular version of this http://forum.xda-developers.com/showpost.php?p=34937936&postcount=6210 . put a Jellybean rom either Androwook 1.51 or nrgz latest from the developers thread on a micro sd card. And then use this to flash a new rom. Do not forget to wipe cache, dalvik and factory reset. You can actually wipe anything EXCEPT FOR EXTERNAL SD.
whycali said:
Just install the regular version of this http://forum.xda-developers.com/showpost.php?p=34937936&postcount=6210 . put a Jellybean rom either Androwook 1.51 or nrgz latest from the developers thread on a micro sd card. And then use this to flash a new rom. Do not forget to wipe cache, dalvik and factory reset. You can actually wipe anything EXCEPT FOR EXTERNAL SD.
Click to expand...
Click to collapse
Fixed him over pm about 6 hours ago mate lol
flumpster said:
Fixed him over pm about 6 hours ago mate lol
Click to expand...
Click to collapse
um, updates are nice
So I was flashing a new rom in CWM on my AT&T Atrix 4G, unlocked bootloader, running CM10. I was going to flash CM9 because there was a bug in CM10, and when I went to wipe my dalvik cache, I hit the wrong menu option somehow and wiped an internal partition that must've been the one that CWM was on, so now I get the screen shown in the picture. Any ideas guys? Thx.
Njl6705 said:
So I was flashing a new rom in CWM on my AT&T Atrix 4G, unlocked bootloader, running CM10. I was going to flash CM9 because there was a bug in CM10, and when I went to wipe my dalvik cache, I hit the wrong menu option somehow and wiped an internal partition that must've been the one that CWM was on, so now I get the screen shown in the picture. Any ideas guys? Thx.
Click to expand...
Click to collapse
what happens if you select #9 android recovery?
barry_ said:
what happens if you select #9 android recovery?
Click to expand...
Click to collapse
I should have mentioned, that doesn't work. I get the error in the following picture.
Please help me! I forgot how awful using a feature phone is! lol
are you familiar with fastboot? What happens if you select fastboot? I am just thinking that you might try reflashing the recovery (fastboot flash recovery recovery.img) but I am not great with fastboot but worth a look?
---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------
saw this http://www.youtube.com/watch?v=1vHaDlRFocU might be of some help?
barry_ said:
are you familiar with fastboot? What happens if you select fastboot? I am just thinking that you might try reflashing the recovery (fastboot flash recovery recovery.img) but I am not great with fastboot but worth a look?
---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------
saw this http://www.youtube.com/watch?v=1vHaDlRFocU might be of some help?
Click to expand...
Click to collapse
I'll give it a try. Thanks man! I was looking at SBF files, which I really wanted to avoid. I'll let you know what happens.
Nothing. The fastboot command line tool couldn't see my phone. I'm going to look for another guide. Maybe there's something I'm missing.
this? http://modmymobile.com/forums/661-motorola-atrix-4g-development/560719-how-recover-soft-brick.html
barry_ said:
this? http://modmymobile.com/forums/661-motorola-atrix-4g-development/560719-how-recover-soft-brick.html
Click to expand...
Click to collapse
Driver issues. When I click yes to the error on the first button, the error in the second screenshot pops up.
By the way, I just want to say I appreciate the help and the quick replies.
Found the drivers and successfully flashed RomRacers Recovery through Fastboot! Thanks guys! She lives!:victory:
It's odd though, I just flashed cm10 and I'm having frequent random reboots and the screen calibration is off.
It looks like the trick here is a pds partition fix. I'll give it a try tomorrow and report back.
The pds partition worked.
Njl6705 said:
Driver issues. When I click yes to the error on the first button, the error in the second screenshot pops up.
Click to expand...
Click to collapse
Njl6705 said:
By the way, I just want to say I appreciate the help and the quick replies.
Click to expand...
Click to collapse
Njl6705 said:
Found the drivers and successfully flashed RomRacers Recovery through Fastboot! Thanks guys! She lives!:victory:
Click to expand...
Click to collapse
Njl6705 said:
It's odd though, I just flashed cm10 and I'm having frequent random reboots and the screen calibration is off.
Click to expand...
Click to collapse
Njl6705 said:
It looks like the trick here is a pds partition fix. I'll give it a try tomorrow and report back.
Click to expand...
Click to collapse
Heard about edit function?
eagleeyetom said:
Heard about edit function?
Click to expand...
Click to collapse
No, I haven't. Care to elaborate?
It means posting 5 posts one after the other instead of simply editing the first one is frowned upon.
ravilov said:
It means posting 5 posts one after the other instead of simply editing the first one is frowned upon.
Click to expand...
Click to collapse
Oh. Haha that edit function. I thought he was talking about something in android. N00b here. Sorry.
Njl6705 said:
Found the drivers and successfully flashed RomRacers Recovery through Fastboot! Thanks guys! She lives!:victory:
Click to expand...
Click to collapse
good to see you got there in the end :good:
a little help
Njl6705 said:
Found the drivers and successfully flashed RomRacers Recovery through Fastboot! Thanks guys! She lives!:victory:
Click to expand...
Click to collapse
I am a RAZR user and have it all rooted and running great so I am fairly competent but a co-worker has the ATRIX and it was in a bootloop. I offered to help and find myself practically where you were except I have no OS on the phone and can not seem to get recovery on it.
Can you share where you found the right drivers, recovery, and a good OS? Basically I need someone to hold my hand through this because I do not have the time to keep looking for the right things since I have a kitchen remodel underway and a wife who....need I say more?
Thanks
can't recover from this
Njl6705 said:
So I was flashing a new rom in CWM on my AT&T Atrix 4G, unlocked bootloader, running CM10. I was going to flash CM9 because there was a bug in CM10, and when I went to wipe my dalvik cache, I hit the wrong menu option somehow and wiped an internal partition that must've been the one that CWM was on, so now I get the screen shown in the picture. Any ideas guys? Thx.
Click to expand...
Click to collapse
I got exactly what you did. But even in fastboot mode I can't get out of this screen after flashing the recovery. Actually it does not get into CWM or another recovery but each time I Vol and Power Down it gets into this screen again. Looks like flashing does not help at all. If I select Boot Android it powers up in the last ROM I flashed before all this. The problem is that I cannot operate any soft button at the bottom: the screen looks not calibrated so I need to push on areas lower than actual buttons are, and I don't know how to get out of that either. No Back, neither Home or Search buttons are unreachable.
What can I do? How to reflash this phone?
If you activate the RSD mode you can flash your stock rom with RSDLite. There is a superthread with the original firmwares, you will lose root and unlock but it will restore completely your device
So I had Cyanogenmod 10 on my tf201 with clockwork recovery. In the Dev page there is a new Rom for PA for the 201. I did exactly as it said and factory reset, wiped cache, ect then installed PA and GAAPS. Problem is Im stuck at the splash screen on boot now and I DONT HAVE ANY OTHER ROM LOADED ON THE MEMORY. CMW recover doesnt recoginise micro sd cards and no matter what i try that PA rom wont load. So now I feel I have a very expencise paper weight and I'm dieing of worry here. PLEASE any help in this issue would be much appreciated!
redon2 said:
So I had Cyanogenmod 10 on my tf201 with clockwork recovery. In the Dev page there is a new Rom for PA for the 201. I did exactly as it said and factory reset, wiped cache, ect then installed PA and GAAPS. Problem is Im stuck at the splash screen on boot now and I DONT HAVE ANY OTHER ROM LOADED ON THE MEMORY. CMW recover doesnt recoginise micro sd cards and no matter what i try that PA rom wont load. So now I feel I have a very expencise paper weight and I'm dieing of worry here. PLEASE any help in this issue would be much appreciated!
Click to expand...
Click to collapse
Is there some way I can boot from usb or adb transfer or somthing. Or am I completely screwed here? This is horrible
redon2 said:
Is there some way I can boot from usb or adb transfer or somthing. Or am I completely screwed here? This is horrible
Click to expand...
Click to collapse
If you are using cwm chances are you are on the ics bootloader. To check look where the nvidia logo is when you turn it on. If it is bottom center it is ics, bottom right is jb.
Now go to the twrp thread and then to their website and get twrp for your bootloader (prob ics) and flash in fastboot. Now you can flash from external sd.
flumpster said:
If you are using cwm chances are you are on the ics bootloader. To check look where the nvidia logo is when you turn it on. If it is bottom center it is ics, bottom right is jb.
Now go to the twrp thread and then to their website and get twrp for your bootloader (prob ics) and flash in fastboot. Now you can flash from external sd.
Click to expand...
Click to collapse
Thanks flumpster! I ended up finding an emergency file transfer that uses fastboot. You're solution would have been simpler but in the end its back up and running with a JB bootloader and rom now :victory:
Same issue
redon2 said:
Thanks flumpster! I ended up finding an emergency file transfer that uses fastboot. You're solution would have been simpler but in the end its back up and running with a JB bootloader and rom now :victory:
Click to expand...
Click to collapse
I have the same exact problem. Where did you finding the emergency file transfer that uses fastboot?
---------- Post added at 05:40 PM ---------- Previous post was at 05:30 PM ----------
flumpster said:
If you are using cwm chances are you are on the ics bootloader. To check look where the nvidia logo is when you turn it on. If it is bottom center it is ics, bottom right is jb.
Now go to the twrp thread and then to their website and get twrp for your bootloader (prob ics) and flash in fastboot. Now you can flash from external sd.
Click to expand...
Click to collapse
I can't find twrp for Asus Prime on their website... or the thread in this forum? Its probably somewhere obvious, could you possibly point me in the right direction?
---------- Post added at 06:29 PM ---------- Previous post was at 05:40 PM ----------
SS823 said:
I have the same exact problem. Where did you finding the emergency file transfer that uses fastboot?
---------- Post added at 05:40 PM ---------- Previous post was at 05:30 PM ----------
I can't find twrp for Asus Prime on their website... or the thread in this forum? Its probably somewhere obvious, could you possibly point me in the right direction?
Click to expand...
Click to collapse
Never mind, easy find.
Fixed, but newbie question
I reverted back to CM10 by pushing a the ROM in adb.
I was hoping to try things over, but as a newbie I am not sure how (really, when) to install the bootloader necessary for 4.2.
I know baked bean requires the offical firmware from ASUS, which I have, but when do I install it, before or after the ROM?
SS823 said:
I reverted back to CM10 by pushing a the ROM in adb.
I was hoping to try things over, but as a newbie I am not sure how (really, when) to install the bootloader necessary for 4.2.
I know baked bean requires the offical firmware from ASUS, which I have, but when do I install it, before or after the ROM?
Click to expand...
Click to collapse
Flash the ASUS JB rom first. it should update your bootloader and allow you to boot custom JB roms from then on.
Thanks. If I install the ASUS firmware will I will lose root?
Sent from my Transformer Prime TF201 using xda app-developers app