Related
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
mrnexus said:
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There is a .sh file that needs to be removed, totally forgot the location of it :/
/etc/install-recovery.sh needs to be deleted or renamed.
It's a "safety" feature in 3.3.1 and above to restore the stock recovery if it doesn't pass a check on boot each time.
This is pointed out in numerous threads...search a little for more details if you need them.
Ok thanks
Sent from my Nexus S using XDA App
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
mrnexus said:
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
distortedloop said:
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
Click to expand...
Click to collapse
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
EDIT: Nevermind, I used root explorer and was able to find "mount r/w" and rename it finally. Thanks.
godzigga said:
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
Click to expand...
Click to collapse
Because those won't allow you to modify system files. Get Root Explorer, like he said, and use that.
AllGamer said:
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
Click to expand...
Click to collapse
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
sarge363 said:
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
True, I used adb, spent like 2 hour trying to get the pc drivers to recognize the nexus. I used the PDAnet drivers eventually.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Are you on a custom ROM like CM or Bionix? They remove the script that rewrites stock recovery.
If you're on stock, what version of it are you on? 2.3.1 and higher have a file called /etc/install-recovery.sh on them, and if that's there it should be reflashing stock on every boot, whether you renamed the image you flashed to recovery or not...
so i have a samsung galaxy s 4g that is rooted with superoneclick. right now i have clockworkmod recovery 3.2.0.0. i like amon ra much better. i had this on my G1.im trying to flash 2.2.1. i cant seem to get it to flash. in terminal emulator it doesnt recognize the command "flash_image" it is "not found". i have adb setup but when i try "adb root" i get a message "adbd cannot run as root in production builds" i cant seem to get into bootloader by holding down buttons or by using "quick boot" i tried rom manager, "flash alternate recovery" is greyed out. please help!
No amon ra or ROM manager for this phone.
Sent from my SGH-T959V using xda premium
jager555 said:
No amon ra or ROM manager for this phone.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Is the 3E stock recovery the only reason?
I don't understand why its not an option....
Was it built for this phone?
Sent from my SGH-T959V using xda premium
A bunch of things you need to know for galaxies vs aosp
1. I also came from a g1. I loved it.
2. AOSP, Sense, Motoblur.etc excluding Touchwiz(These types run on the basic file format. Install rom from a signed zip, start up using a bootloader spl, you must be familiar with hardspl. A boot.img, this is the kernel, and a zip with /system, and other stuff. Also a recovery.img(Amon Ra). And a modem.img
3. Those phones have a posibility for ADB Remount command and fastboot.
eg adb remount, or fastboot flash recovery.img
4. Touchwiz is Galaxy. They run on 2 bootloader binary files, a zImage as a kernel, and mainly the /system partition called factoryfs.rfs is stockly available on a computer flashable tar file which has the files. The tar files usually with files that include factoryfs.rfs, datafs.rfs, cache.rfs, param.lfs, boot.bin, sbl.bin, zImage and modem.bin.
5. Factoryfs = /system zip datafs = /data partition cache = /cache partition, param includes core files like splash image 1 for the g1, and boot and sbl are bootloader, zImage = boot.img with different coding, modem.bin = modem.img
6. zImage contains the recovery.img partition on GB and the /system partion has recovery in froyo roms.
7. Touchwiz has odd mounts, and flashing alternate recoveries has the potential to make your phone an expensive paper weight.
8. There is a feature kind of like boot loader and spl mode for g1(rainbow screen) called download mode. This is where you connect to the computer to flash the big tar files.
9. The smart devs have created a clockworkmod recovery, which has more functions then amon ra and allows you to flash zip files with sgs4g roms.
10. Boot animation cannot be changed unless you have a kernel supporting them. Instead of bootanimation.zip, they use 2 files called bootsamsung.qmg, and bootsamsungloop.qmg
11. DON"T FLASH ANYTHING NOT MADE FOR THIS PHONE, ESPECIALLY BOOTLOADERS AS THEY MAY MAKE YOUR PHONE UNUSABLE, THE REST USUALLY CAN BE RECOVERED.
so is there a way to backup/restore my galaxy s like i could my G1
1. the galaxy s 4g is not a G1
2. yes, you can back it up by going to "backup and restore" in CWM and then clicking "Backup". this will back everything up.
you can restore by choosing the same option in cwm, but "restore" once in the menu.
if you are on a rom that you want to keep, you can go to advanced restore in the backup/restore menu and restore only your data.
gdofwar has a tutorial out on how to backup/restore the phone. does this help?
when i go into ROM Manager and click "backup current rom" it takes me to the screen in the picture. there are no backup options. incase you cant see the pic. the options are:
reboot system now
reinstall packages
delete all user data
delete cache data.
lokeycmos said:
when i go into ROM Manager and click "backup current rom" it takes me to the screen in the picture. there are no backup options. incase you cant see the pic. the options are:
reboot system now
reinstall packages
delete all user data
delete cache data.
Click to expand...
Click to collapse
ROM manager does not work on this phone. You cant use ROM manager. ROM manager does not work.
Sent from my SGH-T959V using xda premium
Exodian said:
ROM manager does not work on this phone. You cant use ROM manager. ROM manager does not work.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
so what can i do?
Omfg
Sent from my SGH-T959V using xda premium
Dev section krylon 360 cwm final thread. Read it follow it.
Sent from my SGH-T959V using xda premium
Bali on Froyo. drhonk's GB kernels.
Sent from my SGH-T959V using xda premium
Cool THank you for the thread! i have the update.zip on my sd card. when i try to push the other file it says "failed to copy 'recovery' to '/system/bin/recovery': Read-only file system" how do i work through this? thank you much!
jager555 said:
Omfg
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
You read my mind with that post. LOL
htaak said:
You read my mind with that post. LOL
Click to expand...
Click to collapse
Im looking for help not criticism. im obvisously not on your level.
ok. look for the bali 3.3uv threads. odin this file using the instructions in the thread. this will give you the proper cwm and root.
lokeycmos said:
Im looking for help not criticism. im obvisously not on your level.
Click to expand...
Click to collapse
I hope you are above my level LOL.
It wasn't meant as criticism, Jager just happened to post exactly what I was thinking at the moment I was thinking it as I read through the thread, and it made me laugh. It was like a mini version of Monty Python's Dead Parrot Sketch.
I sincerely apologize if it came over that way. I am not here to argue with or upset anyone.
lokeycmos said:
Cool THank you for the thread! i have the update.zip on my sd card. when i try to push the other file it says "failed to copy 'recovery' to '/system/bin/recovery': Read-only file system" how do i work through this? thank you much!
Click to expand...
Click to collapse
Flash, not push. Unless you're rooted, the file system is set to read-only. If you are rooted, download root explorer or any other file system explorer, set to R/W, and push again.
To flash, boot to recovery and select the update.zip option (don't remember exact wording).
Sent from my SGH-T959V using xda premium
neocorteqz said:
Flash, not push. Unless you're rooted, the file system is set to read-only. If you are rooted, download root explorer or any other file system explorer, set to R/W, and push again.
To flash, boot to recovery and select the update.zip option (don't remember exact wording).
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
if you do it this way for the love of god dont forget to remont the system as r/o after you copy the recovery file to the system bin folder ....
Hi,
I tried the trickdroid ROM but i dont see any benefits, instead there are downsides, like wifi disconnecting and so on. I would like to go back to the original Stock ROM but i do not have the boot.img and nandroid does not back it up along with my backup. Without it, my wifi does not work.
Where can i get this boot.img, or can someone give it here? Thanks!
onlinechi said:
Hi,
I tried the trickdroid ROM but i dont see any benefits, instead there are downsides, like wifi disconnecting and so on. I would like to go back to the original Stock ROM but i do not have the boot.img and nandroid does not back it up along with my backup. Without it, my wifi does not work.
Where can i get this boot.img, or can someone give it here? Thanks!
Click to expand...
Click to collapse
http://www.4shared.com/file/k-UJs2Eo/RUU_VILLEC2_U_ICS_40_hTC_Asia_.html?aff=7637829
You can try this stock. by the way , I'm using Trickdroid V1.0,I do not have WiFi problem at all.You have to manually flash the boot img using fastboot.
i have strange problems where my 3g or wifi will stop connecting on TD. Even if i go to airplane mode it does not recover. I have to reboot phone. But last time i did not do a backup of my boot.img.. thats why i need it now
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
onlinechi said:
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
Click to expand...
Click to collapse
RUU file is a install script setup launcher where you can install onto your window then connect your phone to usb , execute this file , then follow the instruction on the screen . I do not have the boot img.
onlinechi said:
Is it possible that i just get the boot.img instead of downloading the whole giant file? thanks!
Click to expand...
Click to collapse
Possible to extract only the boot.img but not without downloading the whole big file.
Open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One S, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
Code:
fastboot flash boot boot_signed.img
-----------------
This was copied from a thread in One X made by Setsuna666 and pasted there from user: torxx (http://forum.xda-developers.com/showthread.php?t=1609190), but applies for any RUU file extraction. It is not from me, but this method works.
A newbie, I rooted my phone and was trying to figure out EZRecovery. Ended up bricking the phone and installed a stock image using Odin, but that is a separate issue about which I may write a separate question.
After I installed the stock image, I noticed that there is a folder on the SDCard entitled gs3recovery and inside are 6 files named as follows: 2 (0 bytes), recovery_hyb_invisibleckv2 (5.44MB), recovery_rec_CWM6010 (5.41MB), recovery_rec_CWMT5849 (6.34MB), recovery_rec_stock (6.10MB), and recovery_rec_twrp220 (6.96MB). The latter 5 are all Disk Image Files.
When I was trying to use EZRecovery, I went looking for images in TRWP and CWM folders and didn't find any. Are these the images inside the gs3recovery folder or are they too small to be images?
Could these images be used if I rerooted?
What images are you trying to find? The images in that folder are when you open ezrecovery and use the drop down box to select a recovery to flash, those are the recoveries.
Sent from my SCH-I535 using xda app-developers app
Those are the recovery images that EZRecovery uses to flash a specific recovery onto your phone. There only usable if your rooted, so if you aren't its safe to delete that folder.
kintwofan said:
What images are you trying to find? The images in that folder are when you open ezrecovery and use the drop down box to select a recovery to flash, those are the recoveries.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your reply.
So let me confirm that you're saying these are images that I could recover using EZRecovery?
I thought that was probably the case, but I had expected the images to be a lot larger than 5-6MB.....like on Windows PC 7 where the image is more than 50% the size of the system drive.
Those are the recovery images. You could even use terminal to flash them using.the dd commands. The app does it for u
Sent from my SCH-I535 using xda premium
Thank you all for responding. Basically then, I have images I could restore but I will have to root to do so.
I won't go into the whole story, but I have to root anyway because I restored a stock image to the bricked phone while the bootloader was unlocked.
I am planning to go back to stock but I can't do that until the bootloader is locked and I have to root in order to do that.
Thanks again.
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit
alteredlikeness said:
Well, first, turn off the phone and charge it so you don't loose battery.
Second, never install another recovery on top of an existing one without knowing what you are doing - ask first.. (You get into the built-in recovery on that cm10.1 by tapping the volume down button at the end of the red moto logo when the lights come on).
Next, you could possibly fix your system with adb and switching some files.. but that would take a lot of explaining if you are not familiar with it.. plus, you might not get adb recognized during the bootloop.
So, you need to use the FXZ files for your phone/region... Or, just flash the system.img only.. See here: http://forum.xda-developers.com/showpost.php?p=41436876&postcount=1106 - and see the link linked there.
EDIT: If you can get adb recognized, you might be able to just run these few lines to fix things from the command prompt:
Code:
adb shell
su
mount -o rw,remount /system
rm /system/bin/hijack
sh /system/bin/finalize_release
exit
Click to expand...
Click to collapse
do you know any other place to download the zip file
and wheres the fxz folder supposed to be
DaFrenchTaco said:
do you know any other place to download the zip file
and wheres the fxz folder supposed to be
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app
nikhJ said:
Look here
http://forum.xda-developers.com/showthread.php?t=2176124
Make sure you install the correct firmware otherwise you will brick.
And next time please search before posting. This has been asked a number of times before
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737
DaFrenchTaco said:
sorry for asking u so much stuff but i lost without help
ok so it says i have to edit it with the moto android depacker but i dont see any tutorials on how to do that
would it boot up if i use this hack to install the honk kong boot img on to it or would mess my device since its on "4.2.2." http://forum.xda-developers.com/showthread.php?p=35000737
Click to expand...
Click to collapse
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.
alteredlikeness said:
I am very confused at what you want to do. That link is only to root your device. But, if you are bootlooping, you need to replace your system.img.
You should download the entire SBF/FXZ zip file for your device/region/firmware. Then unzip it into a folder on your computer (best if it's close to C:\ with spaces in the path). Are you using a Windows OS on your computer?
Then, grab the restore-to-ics_win-batch.zip AND the restore-ics-system-only.bat.txt (remove the .txt extension) attached in this post: http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Mix those files in with the big FXZ files that you just unzipped. Then run the .bat file to flash the system.img only. If that doesn't work, then open the other .bat file (use Notepadd++ or similar), check that everything that is being flashed is actually in your folder and has the same name... and flash the entire FXZ. If none of that helped, then you probably flashed the wrong files to your phone.
Just flashing the system.img only is probably the safest.. Because if it's wrong, you can just flash another one. The other files in the FXZ package can mess up your phone if they are not for your specific device.
EDIT: If you still did not flash anything else, you could try to use adb... Get that restore-to-ics_win-batch.zip that I linked above.. Unzip it to your desktop. Power on your phone so it bootloops and connect with USB. Open a command prompt on the restore-to-ics_win-batch folder by holding down shift and right-click. Then type adb devices - if it returns a number with the word "device" (not the word "offline"), then you can try to use those adb codes I posted in my previous post. Otherwisem you need to use fastboot and flash fxz or system only.
Click to expand...
Click to collapse
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed
DaFrenchTaco said:
can not load "system.img" i went in and edited the the text to C:\system.img but it wont work
i tried the other one didnt work is the path supposed to be = C... or =C... what i mean is there a space or not
is the bat file scripted to work with me865 or only with mb865 flashing that sbf/fxz
and is the sbf/fxz file supposed to be unzipped and in a folder
or compressed
Click to expand...
Click to collapse
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat
alteredlikeness said:
Unzip the sbf/fxz - all the files in a single folder, on your desktop or in the root of your C:\ drive (like C:\ InlineFlashing_Edison_XX-XX-XX_CFC_P3_APBP.xml - where that is the name of the folder)
Then put the .bat file and other files from my restore_to_ics zip and the restore_system_only .bat in that same folder.
Then, connect with USB while in AP fastboot mode, see if it says "OK to program", then double-click the restore-ics-system-only.bat
Click to expand...
Click to collapse
thank u so much is it safe to root and install cm10 with bootstrap?
and how do you enter cmw in cm10.1?
THX
Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app
Aceofzeroz said:
Sorry to intrude with my following off-topic statement, but that was a lot of detailing you did there altered. xD Great job and it'll serve well to assist others who need the same solution.
Now on-topic;
Yes it's okay to root with any of the ICS root methods available.
Sent from the Ace's MB865 using xda app-developers app
Click to expand...
Click to collapse
yeah true that this is a very detailed guide/thread i hope my problem will help all the others now that i know how it feels to mess up a two day old phone
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
Ah..sorry my bad..Forgot his phone was me865..
Question about the original problem
DaFrenchTaco said:
im stuck in a loopboot on my ME865 after installing 4.2.2 from this http://forum.xda-developers.com/showthread.php?t=2121029
i flashed the rom but didnt flash the gapps because it said to do it after with built in recovery but i didnt know how to so i used this http://forum.xda-developers.com/showthread.php?t=1346977
which got me into the loop boot i can boot into fastmode
PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Did you solve this? I have the same problem...
---------- Post added at 10:17 PM ---------- Previous post was at 10:01 PM ----------
alteredlikeness said:
No. Those are only MB865. And those are only for gingerbread..
The 4.0.4 ME865 ones are here: http://forum.xda-developers.com/showthread.php?t=1934874
Also, it's a little outdated, but see here too: http://forum.xda-developers.com/showthread.php?t=1909319
Which should all lead you here: http://sbf.droid-developers.org/edison/list.php
Sent from my manta ray
Click to expand...
Click to collapse
I encounter the same issue. I am not able to see the device in ADB.exe, but I am able to see in FASTBOOT.exe
Can I flash in FASTBOOT.exe?
Thank you
pa 3.60 problem from altered likeness
I tried to install Paranoid android 3+ from the link from altered likeness which was successful but the problem started after rebooting .The animation goes on forever and the first time the reboot gave me a message stating updating android system . Any solution to get back would be of a lot of help .I also have the recovery of my stock 4.0.4 done using CWM .
Same problem extension
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out
Thnks guys
kyashwanth said:
Hi....
I faced the same problem and now after following the procedure facing a new prob.
Things I did
1. Upgraded from ICS to CM10.1--->Success
2. Forgot to install GAPPS ..so installed Atrix2Strap.apk (Bootloop problem started)
3. Flashed my atrix 2 with the procedure mentioned in the link by alteredlikeness.(Overcame the bootloop problem)
Now the problem is
I'm getting the lock screen but when I try to unlock it stays unresponsive.
How do I solve this. Please Help me out
Click to expand...
Click to collapse
Thanks guys for the wonderful tutorial...
Solved the issue by inserting a sim card into the phone.
Now I'm on CM 10.1