[Q] me860 confusions? - Atrix 4G Q&A, Help & Troubleshooting

i have rooted atrix me860 4.5.2A.74.OLH-25 running stock 2.3.4 (rooted with doomlords/zergrush exploit method). bootloader is still locked. i am unable to enter clockworkmod recovery "failed entering boot 2" error.
some confusions since most of the section is labelled with mb860..?
1-which rom can i flash without unlocking boot loader?
2-can i flash roms meant for mb860?
3-can bootloader be unlocked after rooting or it has to be unlocked first?
4-are the procedures given here to unlock bloader for mb860 can be used for above me860?
using these phone in india.
thanks for help.

http://forum.xda-developers.com/showthread.php?t=1302423&highlight=me860
tried my luck and did it!!
after rooting i followed above link
to unlock.
in first attempt (bell sbf) i got stucked, i did battery pull & unlocked with fastboot as stated in above link in 2/3 attempts though.then flashed recovery. by this time i was unable to boot "no os detected". after searching i did battery pull and powered with vol down continuosly thus i reached android recovery, pressed vol up and entered recovery.
from recovery flashed topsmart rom as per developers instructions and booted in successfully. its working very well.
NOTE:do a full charge before attempting.
PROBLEMS:
1)my internal sd memory is not mounting/unusable, but external SD 32GB working good.
2)every time i reboot a screen showing some 10 boot options comes before boot animation, i dont know whether its normal or not?
but its working very well.

Related

[Q] Clcokworkmod CWM recovery "Fails to boot 2"

After first getting my Atrix I used tenfar's recovery to install one of the first Proms. I cant remember which now.
I have since used Atrix ATTT 2.3.4 Pudding preroot SBF through RSD lite to update to 2.3.4. I would now like to go to CM7.
I have installed the latest Rom Manager and it says I successfully updated to the latest CWM. When I try to reboot into recovery - I get
"Failed to boot 2"
"Starting RSD"
The only way i've been able to fix it is to reflash the preroot SBF.
What am I doing wrong?
welcome to the club my friend. you have to unlock the bootloader and your golden
more info. if you follow the thread more. you will need to run fast boot to obtain this. once you run fastboot. type in fastboot oem unlock. it will then give you the uniquee device id.
power down remove battery if you have. restart the phone in fastboot mode. type in fastboot oem unlock plus the unique id number let it run through process. phone will say unlocked when it reboots. then go ahead and install rom manager and flash the cwm. once installed reboot using rom manager to get into cwm and flash rom
SErooted said:
welcome to the club my friend. you have to unlock the bootloader and your golden
more info. if you follow the thread more. you will need to run fast boot to obtain this. once you run fastboot. type in fastboot oem unlock. it will then give you the uniquee device id.
power down remove battery if you have. restart the phone in fastboot mode. type in fastboot oem unlock plus the unique id number let it run through process. phone will say unlocked when it reboots. then go ahead and install rom manager and flash the cwm. once installed reboot using rom manager to get into cwm and flash rom
Click to expand...
Click to collapse
Thanks for the tip! When I do this, though, fastboot hangs on "Waiting for device." Am I doing something wrong? I'm using a Mac, so re-installing drivers isn't the issue.
It's most likely a permission problem. Run fastboot as root/administrator/whatever macs have.
It for sure is the locked bootloader problem. I had though i had unlocked the bootloader and tried to install CWM through rom manager and it put the same error up. I flashed pudding again and then made sure to do the oem unlock commands that i had apparently overlooked
Thats what i am thinking too. that it is the locked bootloader issue. i had this the other day when i attempted to cwm and rom install. thanks to Turl1 and a few others, i was able to have it taken care of in no time.
http://www.briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Sent from my MB860 using XDA App
This was quick & easy, thank you!

[Q] unable to run any recovery

hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Have you tried downloading the twrp pg86img.zip & make sure it's named PG86IMG.zip then put it on the root of you're sdcard, boot into bootloader and update that way?
CM powered EVO 3D, enough said.
luca73n said:
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Click to expand...
Click to collapse
when the device either hangs on the htc logo or reboots while on the htc logo, it means there is an issue with the actual kernel/ramdisk.
when dealing with a custom recovery, they should always boot without any issues. the best suggestion off the top of my head is to make sure if you're on the CDMA version, use the shooter recovery and if you're on the GSM version, use the shooteru version of the custom recovery.
otherwise, as suggested above, reflash the confirmed correct custom recovery for your device. there are a few ways to flash the custom recovery although, being you used the htc unlock method, regular custom recovery mode will not have write access to the boot/kernel partition.
if you're interested in loading any ROMs which come with kernels or separately flashing a custom kernel, there are essentially two complete methods:
1) use my Flash Image GUI app from normal android mode to flash the kernel. then flash the ROM from custom recovery.
2) use fastboot boot c:\android\cwm-recovery.img . this will temporarily boot the custom recovery and htc unlock will grant it write access to the kernel/boot partition. this command is different than fastboot flash recovery c:\android\cwm-recovery.img. the fastboot boot will temporarily boot into the custom recovery while fastboot flash will permanently write it into the recovery partition.
hope all the extra details make sense and helps!
Ummm.....Just my 2 cents, but it sounds as though the most basic possible problem has been overlooked here. You need to go into menu>settings>power and uncheck the "fast boot" box or do a battery pull, then try to boot into your bootloader to access recovery. With your phone completely powered down (fast boot unchecked or after battery pull), hold volume down and press power. That will put you in your bootloader with an option to boot recovery from there.
ok i'm a noob i've used thr shooter and not the shooteru cwm img, now all works
ty guys

ugh 4.5.141 help needed

