Okay my Atrix 4g has unlocked bootloader, Android 2.3.6, and I flashed CWM recovery the other day, and it worked fine except whenever I plugged in my phone to wall charger, it would boot AUTOMATCALLY into that recovery. Followed this guide: LINK
I then installed CWM recovery 5.0.2.3 from here: LINK
Now again when I plug usb into wall to charge, it boots into the first recovery I installed. I can't see the battery charge symbol.
Now I downloaded this ROM - http://forum.xda-developers.com/showthread.php?t=1836674 and tried to boot into recovery from using the volume down button until "Android recovery" but that takes me to the stock 4 option crap.
So I tried to flash the MROM from ROM manager in the os, and it says restarting into recovery, AGAIN that takes me to the triangle exclamation point crap.
SO MY QUESTION is if I do a disk clear, format from the recovery, would my phone still work with T-mobile afterwards, and I can install the CWM again, and flash the new ROM?? I don't care about losing data, I have only few apps.
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
ravilov said:
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
Click to expand...
Click to collapse
Here's a crazier idea - do you mind explaining things in more detail, since I am a noob and this is a help forum.
--
When I install the the recovery, it just says hit yes to continue. Please help, rather than telling me that I am an idiot.
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
ravilov said:
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
Click to expand...
Click to collapse
No problem mate.
Well I guess I could tell you what I did, but I did exactly what the guides said:
downloaded the .zip archive, placed contents anyplace, and started cmd from that folder and entered:
adb install MOTOA4_Bootstrap_0408_1720-signed.apk
Then I opened up that app "System Recovery" and hit Install recovery, then I hit recovery mode from the app, and was told to connect the usb to the wall charger, not pc. And that was it for the first recovery. I then noticed that this specific recovery was missing some functions in the actual recovery so I installed 5.0.2.3 later.
I downloaded the .zip from the site and placed inside phone internal SD, the second link from OP here, turned on phone and went into Android recovery and it opened up the one I installed just a minute ago, and hit install zip from sdcard, I hit internal, and selected the .zip I downloaded from that site. I hit reboot recovery and it booted into that recovery, 5.0.2.3, the real one.
To go to this new one, I insert wall usb to phone and it boots in the first recovery, and I hit, reboot recovery, and it takes me to the new one.
NOW whenever I plug in usb to wall to charge, it boots in the old recovery, and I don't see charge symbol. I have calibrated my battery 3 times, and it is still CRAP (brand new 1800mah battery for mb860).
Anyways, I thought to ask here if I did a wipe data from the new recovery, or old, would it get rid of this whole mess?
Hmm ok.
I told you this before but here goes again. I'd give up on random guides from random sites. Everything you need is right here on this forum.
Not to mention, the recovery in that ZIP is slightly older, there is a newer one available.
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
The ZIP you downloaded seems fine, but it's somewhat likely your boot is also messed up too. If all this goes well, you can try finding the T-Mobile fruitcake (go over to the Atrix Reboot Project thread) and flashing it from the recovery. Be aware though that you might lose all data in doing this.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
ravilov said:
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
Click to expand...
Click to collapse
ALRIGHT thanks for this actual guide.
It installed fine, works fine, AND AGAIN whenever I plug the wall charger in when the phone is off, it boots into the OLD OLD recovery, from the first link.
I still can't see the battery.
Please stop throwing sass at me. :crying:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
ravilov said:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
Click to expand...
Click to collapse
I can only find this: http://forum.xda-developers.com/showthread.php?t=1163009
I downloaded the 2.3.6 ROM from the backup thread. Says nothing about T-mobile.So do I just install this from the new CWM?
Is there just no way of getting rid of CWM recovery so I can install it just once, rather than you keep telling me to install this and that?
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
ravilov said:
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
Click to expand...
Click to collapse
YES!!! Because everytime I connect the damn charger it boots cwm. AND EVERYTIME I hit ANDROID RECOVERY I boot into the OLD OLD OLD OLD Recovery.
why is that hard to understand? I want to uninstall ALL the cwms, and install the one you sent me just to have that one, rather having 3 different cwms I have right now.
Also that thread is just a bunch of people talking about nothing really. HAS ABSOLUTELY nothing to do with T-mobile whatsoever.
I just want to make sure that this AT&T phone will still work with my t mobile sim card after I install ROMs!!!!
---
And for the love of all that is holy, don't reply with: "why won't it?"
BECAUSE THAT IS WHY I AM ASKING. I have never done this, that is why I ASK!!!!!
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
ravilov said:
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
Click to expand...
Click to collapse
SO there is NO WAY to remove CWM recoveries?????
LOL THIS IS FUNNY! Now when I plug charger in, it just boots into OS, and when I hit android recovery with VOL buttons, it shows the white triangle.
Still don't get what that rom did. Installed it, and nothing, except for losing all my data.
This forum made things worse.
Thank you.
EDIT: OKAY NOW it shows the battery when plugged in but still the white triangle crap in the recovery.
You must have SOME recovery. You can install TWRP if you like that better, but you must have SOMETHING. By following the procedure I described you properly installed RomRacer's CWM so that part is fine. Now, why are you still sometimes getting the stock 4-option recovery - only heaven knows.
I don't think there's a way to install the stock Motorola recovery other than installing the full SBF, however SBFs are VERY dangerous and nobody is going to recommend that.
I really can't imagine what you've done with your phone. The mere fact you have multiple recoveries raises a big red flag right there. I tried to help the best way I can, but since obviously it's not doing much good, I'm going to refrain from further comments and let someone else take over. Good luck.
Ravilov has said it all but its pretty spread out trying to figure out what happened so I'm hoping I can tie it all together.
If you attempt to boot into recovery and get the old android recovery but booting normally puts you into CWM Recovery then somehow you have flashed the BOOT partition with CWM image. To fix this just download the correct fruitcake and flash the BOOT.IMG to the BOOT partition using the moto-fastboot tool and reboot. I would recommend erasing the BOOT partition first just in case.
Sent from my Nexus 7 using xda app-developers app
Thanks for your patience and help Ravilov
Sent from my MB860 using xda app-developers app
Related
I've spent my entire day trying to flash a recovery image on my streak to no avail. I've rooted it using the super one click, have superuser on my device, along with clockworkmod.
I've confirmed my device is rooted using z4root.
I've tried flashing the recovery via clockwork, it says it was successful, yet when I reboot to recovery, I always end up in the regular OS, like all it did was reboot. Furthermore, trying to manually get there, holding down the buttons, tells me that the stanard recovery wasn't actually overwritten. When I go through fastboot and flash it that way, both computer and streak tell me that everything was successful. Yet, the recovery was still not overwritten.
My end goal is to put Steve's ROM on the streak, but I can't even get the recovery overwritten with clockworkmod.
I have a Dell Streak OEM:340. Thats the locked ATT version, which I think might be a part of the problem.
How do I end up with Steve's rom?
Sounds like you are using ROM manager? That does not work well with the Streak. See this article. ROM manager may actually flash your recovery, but does not work to start the phone in that mode.
You can flash the recovery image to your phone in fastboot mode. Here is a tool to help.
You get to fastboot mode by starting the Streak while holding the camera and power buttons at the same time. Then select fastboot from the top right of the screen and plug your phone into your computer. You will need the Dell drivers for this.
Also be aware that you need to rename install-recovery-sh to something else to prevent the stock recovery from being installed when the phone restarts. It's in the folder /etc. You have to use root explorer or an alternate method to do this, but it requires root.
I am using a ROM manger, but if that doesn't work as well, I'll stop.
I've been fastbooting it the majority of the time, flashing the ROM, but it says I've done it correctly, even though I obviously haven't. So far, all I know is that it's been rooted, and the recovery flashed via fastboot.
kyrillos27 said:
I am using a ROM manger, but if that doesn't work as well, I'll stop.
I've been fastbooting it the majority of the time, flashing the ROM, but it says I've done it correctly, even though I obviously haven't. So far, all I know is that it's been rooted, and the recovery flashed via fastboot.
Click to expand...
Click to collapse
Have you renamed the install-recovery.sh file so that the custom recovery won't be replaced by the stock recovery when you reboot? If not - do so.
Make sure that the Streakdroid rom you want is in the root of the SD Card along with the install.txt file.
If you can get into fastboot mode and connect to your computer I suggest using MultiRecoveryFlasher Streakmod recovery. You can reboot the phone from there also.
When you reboot you want to get to recovery mode. Turn your phone off then press the power button tile the leds light up and as soon as they do hold down BOTH volume buttons. See this gallery for what Streammod recovery should look like. Selecting the #2 option will take you to the streakmod recovery options. You use the "apply sdcard:update.zip" to install the ROM.
See the release thread for the ROM you are installing for more info and post any problems or questions you have with the ROM in that thread.
I have not renamed the install-recovery.sh file. in fact, haven't seen one through the process. To be honest, I'm not sure this part has been done at all by me. How do I go about doing that?
Furthermore, choosing the second option in recovery doesn't give methe streakmod options, it just tells me everything will be erased (stock Dell recovery). How do I make sure that this gets corrected?
For the record, marvin02, thank you thus far for the amount of help you've been giving me.
kyrillos27 said:
I have not renamed the install-recovery.sh file. in fact, haven't seen one through the process. To be honest, I'm not sure this part has been done at all by me. How do I go about doing that?
Furthermore, choosing the second option in recovery doesn't give methe streakmod options, it just tells me everything will be erased (stock Dell recovery). How do I make sure that this gets corrected?
For the record, marvin02, thank you thus far for the amount of help you've been giving me.
Click to expand...
Click to collapse
The file install-recovery.sh is a script that runs each time your phone is started. It will replace a custom recovery (streakmod) with the stock recovery when your phone starts, so the next time you enter recovery mode you are back at the stock recovery.
If you are going to dstay with a stock ROM, but want a custom recovery you have to rename the file. The easiest way (IMO) is to use Root Explorer which is an app you have to buy. You just open root explorer and the open the folder named etc and find install-recovery.sh long pres on it to get a menu to pop up and then select rename.
You don't have to do that to get a streakdroid rom installed if you enter recovery without letting the phone restart first.
Put the streakdroid rom file and the install.tx on the root of your SD card
Turn your phone off
Turn phone on in fastboot mode (camera and power buttons at the same time)
Use this tool to to flash the recovery you want
Using the same tool you can reboot the phone
As the phone reboots (wait for the leds to turn on just like they do when you restart the phone) hold down BOTH volume buttons to enter recovery. If you let the phone boot normally and you have not renamed install-recovery.sh the custom recovery will be over written.
Select option 2 and you should be taken to the streakmod options (images here)
Select apply sdcard:update.zip from the recovery menu
There will be two options on the next screen, select the one that lets you navigate to/select a file and then select the ROM file you put on your SD Card.
The ROM should install, be patient when it reboots it can take a few minutes.
i have spent the last 2 days searching these xda forums. btw u guys rock. i would not have gotten throgh rooting and putting a custom rom my first phone if it wasn't for you. anyway, i found out the hard way that trying to mod an atrix with 2.3.6 on build 4.5.141 is not easy. after many wrong turns, i was finally able to unlock my bl and get my phone rooted. then i was able to play with cwm. i was able to backup my current rom, but cannot reboot into recovery. this made me curious so i tried to enter android recovery which failed as well. both ways gives me the droid guy and a triangle. i went thru all this work so i could flash a cool rom ( thinking cm7 since it seems to be stable, but i wanna check around). since i cant reboot into recovery, im kind of at a stand still. i did my best to search through the forums before i asked any stupid questions, but im stuck. please help me.
What have you tried to get into recovery? How did you install a recovery?
Delete install-recovery.sh @ /system/etc.
Then, install Rom Racers recovery via fastboot.
Sent from my CM7 Atrix.
I tried to reboot into recovery from rom manager. When that failed i powered phone up holding volume down, then scrolled to android recovery option. i used automatic unlock v4.2 to unlock bl's (option 1). I did not use option 2 to root since i was not familiar with tenfar cwm. So i rooted using method #1 from rootzwiki's atrix page. I then chose option 6 for cwm recovery and rom manager. I went to market, downloaded rom manager. When i opened rom manager, i clicked flash cwm recovery. then tried to reboot into recovery and....dead end.
thanks swiftks. i was actually looking into following your advice. just didnt want to post until i tried. anyway, i already have rom racers zip downloaded onto my internal memory. the plan was to use rom manager to install rom from sd card just like its says on the noob page. just was never able to get that far. so im sorry for my ignorance, but how do i go about deleting that file. and how do i use fastboot to install rom racers recovery? im trying my best to learn. i broke my captivate a few days ago and this phone is new to me. plus, im not exactly a tech expert. i just follow directions well and have learned just enough to get myself into trouble
Ill let swift answer from here cuz im stumped. I do know to delete the file, you need root explorer (can find on play store) and root access. Open root explorer and navigate to system/etc then find the file and delete it.
update. so before i went hunting down root explorer i tried to flash cwm recovery through rom manager one last time (3rd time, every time said it was successful. lo and behold, i got into recovery. i am now going to attempt to upgrade to rom racers cwm. i did at one point download a fastboot file, just cant remember if i installed correctly cuz i was pretty drunk last night. how can i verify. i do definately have sdk tools tho. checked for adb devices. is fastboot under sdk tools? or was that a dumb question?. nevermind. i do have fastboot. found my fastboot device. Then entered "fastboot erase recovery" failed 000300003. im pretty sure this needs to be deleted as u suggested. when i got recovery to open, i went back and tried to finish installing romracers cwm via rom managers install from sd option. got the triangle again. reflashed cwm thru rom manager and was able to boot into recovery. from there i tried to install zip from sd, installation successful, reboot propmpt. rebooted. wnet directly to rom manager, tried to reboot into recovery... triangle. reflash thru rm, recovery boots. reboot system. tried to reboot into recovery, but triangle is back. the only way for me to get to recovery is reflash it everytime before i use it. this has got to be because i never deleted the path you suggested, right? im really tryin here, but i feel like im stuck inside a real life boot loop
twinlakesnake said:
update. so before i went hunting down root explorer i tried to flash cwm recovery through rom manager one last time (3rd time, every time said it was successful. lo and behold, i got into recovery. i am now going to attempt to upgrade to rom racers cwm. i did at one point download a fastboot file, just cant remember if i installed correctly cuz i was pretty drunk last night. how can i verify. i do definately have sdk tools tho. checked for adb devices. is fastboot under sdk tools? or was that a dumb question
Click to expand...
Click to collapse
On my computer the path for fastboot is android-sdk-tools/platform-tools/fastboot
i downloaded root explorer. deleted install-recovery.sh @ /system/etc. once i did this i was able to use fstboot commands from rom racers page. fastboot erase recovery was successful. then tried 'fastboot flash recovery recovery-atrix5.img'
error: cannot load.
im chipping away at it but wow. thoght i would be flashing cm7 by now. I do appreciate your patience, lord knows mine is running low
twinlakesnake said:
i downloaded root explorer. deleted install-recovery.sh @ /system/etc. once i did this i was able to use fstboot commands from rom racers page. fastboot erase recovery was successful. then tried 'fastboot flash recovery recovery-atrix5.img'
error: cannot load.
im chipping away at it but wow. thoght i would be flashing cm7 by now. I do appreciate your patience, lord knows mine is running low
Click to expand...
Click to collapse
At this point are you still not able to get in recovery?
finally, success! just figured out what the hell im doing with fastboot. unzipped romracers cwm to same folder containing fastboot, finished last part of cmd (fastboot flash recovery recovery.img then fastboot reboot and voila! i now have rom racers cwm. i will now enter rom manager, backup rom (which i understand is a nandroid process). then start researcing cm7 and eventually some more roms to play with. thanks for all of your help
once recovery was fixed, everything was a breeze. put cm7zip on internal sd, installed from recovery, data wipe then cache wipe, then reboot. iput google apps zip on internal sd, installed from recovery. fancy new phone! only took me 3 days to do it. i hope someone else can learn from my mistakes
twinlakesnake said:
once recovery was fixed, everything was a breeze. put cm7zip on internal sd, installed from recovery, data wipe then cache wipe, then reboot. iput google apps zip on internal sd, installed from recovery. fancy new phone! only took me 3 days to do it. i hope someone else can learn from my mistakes
Click to expand...
Click to collapse
Congrats
I created this thread because I have looked all over and have been unable to find someone with the exact same issue(s).
I said "sort of" in the title because twrp is working. Ok, so before everyone asks if I have nvflash, the answer is no. I did not have the right version of firmware, and did not try to install it originally. Since I was able to install roms, I figured I was fine...oops.
Twrp is not properly installing roms. More on that later. I am getting to the asus splash screen that says my device is unlocked, but it is stuck there.
My last working rom was the deodexed stock JB rom from craig gomez. I installed it with goo and when I installed that, I lost custom recovery and root, so I decided to go back to a more custom rom so Titanium backup would work. When I did that, I tried also tried again to make nvflash work. I got through the first step, it said it was successful, except I never got the little message in the upper left corner that I was supposed to get. I did not think it was a big deal because my prime would still boot like normal.
Then I installed twrp 2.3.1.0 and I have tried flashing previous restore images. I have tried installing the roms on my sdcard. I cannot get past the asus splash screen.
If I try installing a rom with the force md5 check enabled, it does detect an md5 and then quits.
If I try intalling a rom without the force md5 check, i get an error that says E:Unable to mount '/staging'
When I try installing a backup everything seems to work okay, but then I get the same error E:Unable to mount '/staging'
When I try to install roms through fastboot, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I try using adb, I do not see any devices.
I tried putting CWM on the prime to see if I could install from that instead, but it would not load after install.
I tried putting an older version of twrp on the prime, to see if that was the issue because I used to have an older version...I could not get that to load either...so I went back to this version.
Any ideas or suggestions would be awesome guys. I am stuck.
I even went to install the naked drivers again, and when I try to flash a different recovery, I get the <waiting for device> text that never goes away.
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
godlyitem said:
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
Click to expand...
Click to collapse
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
big time noob said:
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
Click to expand...
Click to collapse
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
godlyitem said:
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
Click to expand...
Click to collapse
Yeah, I thought that too, but fastboot does not work properly either...argh. I wish one of the gurus would chime in here.
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
Click to expand...
Click to collapse
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
godlyitem said:
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
That doesn't really help us. If possible, can you edit/delete your message so that the guys that might help do actually help? Don't want them to think this is done.
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
Click to expand...
Click to collapse
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
godlyitem said:
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
Click to expand...
Click to collapse
big time noob said:
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
Click to expand...
Click to collapse
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Thanks. That is what I needed to know.
I will see if I can make this work when I get back from work.
godlyitem said:
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Click to expand...
Click to collapse
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
Download the zip:
http://goo.gl/hiFHB
Goto to Twrp recovery and install the zip..Since it supports microsd u can transfer the zip to microsd.
Goto TWRP -> INSTALL -> CHOOSE EXTERNAL SD -> INSTALL THE ZIP
It will completely wipe the internal storage and then download the official STOCK JB FROM ASUS SITE and follow the same steps to install. Now install the latest twrp recovery using fastboot
big time noob said:
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
Click to expand...
Click to collapse
When I was doing the fullwipe the same errors happened to me.. But dont mind..I got errors like
1. No md5 file found
2. Mount error
3. Cannot find /staging
Just follow the above the steps ull get it right
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Yeah, I should have said I tried that first. I also tried the stock rom from asus. When that didn't work, I tried the stock rom deodexed I found in goo.
There are a bunch of permission errors going on inside my prime. When I go into the mount area, it will not let me mount the data to move it. Or, when I try to copy it over I get a failed message.
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Fixed?
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
big time noob said:
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
Click to expand...
Click to collapse
big time noob said:
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
Click to expand...
Click to collapse
You will have the jelly bean bootloader now so as long as you stick to it you should be fine. The only other thing I would suggest is check you version of twrp, you should be running the jelly bean version of it also. And if I am not mistaken, you need to be on ics to use nvflash (although I haven't checked the op recently so I could be wrong) so definitely stay away from that unless you downgrade.
Hello all. I was successful in rooting my Nook Tablet according to this thread http://forum.xda-developers.com/showthread.php?t=2037368&nocache=1
Unfortunately, when I went to install the CM7 zip, it kept saying, "file not found"
I then read a post about enabling USB Debugging and Unknown Sources. So even though I shouldn't have rebooted, I really didn't have any choice but to reboot and go into settings and enable USB Debugging and Unknown Sources.
Now, I can't get back into recovery to install the .zip despite trying every combination I could think of or find by searching and I've literally been searching for hours.... must be using the wrong keywords because I can't find anything about getting back into recovery that works.
I even went to the Playstore and installed ROM Manager and GOO Manager and tried to reboot in recovery. When the Nook Tablet starts, it just shows and picture of a Nook with a red exclamation mark in the middle of it and says, "Please restart and try again..." or something like that.
Any ideas? Thanks for any response
In terminal emulator : "reboot recovery" or powering off and holding home and power buttons for like 5secs
If you tried booting recovery and it came up with nook recovery then you haven't replaced your internal recovery program to cwm. Instead of cm7 I'll suggest using cm10 because its much more new and essentially is the same thing, just improved.
If you end up not knowing how to internally flash then either read, read, read until you understand or get an SDC image. So many people brick their nooks by not understanding how to internal flash. The SDC image has no risk.
nikufellow said:
In terminal emulator : "reboot recovery" or powering off and holding home and power buttons for like 5secs
Click to expand...
Click to collapse
I tried several times holding the buttons but that didn't work. Terminal Emulator just says, "Operation not permitted." Thanks though.
nikufellow said:
In terminal emulator : "reboot recovery" or powering off and holding home and power buttons for like 5secs
Click to expand...
Click to collapse
datallboy said:
If you tried booting recovery and it came up with nook recovery then you haven't replaced your internal recovery program to cwm. Instead of cm7 I'll suggest using cm10 because its much more new and essentially is the same thing, just improved.
If you end up not knowing how to internally flash then either read, read, read until you understand or get an SDC image. So many people brick their nooks by not understanding how to internal flash. The SDC image has no risk.
Click to expand...
Click to collapse
I was orginally in CWM Recovery when it would let me flash the CM7. The link to the thread in the OP advised that CM7 and the appropriate Gapps needs to be installed first before flashing the CM10 + JB Gapps zips. According to the thread I linked, these ROM's will be flashed to internal. This is the method I've been searching for because I didn't like the SDC image idea... just me.
I wasn't supposed to reboot the NT per instructions but when I forgot to enable USB debugging, it would not let me flash the .zips so I had to reboot the NT to get into settings. Is there a way I haven't read about yet that will enable me to flash the .zips without going through CWM Recovery or is it an absolute must?
Umigobbles said:
I was orginally in CWM Recovery when it would let me flash the CM7. The link to the thread in the OP advised that CM7 and the appropriate Gapps needs to be installed first before flashing the CM10 + JB Gapps zips. According to the thread I linked, these ROM's will be flashed to internal. This is the method I've been searching for because I didn't like the SDC image idea... just me.
I wasn't supposed to reboot the NT per instructions but when I forgot to enable USB debugging, it would not let me flash the .zips so I had to reboot the NT to get into settings. Is there a way I haven't read about yet that will enable me to flash the .zips without going through CWM Recovery or is it an absolute must?
Click to expand...
Click to collapse
You don't need to flash CM7 before CM10. It just replaces it anyways. You just need to replace your current internal recovery with CWM and install the zips. There's no other way to internally flash without using a recovery program.
Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Vant2239 said:
Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Click to expand...
Click to collapse
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
robneymcplum said:
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
Click to expand...
Click to collapse
Once again thanks a lot for reply!
I have successfully ported one of your builds, but with some mindless actions trying to flash recovery through fast boot got a boot loop of some sort, logo keeps appearing and phone doesn't boot.
What I did is in fastboot flashed recovery with help of 'fastboot oem unlock' and now I just stuck. I have stock recovery, tried to flash it back but unsuccessfuly. Any idea how can I fix it?
Sorry for being such a noob
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
robneymcplum said:
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
Click to expand...
Click to collapse
Im getting an error when try to flash it: ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
trying to flash stock firmware?
I had numerous issues getting mine to flash the first time, I downloaded and tried different versions of SPflash tools, different USB leads/ports etc...
I have to use a USB lead from my moto x play as the stock lead wouldnt work, my galaxy tab lead wouldnt work either.
I have to use SPflash tool version SP_Flash_Tool_exe_Windows_v5.1552.00.000 as other versions kept bringing up that error and similar ones.
It really does seem to be trial and error unfortunately.