Ok so after getting 4.5.141 to load via motos update I attempted to root the phone. Which by all accounts looked like it worked however....
My phone does not appear to still be BL unlocked, and there are no apps in the list under superuser. I downloaded CWM and tried flashing then going into recovery and that fails even through prompted for SU by the apps it says it work etc.
Now I cannot even get into recovery via any method. Via CWM it errors with a message cannot boot 2 error then loads rsd mode. Via power on/vol dwn it just gives the android dude with ! in the triangle.
Ok so how do I fix this? I need to be able to root, unlock the BL (if even possible) and fix my recovery partition. (any command used from fastboot fails I suspect its still a permissions root issue)
Any help is appreciated.
NVM I fixed it.
I re-ran the unlock process what was funny is when I flashed the sbf to unlock the BL the screen immediately showed the "unlocked" in the upper left hand corner. When I went to do the fastboot oem unlock part it said already unlocked. (I tried this earlier and it kept failing I think cause I forgot the sbf.
I then went through the steps to re-root it, then re-flashed the newer CWM and now I am able to get into recovery etc.

Can Someone Please Help?

This is an exerpt from a previous thread. I am at a loss and ready to junk this phone.
Originally Posted by Ninjistix
okay i just read this whole thread and i'm completely lost as to what your trying to do.. first off if your boot loader is still locked and you want to flash back to stock you need to download the correct RUU file for your carrier... if you supply that information i can help you look for the right one.. then you rename that file to ph85img.zip and place it on the root of your SD CARD and boot into bootloader by removing your battery and placing it back in and "HOLDING" volume down and the power button until you are in the bootloader menu... after that its just following the instructions to flash back to stock
these are the instuctions to Unlock Bootloader > FLASH 4EXT > ROOT > Flash ROM
download hasoon's AiO toolkit and instll the htc usb drivers...
use the toolkit to unlock the bootloader if not go to htcdev.com and follow the VERY easy instuctions listed there... (you can skip the first few about installing android sdk)
after you unlock your boot loader proceed to flash your recovery (id suggest using 4EXT since your prob S-ON)
once you have a custom recovery you can proceed to flash the super SU file including in the aio toolkit
then make a "NANDROID" backup of your phone using 4EXT before you continue to flashing any roms
the rest is simple just download what roms you want and read the instructions to flashing the rom..
------
I have done all of this to the T back when I originally started this thread and now that I tried it again today. When my phone is booted to bootloader using the toolkit it is just a black screen. When I unlock the bootloader using the token I received from the HTC Dev site the toolkit says it was unlocked successfully. I then flashed custom recovery that it says was done correctly. Then when I boot into recovery it is goes to a picture of a phone with a green circle of arrows for 5 seconds then a phone with a red triangle and exclamation point. If I play around mashing buttons I can get into the stock recovery with blue letters and options to restore (doesnt work, many errors) and 4 other options. It is like my screen is messed up and will not show the bootloader/hboot screens. I have never been able to see the screen with the option for fastloader before which other people can see. Does this make any more sense? When I boot my phone it is a black screen until I see the bleedover from the soft keys, then I have to press the power button to turn screen off and back on for the screen to start working. After that it always works fine!?!?!?! What is wrong here?!? Its like I should just load the stock firmware and start all over but I cannot see the screen to select fastloader so it will recognize the PH#### file I have downloaded and loaded onto my SD Card. I am at a loss over here!
How did u flash the recovery? Was it with the all in 1 toolkit?? Are u s-off???
Sent from my Amaze 4G using xda app-developers app
Ok so you flashed 4ext... Now use the toolkit to root the phone... Then flash the appropriate RUU (not just any rom)
(ruu may relock bootloader)
Boot
Try your recovery...
I hope your recovery has your contacts etc but I expect it won't... If you were ics flash ics.. If you were gb you can flash either..
Boot... Fingers crossed...
If you are s-off and rooted.. Unlock CID (sticky)
If everything has worked you should be Ok.....
Also if you are lucky Google will have copy's of your contacts and calendar etc thanks to autosync
e-Sex.. All of the carpral none of the tunnel

No Rom or Back Up on My Phone!!!

So I screwed up and cleared my wiped my phone then when I went to flash CM 11 from Pacman I got a failure so I couldn't flash the ROM and it cleared out my Pacman as well so I didn't have any ROMs on my phone and no ROM installed so it would just boot to recovery (i use TWRP). When i tried to put a ROM on to my phone through my computer I got an error and when I tried to use the ADB Sideloader but it just got stuck saying"waiting for device." So I went ahead and re-locked my boot loader and tried to restore the phone with the stock RUU but it just fails every time and I have let it run for an entire day before. So at this point I have an AT&T HTC One that boots to a boot loader then says tampered, re-locked and security warning on the top i can use fast boot (but not sure what to do with it) no ROM to boot to, and cant get to TWRP (unless I unlock boot loader again). Any recommendations would be very helpful.
crabbymonkey said:
So I screwed up and cleared my wiped my phone then when I went to flash CM 11 from Pacman I got a failure so I couldn't flash the ROM and it cleared out my Pacman as well so I didn't have any ROMs on my phone and no ROM installed so it would just boot to recovery (i use TWRP). When i tried to put a ROM on to my phone through my computer I got an error and when I tried to use the ADB Sideloader but it just got stuck saying"waiting for device." So I went ahead and re-locked my boot loader and tried to restore the phone with the stock RUU but it just fails every time and I have let it run for an entire day before. So at this point I have an AT&T HTC One that boots to a boot loader then says tampered, re-locked and security warning on the top i can use fast boot (but not sure what to do with it) no ROM to boot to, and cant get to TWRP (unless I unlock boot loader again). Any recommendations would be very helpful.
Click to expand...
Click to collapse
Unlock it again, run the ruu exe.
Only reason to go through the relock **** is to warranty it.
Sent from my One using Tapatalk
crabbymonkey said:
So I screwed up and cleared my wiped my phone then when I went to flash CM 11 from Pacman I got a failure so I couldn't flash the ROM and it cleared out my Pacman as well so I didn't have any ROMs on my phone and no ROM installed so it would just boot to recovery (i use TWRP). When i tried to put a ROM on to my phone through my computer I got an error and when I tried to use the ADB Sideloader but it just got stuck saying"waiting for device." So I went ahead and re-locked my boot loader and tried to restore the phone with the stock RUU but it just fails every time and I have let it run for an entire day before. So at this point I have an AT&T HTC One that boots to a boot loader then says tampered, re-locked and security warning on the top i can use fast boot (but not sure what to do with it) no ROM to boot to, and cant get to TWRP (unless I unlock boot loader again). Any recommendations would be very helpful.
Click to expand...
Click to collapse
what ruu are you trying that fails? when does it fail ?
go here and get the correct way to reset you phone to stock
http://www.htc1guru.com/downloads/stock-rom-downloads/ Guru Reset
Thats the same one and I downloaded the RUU for the forth time and it worked I guess I got unlucky. all is good now thanks for the help.

Categories

Resources