Related
Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.
Hello everyone,
Before I describe the issue I have been experiencing, I would like to say thanks in advanced for providing me assistance.
Okay currently, I am running.905 base band, and have followed the method for flashing back to .902(FXZ) in order to receive the .905(OTA), and have rooted my device using the moto-fail exploit. The issue I have been experiencing is persistent boot loops when flashing any ICS ROM(I am using CWM 4.0.1.5) via Bionic Bootstrap.
The procedure I have been using(assuming I am rooted and on .905),
Boot the device into recovery(CWM via Bionic Bootstrap)
Wipe Data/Factory Reset.
Wipe Dalvik, and System.
Apply update from SD-CARD(Initial ROM).
Apply update from SD-CARD(correct GAPPS for build).
Reboot ----->> Then the device boot loops.(I restore the device using the FASTBOOT Method).
I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs.
Is there anyone else experiencing this issue? or does anyone have a recommended solution(other than using safestrap)?
Thanks again!
Most, but not all, ROMs require GApps. Make sure the one you are installing does.
There is now a .905 FXZ that you can use to shorten the waiting time.
Make sure you are NOT using Bootstrap for ICS .
Most ROMs already wipe /system as a party of the install procedure.
*** MAKE SURE YOU ARE USING A ROM DESIGNED TO BE INSTALLED IN BOOTSTRAP AND ONE THAT IS NOT DESIGNED TO RUN ON THE ICS LEAKS.
HTH
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
johnlgalt said:
There is now a .905 FXZ that you can use to shorten the waiting time.
Click to expand...
Click to collapse
Where?
The one that has been available for download is not a true zip.
It fails in RSD and no zip utility can decompress it.
I've tried downloading from 3 different sources.
-s
Atheistnofaith said:
Hello everyone,
Before I describe the issue I have been experiencing, I would like to say thanks in advanced for providing me assistance.
Okay currently, I am running.905 base band, and have followed the method for flashing back to .902(FXZ) in order to receive the .905(OTA), and have rooted my device using the moto-fail exploit. The issue I have been experiencing is persistent boot loops when flashing any ICS ROM(I am using CWM 4.0.1.5) via Bionic Bootstrap.
Thanks again!
Click to expand...
Click to collapse
Are you installing one of the ICS releases like AOKP or CM9 or are you trying to install an ICS Leak?
If you're trying to install one of the official ICS Leaks, they will only flash in Stock Recovery.
suprsidr said:
Where?
The one that has been available for download is not a true zip.
It fails in RSD and no zip utility can decompress it.
I've tried downloading from 3 different sources.
-s
Click to expand...
Click to collapse
It's there, it's not an OTA, it is a true FXZ, given to us one week ago.
If the file you are downloading is less than 300MB it is definitely not the right one. The file name is the same as the .902 FXZ except .902 is replaced by .905.
I don't have the link on my phone, but PM me and i can link you to it back here tomorrow.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
johnlgalt said:
It's there, it's not an OTA, it is a true FXZ, given to us one week ago.
If the file you are downloading is less than 300MB it is definitely not the right one. The file name is the same as the .902 FXZ except .902 is replaced by .905.
I don't have the link on my phone, but PM me and i can link you to it back here tomorrow.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
Click to expand...
Click to collapse
I just tried again w/ the one listed http://forum.xda-developers.com/showthread.php?t=1328100
VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip ~488MB
and you cannot use it in RSD as it will fail and you cannot unzip it
7zip:"Can not open file 'VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip' as an archive"
I found it listed 3 different places and DL'd all each w/ same result.
I spent all day last Thursday flashing different ROMs and each time I had to use the OTA to get to .905 if this VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip had worked it would have saved me hours.
If you know where I can find a working version you would get my vote for president.
-s
suprsidr said:
I just tried again w/ the one listed http://forum.xda-developers.com/showthread.php?t=1328100
VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip ~488MB
and you cannot use it in RSD as it will fail and you cannot unzip it
7zip:"Can not open file 'VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip' as an archive"
I found it listed 3 different places and DL'd all each w/ same result.
I spent all day last Thursday flashing different ROMs and each time I had to use the OTA to get to .905 if this VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip had worked it would have saved me hours.
If you know where I can find a working version you would get my vote for president.
-s
Click to expand...
Click to collapse
Though I haven't tried it, this one might be the correct one, it's about 512 MB in size.
http://rombot.droidhive.com/ROMs/targa/fastboot/VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip
**Disregard, it is only listed as being 512 MB, it is actually the same as above.
Hey,
This is a pretty long post, so if all you're interested in is the 905 FXZ file, scroll down to the "FXZ to 905" section, it's bolded.
Problems with flashing ICS ROMs ( in regards to OP, by Atheistnofaith ) :
You may already know this, but each custom ROM is "built off" of one of the stock roms, flashing from a different starting point will often cause your phone to not boot correctly ( boot loop, or freeze at the Motorola logo ), or will boot, but not work correctly ( i.e. something like data will not work ). This, combined with the fact that many new ICS ROMs are built on the ICS leaks, could account for the problem ( Are you sure you're not trying to flash a ROM built on an ICS leak? That would definitely not work! ).
Another possible issue is that you are using the Bionic Bootstrap program to flash CWM. The version of CWM flashed by that program is rather old ( 4.x.x.x vs current: 5.x.x.x ). You may not like this, but Safestrap is the way to go. Before you defer me to the OP, "I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs." I want to point out that Safestrap is not for the purpose of Dual-booting ROMs, or at least, that's not how many people use it. Safestrap has many features that will: prevent being stuck at bootloops ( and needing to re-Flash 902/905 every single time ), allow you to always have a backup system ( i.e. I've soft-bricked the side that I flashed ROMs on, and since I needed to use my phone, I just opened safestrap ( battery pull, start booting phone, and hit the menu button at the Safestrap prompt ), and toggled safe system in the safeboot menu. This brings up another advantage of Safestrap: you don't need to be able to boot the phone to access CWM, installing safestrap adds a new bootup prompt that either lets you open safestrap or boot normally. Again safestrap is based on a much newer version of CWM, so if you don't want to install it for any other reason, install it for that one...
Setting up for, and using Safestrap:
So if I've convinced you that you want to use Safestrap ( I really recommend you do ), follow the instructions given here: http://forum.xda-developers.com/showthread.php?t=1771993 until step 10. Then root with motofail, and install Safestrap 2.0 ( download it here:
Code:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1328100&v=1&libid=1343056993296&out=http%3A%2F%2Frombot.droidhive.com%2FROMs%2Ftarga%2FBionicSafestrap-ICS-2.00.apk&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D1006&title=%5BLIST%202012-07-18%5DOne%20Stop%20Shop%2C%20ROMS%2C%20MODS%2C%20SCRIPTS%2C%20TOOLS%2C%20ROOT%2C%20BOOTSTRAP%20-%20xda-developers&txt=2012-06-22%20Safestrap%20v2.0&jsonp=vglnk_jsonp_13430595105542
). The file should be an apk, just install it on your phone, open it, and select the option to flash it.
If I haven't convinced you to use Safestrap, go to the section titled, "Picking a compatible ICS ROM". ( Then reconsider, and come back, lol ).
When you're ready to flash a ROM, power off the phone, turn it back on, while booting, a new screen will pop up, saying something like "Safe system: Disabled", while that screen is shown, hit the menu button. The screen will temporarily go blank ( Don't panic ), then it should enter a CWM-like setup ( it looks very similar and functions the same ). Now's a good time to do a full backup ( Same as CWM ). From there, go to safeboot menu, then go to toggle safe system ( Don't do quick toggle ). This will take a few minutes. Next flash the zip like you normally would with CWM. If All goes well, you can exit that ( same as CWM ) and the ROM should boot. If it doesn't ( give it at least 5 minutes though ), do a battery pull, and power on the phone again, going into the Safestrap menu like before ( hit the menu key at the screen ), and then go to the safeboot menu and toggle safe mode ( DO NOT QUICK TOGGLE NOW!!! Doing this will require you to re-FXZ ). After that finishes, reboot and your phone should be back to stock, ready to load a working ROM on it.
Picking a compatible ICS ROM:
As mentioned before, each ROM is built on a certain OTA release, like 905 or 902, or even the leaked ICS OTAs. Any ROM that say "ICS" and "LEAK" in its name is not for 905, or anything prior. For a list of 905 based ICS ROMs, check this out: http://rombot.droidhive.com/ROMs/targa/ ( Make sure you don't install anything from the "ics-leak-builds" folder ). CM9, AOKP, and AOKP AXIOM should all contain 905-based ICS builds. Try flashing something from there.
If you have a specific ROM in mind, read the forum post about it, making sure it doesn't say that you need to be on an ICS leak build. Make sure it's 905 based.
FXZ to 905:
I found two links to the new 905 FXZ. While I can't guarentee that either will flash ( I don't want to flash right now, I like where I am... lol ), I have tested and found that RSD Lite is willing to extract them, so they should flash. If one doesn't work, you can always try the other:
https://docs.google.com/open?id=0B26Hj6_2TMNTZ256eV9QbWpBSTQ from: http://forum.xda-developers.com/showthread.php?t=1771993
http://www.mediafire.com/download.php?71oyq7h8eskax6d from: http://androidforums.com/motorola-d...u-ics-back-updated-7-21-12-a.html#post4664922
Keep in mind that flashing these will essentially perform a factory reset on your phone, remove root, remove CWM and Safestrap, and possibly wipe all internal storage ( i.e. /sdcard and /mnt/sdcard ).
Conclusion:
Hopefully you found what you're looking for here. I would suggest trying out an ICS leak, they're all much more stable than the 905-based ICS builds. Also, there's a good amount of development going on that's based on them. ( For ICS builds based on the ICS leaks, See here: http://rombot.droidhive.com/ROMs/targa/ics-leak-builds/ ).
So if you want to try out an ICS leak, here's a link to a how-to ( but first a disclaimer ):
WARNING: DO NOT FLASH THE 235 ICS LEAK. YOU WILL NOT BE ABLE TO FXZ BACK TO 905. YOUR BEST BET IS 232
http://forum.xda-developers.com/showthread.php?t=1771993
If you use the 905 FXZ linked to above, make sure to give crobs808 ( The OP of that above thread ), a good thumbs up, he's the one that posted the FXZ.
Sorry this got so long. I hope this helps you get things working again. Good luck,
jedi453
projektorboy said:
Are you installing one of the ICS releases like AOKP or CM9 or are you trying to install an ICS Leak?
If you're trying to install one of the official ICS Leaks, they will only flash in Stock Recovery.
Click to expand...
Click to collapse
To further explain, I am not flash any of the ICS leaks, I am flash aokp, other etc etc. Also other posts stat to flash directly via FXZ file(the 905 firmware). I have attempted to flash the .905 on two bionics on both coming from 905 already, and will most defiantly wipe your web-top files, and corrupt your phones firmware(not brick it but Fasboot will end up failing to boot "A.6 error"), this is well documented not to flash directly to the fxz(.905) if you already have it installed it will corrupt your web-top files soft bricking your phone. The process requires you restore back to .902 and then apply .905 update(not fxz). Anyways thanks for the help, I have not flashed any of the leaks, only attempt were AOSP based roms. Maybe it is time to test out safestrap?
jedi453 said:
Hey,
This is a pretty long post, so if all you're interested in is the 905 FXZ file, scroll down to the "FXZ to 905" section, it's bolded.
Problems with flashing ICS ROMs ( in regards to OP, by Atheistnofaith ) :
You may already know this, but each custom ROM is "built off" of one of the stock roms, flashing from a different starting point will often cause your phone to not boot correctly ( boot loop, or freeze at the Motorola logo ), or will boot, but not work correctly ( i.e. something like data will not work ). This, combined with the fact that many new ICS ROMs are built on the ICS leaks, could account for the problem ( Are you sure you're not trying to flash a ROM built on an ICS leak? That would definitely not work! ).
Another possible issue is that you are using the Bionic Bootstrap program to flash CWM. The version of CWM flashed by that program is rather old ( 4.x.x.x vs current: 5.x.x.x ). You may not like this, but Safestrap is the way to go. Before you defer me to the OP, "I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs." I want to point out that Safestrap is not for the purpose of Dual-booting ROMs, or at least, that's not how many people use it. Safestrap has many features that will: prevent being stuck at bootloops ( and needing to re-Flash 902/905 every single time ), allow you to always have a backup system ( i.e. I've soft-bricked the side that I flashed ROMs on, and since I needed to use my phone, I just opened safestrap ( battery pull, start booting phone, and hit the menu button at the Safestrap prompt ), and toggled safe system in the safeboot menu. This brings up another advantage of Safestrap: you don't need to be able to boot the phone to access CWM, installing safestrap adds a new bootup prompt that either lets you open safestrap or boot normally. Again safestrap is based on a much newer version of CWM, so if you don't want to install it for any other reason, install it for that one...
Setting up for, and using Safestrap:
So if I've convinced you that you want to use Safestrap ( I really recommend you do ), follow the instructions given here: http://forum.xda-developers.com/showthread.php?t=1771993 until step 10. Then root with motofail, and install Safestrap 2.0 ( download it here:
Code:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1328100&v=1&libid=1343056993296&out=http%3A%2F%2Frombot.droidhive.com%2FROMs%2Ftarga%2FBionicSafestrap-ICS-2.00.apk&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D1006&title=%5BLIST%202012-07-18%5DOne%20Stop%20Shop%2C%20ROMS%2C%20MODS%2C%20SCRIPTS%2C%20TOOLS%2C%20ROOT%2C%20BOOTSTRAP%20-%20xda-developers&txt=2012-06-22%20Safestrap%20v2.0&jsonp=vglnk_jsonp_13430595105542
). The file should be an apk, just install it on your phone, open it, and select the option to flash it.
If I haven't convinced you to use Safestrap, go to the section titled, "Picking a compatible ICS ROM". ( Then reconsider, and come back, lol ).
When you're ready to flash a ROM, power off the phone, turn it back on, while booting, a new screen will pop up, saying something like "Safe system: Disabled", while that screen is shown, hit the menu button. The screen will temporarily go blank ( Don't panic ), then it should enter a CWM-like setup ( it looks very similar and functions the same ). Now's a good time to do a full backup ( Same as CWM ). From there, go to safeboot menu, then go to toggle safe system ( Don't do quick toggle ). This will take a few minutes. Next flash the zip like you normally would with CWM. If All goes well, you can exit that ( same as CWM ) and the ROM should boot. If it doesn't ( give it at least 5 minutes though ), do a battery pull, and power on the phone again, going into the Safestrap menu like before ( hit the menu key at the screen ), and then go to the safeboot menu and toggle safe mode ( DO NOT QUICK TOGGLE NOW!!! Doing this will require you to re-FXZ ). After that finishes, reboot and your phone should be back to stock, ready to load a working ROM on it.
Picking a compatible ICS ROM:
As mentioned before, each ROM is built on a certain OTA release, like 905 or 902, or even the leaked ICS OTAs. Any ROM that say "ICS" and "LEAK" in its name is not for 905, or anything prior. For a list of 905 based ICS ROMs, check this out: http://rombot.droidhive.com/ROMs/targa/ ( Make sure you don't install anything from the "ics-leak-builds" folder ). CM9, AOKP, and AOKP AXIOM should all contain 905-based ICS builds. Try flashing something from there.
If you have a specific ROM in mind, read the forum post about it, making sure it doesn't say that you need to be on an ICS leak build. Make sure it's 905 based.
FXZ to 905:
I found two links to the new 905 FXZ. While I can't guarentee that either will flash ( I don't want to flash right now, I like where I am... lol ), I have tested and found that RSD Lite is willing to extract them, so they should flash. If one doesn't work, you can always try the other:
https://docs.google.com/open?id=0B26Hj6_2TMNTZ256eV9QbWpBSTQ from: http://forum.xda-developers.com/showthread.php?t=1771993
http://www.mediafire.com/download.php?71oyq7h8eskax6d from: http://androidforums.com/motorola-d...u-ics-back-updated-7-21-12-a.html#post4664922
Keep in mind that flashing these will essentially perform a factory reset on your phone, remove root, remove CWM and Safestrap, and possibly wipe all internal storage ( i.e. /sdcard and /mnt/sdcard ).
Conclusion:
Hopefully you found what you're looking for here. I would suggest trying out an ICS leak, they're all much more stable than the 905-based ICS builds. Also, there's a good amount of development going on that's based on them. ( For ICS builds based on the ICS leaks, See here: http://rombot.droidhive.com/ROMs/targa/ics-leak-builds/ ).
So if you want to try out an ICS leak, here's a link to a how-to ( but first a disclaimer ):
WARNING: DO NOT FLASH THE 235 ICS LEAK. YOU WILL NOT BE ABLE TO FXZ BACK TO 905. YOUR BEST BET IS 232
http://forum.xda-developers.com/showthread.php?t=1771993
If you use the 905 FXZ linked to above, make sure to give crobs808 ( The OP of that above thread ), a good thumbs up, he's the one that posted the FXZ.
Sorry this got so long. I hope this helps you get things working again. Good luck,
jedi453
Click to expand...
Click to collapse
Thank you for the advice, but I have tested the method of flashing .905 directly via fxz on two bionic's, and can/will soft brick your phone. This has been documented not to because the webtop files are not included in the .905 fxz files, and if you flash an existing systems running 905 you will corrupt your firmware(the good old AP Fasboot failing to boot with an A.6 error I have tested this on two bionics with the same results both running .905. The solution is to flash back to .902, and then apply the OTA update(or dump the update to the cache directory) to .905. That is just a warning.
jedi453 said:
Hey,
This is a pretty long post, so if all you're interested in is the 905 FXZ file, scroll down to the "FXZ to 905" section, it's bolded.
Problems with flashing ICS ROMs ( in regards to OP, by Atheistnofaith ) :
You may already know this, but each custom ROM is "built off" of one of the stock roms, flashing from a different starting point will often cause your phone to not boot correctly ( boot loop, or freeze at the Motorola logo ), or will boot, but not work correctly ( i.e. something like data will not work ). This, combined with the fact that many new ICS ROMs are built on the ICS leaks, could account for the problem ( Are you sure you're not trying to flash a ROM built on an ICS leak? That would definitely not work! ).
Another possible issue is that you are using the Bionic Bootstrap program to flash CWM. The version of CWM flashed by that program is rather old ( 4.x.x.x vs current: 5.x.x.x ). You may not like this, but Safestrap is the way to go. Before you defer me to the OP, "I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs." I want to point out that Safestrap is not for the purpose of Dual-booting ROMs, or at least, that's not how many people use it. Safestrap has many features that will: prevent being stuck at bootloops ( and needing to re-Flash 902/905 every single time ), allow you to always have a backup system ( i.e. I've soft-bricked the side that I flashed ROMs on, and since I needed to use my phone, I just opened safestrap ( battery pull, start booting phone, and hit the menu button at the Safestrap prompt ), and toggled safe system in the safeboot menu. This brings up another advantage of Safestrap: you don't need to be able to boot the phone to access CWM, installing safestrap adds a new bootup prompt that either lets you open safestrap or boot normally. Again safestrap is based on a much newer version of CWM, so if you don't want to install it for any other reason, install it for that one...
Setting up for, and using Safestrap:
So if I've convinced you that you want to use Safestrap ( I really recommend you do ), follow the instructions given here: http://forum.xda-developers.com/showthread.php?t=1771993 until step 10. Then root with motofail, and install Safestrap 2.0 ( download it here:
Code:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1328100&v=1&libid=1343056993296&out=http%3A%2F%2Frombot.droidhive.com%2FROMs%2Ftarga%2FBionicSafestrap-ICS-2.00.apk&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D1006&title=%5BLIST%202012-07-18%5DOne%20Stop%20Shop%2C%20ROMS%2C%20MODS%2C%20SCRIPTS%2C%20TOOLS%2C%20ROOT%2C%20BOOTSTRAP%20-%20xda-developers&txt=2012-06-22%20Safestrap%20v2.0&jsonp=vglnk_jsonp_13430595105542
). The file should be an apk, just install it on your phone, open it, and select the option to flash it.
If I haven't convinced you to use Safestrap, go to the section titled, "Picking a compatible ICS ROM". ( Then reconsider, and come back, lol ).
When you're ready to flash a ROM, power off the phone, turn it back on, while booting, a new screen will pop up, saying something like "Safe system: Disabled", while that screen is shown, hit the menu button. The screen will temporarily go blank ( Don't panic ), then it should enter a CWM-like setup ( it looks very similar and functions the same ). Now's a good time to do a full backup ( Same as CWM ). From there, go to safeboot menu, then go to toggle safe system ( Don't do quick toggle ). This will take a few minutes. Next flash the zip like you normally would with CWM. If All goes well, you can exit that ( same as CWM ) and the ROM should boot. If it doesn't ( give it at least 5 minutes though ), do a battery pull, and power on the phone again, going into the Safestrap menu like before ( hit the menu key at the screen ), and then go to the safeboot menu and toggle safe mode ( DO NOT QUICK TOGGLE NOW!!! Doing this will require you to re-FXZ ). After that finishes, reboot and your phone should be back to stock, ready to load a working ROM on it.
Picking a compatible ICS ROM:
As mentioned before, each ROM is built on a certain OTA release, like 905 or 902, or even the leaked ICS OTAs. Any ROM that say "ICS" and "LEAK" in its name is not for 905, or anything prior. For a list of 905 based ICS ROMs, check this out: http://rombot.droidhive.com/ROMs/targa/ ( Make sure you don't install anything from the "ics-leak-builds" folder ). CM9, AOKP, and AOKP AXIOM should all contain 905-based ICS builds. Try flashing something from there.
If you have a specific ROM in mind, read the forum post about it, making sure it doesn't say that you need to be on an ICS leak build. Make sure it's 905 based.
FXZ to 905:
I found two links to the new 905 FXZ. While I can't guarentee that either will flash ( I don't want to flash right now, I like where I am... lol ), I have tested and found that RSD Lite is willing to extract them, so they should flash. If one doesn't work, you can always try the other:
https://docs.google.com/open?id=0B26Hj6_2TMNTZ256eV9QbWpBSTQ from: http://forum.xda-developers.com/showthread.php?t=1771993
http://www.mediafire.com/download.php?71oyq7h8eskax6d from: http://androidforums.com/motorola-d...u-ics-back-updated-7-21-12-a.html#post4664922
Keep in mind that flashing these will essentially perform a factory reset on your phone, remove root, remove CWM and Safestrap, and possibly wipe all internal storage ( i.e. /sdcard and /mnt/sdcard ).
Conclusion:
Hopefully you found what you're looking for here. I would suggest trying out an ICS leak, they're all much more stable than the 905-based ICS builds. Also, there's a good amount of development going on that's based on them. ( For ICS builds based on the ICS leaks, See here: http://rombot.droidhive.com/ROMs/targa/ics-leak-builds/ ).
So if you want to try out an ICS leak, here's a link to a how-to ( but first a disclaimer ):
WARNING: DO NOT FLASH THE 235 ICS LEAK. YOU WILL NOT BE ABLE TO FXZ BACK TO 905. YOUR BEST BET IS 232
http://forum.xda-developers.com/showthread.php?t=1771993
If you use the 905 FXZ linked to above, make sure to give crobs808 ( The OP of that above thread ), a good thumbs up, he's the one that posted the FXZ.
Sorry this got so long. I hope this helps you get things working again. Good luck,
jedi453
Click to expand...
Click to collapse
Thank you for the advice, I have already tried safestrap, but I do not want to dual boot,(safe strap will not allow you to flash over any currently installed ROMS, it appears to "sandbox" and new installs). To answer your question, I am not using the ICS leaks straigh AOKP, AOSP, and CM9(none flash without bootloops in CWM), and I understand the only way to install them is via stock recovery. lol I do not want a "sandboxed rom", because it simply is wasteful in regards to diskspace. Although, I do have a question are the ICS leaks still using motoblur as a the default launcher? Thank you again!!!
Over the next week or so I plan on making stock, deodexed roms from our fastboot system.img's. Other than Root, Busybox, init.d support, insecure adb, and being deodexed, they'll be completely stock -- nothing removed, nothing else added -- and are to be used as roms, the base rom for ports, whatever.
If you don't need insecured adb, delete /system/etc/init.d/AdbdInsecured
I include it because its a necessary feature for me.
All the roms* will be uploaded to my Goo.im page for Atrix HD
All the roms are for the locked AT&T Atrix HD running Jellybean 4.1.1.
Do not flash Gapps with the Stock Roms
Currently Done
Mexico Retail 4.1.2
AT&T 4.1.1* (not mine, see below)
To Do
Bell 4.1.2 (Jellybean)
ATT 7.7.1Q-115 (ICS)
Bell 7.7.1Q-115 (ICS)
ATT 7.7.1Q-144 (ICS)
Mods
Currently the only Mod available is the Extended Reboot Menu for stock AT&T DeOdexed, I'll make the same mod for other stock roms as I have the time.
Mexico Retail Info
Jellybean 4.1.2
Moto Blur 98.2.2 (oddly, AT&T JB 4.1.1 is Blur 98.4.20 -- this rom is higher Android Version, Lower Blur Version -- weird)
Very little bloat
WIFI didn't work until I added in the kernel modules from Stock AT&T. If you have errors, see first if it could be module related and replace the offending one.
* STOCK AT&T INFO
The stock AT&T rom is located on the Batakang FTP server and was not done by me. I assume Mattlgroff or SirHoover did that one. Someone let me know so I can give proper credits & thanks. It does not contain InsecuredAdb or init.d support. When I finish up the other stock roms on the list I'll make a Stock AT&T of my own, unless the current one's maker doesn't mind me adding init.d support and InsecuredAdb like the rest of mine on goo.im will have.
To Rom Cooks
For init.d support, I hid the init.d initialize command in /system/etc/init.qcom.bt.sh. Let me know if there's a better place to put that command or a script activated earlier in the init process we can edit.
Feel free to use my stock roms for whatever project you want. Thanks and credits are appreciated but not required.
I'm unsure if the ICS roms will even work with the Jellybean kernel & boot. I'll be finding out later on today.
Credit and Thanks
Gotta give Mattlgroff credit for the InsecuredAdb and reverse engineering Chainfire's
Thank You to whoever uploaded the Stock ATT Deodex on Batakang, I'm using its updater-script, su binary, & superuser.apk. I was lazy on the su part
I'm working on getting ICS to boot with the AT&T Jellybean kernel.
So far I'm able to get it to boot, do a complete gapps setup, but after that, it bootloops within a minute of accessing the homescreen.
Boots after that loop on the animation or will give ~30 seconds of usable display before looping.
Factory resetting allows for completing the initial setup.
If I sit on the Gapps setup page, it'll eventually start looping, but much longer than if I finished and accessed the homescreen.
I'm unable to pull any kind of logcat, ddms, etc since I can't get the PC to recognize it over usb (driver error???)
Any ideas?
I've tried replacing kernel modules with JB versions -- didn't work. By then it was after midnight so I went to sleep. That's where I'm at now. Gonna start testing out JB binaries and libs today.
Since we're able to get a working display, that makes me think that a stock ICS rom for JB users is possible. We just gotta figure out what needs to be backported from Jellybean. Maybe a new init script or an init.d script that'll fix what JB sets that ICS doesn't like.
Can someone running ICS please upload their init scripts? I'd like to compare them with JB's.
RAZRHD 4.1.2 firmware if you're still interested: http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
As for getting ICS to boot, I think you're spot-on about the init files. Safestrap doesn't mess with / files, but it does create symlinks for /system, etc & execute init files that are placed in /system/etc/rootfs. This might be key to your efforts.
Epinter has a CM10 rom that uses a modified ICS kernel, but it has no problem running on my JB phone with SS (minus the camera). Although I had to repair his inits to fix a boot error & insert two /bin files. Perhaps you could use his rootfs/inits as a guide on getting ICS to work with SS on JB.
My safestrap fix for Epinter: http://forum.xda-developers.com/showthread.php?t=2178123
Epinter's ICS-based CM10: http://d-h.st/ML8
Update: Just found this: http://rootzwiki.com/topic/8794-bionic-safestrap-bootstrap-recovery-12142011/page__st__20
It says that SS moves anything in /system/etc/rootfs to /, so if you can get a hold of the ICS init files, that should be all you need to fix the boot.
SS, while convenient, is a serious pain in the ass as far as the init process goes....I miss Defy's 2nd-Init in that regard. Everything was in /system/bootmenu/*. The downfall with 2nd-Init is you lose and reinstall the bootmenu with every rom install -- Accidentally wipe /system and not install a rom? -- sbf time .
I'll take a look at the RAZR HD 4.1.2 fastboot today or tomorrow. Rainy day, so maybe today. I'm just hoping that the lapdock fix isn't kernel deep.
Thanks for the links, I'm sure they'll be invaluable.
I'm guessing here, but I think ICS's biggest issue is\will be USB -- I'm unable to get anything USB to work -- phone detecting USB or the PC detecting the Phone. Working blind with no logs, no usb, and a looping boot animation really sucks. With any luck, Moto didn't fully remove USB mounting via the kernel, only SW blocks in JB. While only briefly, I know that at least the display works, bluetooth turns on and off, I think audio works (can't remember if it beeped or not with the rocker presses),
Time to search for ICS init scripts then.
Later on tonight I'm going to upload the ICS dumps. They still don't work but I figured the libraries and binaries could be useful with CM10 porting. The Bell will be flashable since it has a working display -- if only until non stop looping .
For some interesting info...there are 2 different sets of ICS camera drivers. The first is 1st AT&T\Bell and the second is the other AT&T. Means ya got two different sets of drivers to test when porting .
/I really need to update my banner below :silly:
UPDATE
They're all uploading now. Should be done in 5-7 hours. My upload speed sucks.
All are flashable, but the ICS ones don't work. Only Tested 144-att and 115-bell.
I'm also uploading 4.1.2 Bell. It's untested but should work.
Obviously, only flash these on a rom slot. I've only used and tested on slot 1.
Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .
thanks for this rom
AnkurBedi said:
Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .
Click to expand...
Click to collapse
I'll be straight up with you, I could make PA for us but it wouldn't be the latest version. It would be 2.5.3 just like the Defy -- AOSPA (PA 3.0+) won't be possible until we're able to get AOSP to compile from source (the SourceForge crap). It would be based on Epinter's CM10, have the same bugs as CM10...basically I'd be making PA for another device then porting that over for us . It would probably take me 6-12 hours to do all the source merging, another 2 to compile, and a day to test then upload. There is no ETA cause I haven't started on anything nor is it on my to do list yet. Times are based on how long it took me to do the Defy merging, compiling, testing.
I'm unsure on the 4.1.2 Bell rom, but the 4.1.2 Mex Retail is worth using instead of stock -- less bloat, no entitlement checks.
I partially agree on the other 4.1 custom roms -- yes, you can do it all yourself, but not everyone can. Also, not everything is compatible, so if you don't know what you're doing and flash a bad, lets say audio tweak, and it doesn't work or loops you, you could be screwed simply by lack of knowledge. That's also why I released the one custom thing I've done as a standalone mod.
Rom cooks do a lot behind the scenes -- I've been working on a rom on and off since I've had my AHD. Only mentioned in here, in a PM, and maybe publicly once or twice. I've been testing various audio tweaks, launchers, scripts, mods....I don't want to give 2-3 week eta posts cause life happens, it might not work when I get to the moment of truth, and something always happens to make any specific eta I give wrong . I've been doing tons of testing, looking for something different than the AT&T stock base or RAZR port base(see this thread :silly, tons of apk decompiling (every 4.1.2 Atrix HD apk so far), and have been adding French\Canadian English to the MR base (25 apps in). Other than that, all I know is its gonna be PlayStation Certified (already have PS Store fully working). Can't say more cause I don't know any more than that :cyclops: Point is, other cooks do tons of crap behind the scenes to ensure a good, working environment that you can't get without doing\knowing some ****. If I wasn't trying to do so much I might have had something usable by now -- I've messed with ICS, CM10 porting, SF sources, stock smali mods, my own rom, alternate stock roms.
Luckily, I still have my Defy and Bravo. Quarx is still going strong and pushing out new CM's, kernels, and everything good. One can only hope that we'll have even a quarter of the roms the Defy has. I'm so glad my first Android phone was a Defy clone. I've learned a lot because of it.
Looking forward for your custom rom skeevy :thumbup:
Sent from my MB886 using xda app-developers app
Going to test out the Bell ROM and will report results later tonight or tomorrow. Thanks so much for the upload and the work youve done so far!
I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Edit: Tried again with 1GB size also just to see if there was any difference, the error im getting has to do with the md5 of the ROM, when i enable both checks it automatically fails, however if i bypass them and continue to flash the ROM it gets stuck in a bootloop as mentioned before
Thanks a lot for your hard work,skeevy. I had a Defy green lense two years ago and sold it a year ago. Luckily,I still can enjoy modding it coz my friend still got it. It's a beast phone with all those mods by you,quarx,epsilon and maniac103. With the lack of official updates and locked bootloader,Defy can do all the impossible things. I've even seen the newest 3.x kernel with CM10.1. You guys have done a great job. Let's hope Atrix HD got the same treatment.
Sent from my MB886 using Tapatalk 2
freshlycutlawn said:
I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Click to expand...
Click to collapse
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
skeevy420 said:
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom
freshlycutlawn said:
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom
Click to expand...
Click to collapse
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.
skeevy420 said:
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.
skeevy420 said:
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.
Click to expand...
Click to collapse
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.
huatz84 said:
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.
Click to expand...
Click to collapse
Me too. Sucks we have an unlockable bootloader that we can't unlock due to Moto not supporting it. Some HD's are unlockable which is the real teaser to the rest of us.
freshlycutlawn said:
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.
Click to expand...
Click to collapse
Good to know that. Sucks JB doesn't work for you, but at least we're both able to get to the boot animation and loop it -- we could be stuck at the boot logo. With any luck I'm hoping that we can find the right combination of files to replace to get the roms to boot with the wrong kernels. We at least know its possible since JB kernel can have a working ICS rom for about 3 minutes .
Since you have an unlockable bootloader why don't you just flash a jellybean boot.img? Unpack and repack it so its not signed and you shouldn't have any issues. You could probably start using the RAZR HD unlocked bootloader roms and recoveries and never see us again.
Holy crap... I am running ICS on my JB AHD!!! It's been 10 minutes and no boot loops so far
I restored a Safestrap ICS backup, then put some ICS init files in etc/rootfs (I attached my flashable ZIP fix).
Camera doesn't work - same for WIFI but I'm sure it's a simple driver fix.
Also attached are the full ICS init files, in case you want to compare and contrast with JB inits. I omitted qcom inits in my fix.
Well that's awesome. 10 minutes beats what I've been able to do :highfive:
Wifi didn't work with MR either -- I needed AT&T wifi modules (or probably the wifi modules of the stock kernel currently running). -- /system/lib/modules/prima/* & system/lib/modules/config.ko
From what I can tell we have 3 sets of Camera Drivers (2 are ICS drivers, 1 more for JB) -- 115-att & 115-bell are the same\1st one, 144-att is 2nd, & all JB roms are the same\3rd. I'm unsure as to what all libs are necessary for the camera with us other than the obvious /lib/camera*, lib/hw/camera*, and bin/mm-qcamera-daemon. We might need to use the JB camera app as well. Also, the 144-att camera libs have more files than the 115's -- they're similar to the JB ones (1st driver doesn't have /lib/libchromatix_ov8820_hfr_60fps.so, everyone else does).
The biggest difference of the 3 JB roms, from what I can tell, are the kernel modules; libraries and drivers are the same.
I'm being a little optimistic, but hopefully whatever works for ICS on JB kernel will work for CM10 as well; and that we can invert what we're doing to get JB working with the ICS kernel.
I know what I'm doing today.
Hello guys,
I'm hoping to get some help here, since I've lost 2 days trying to flash my phone with a custom ROM.
The phone was running Official Android 4.0.4 Ice Cream Sandwich V30A, and I did the following in order to flash it:
After unsuccessful rooting attempts with SuperOneClick (stuck at step 7) I found another way, using nvflash, following these instructions. Somehow I thought I need to unlock the bootloader first, in order to root the phone, so I did that first. After that, I rooted my phone with SuperSU Root as described in this tutorial, and also installed CWM.
I thought that I was ready for the flashing part, and downloaded a custom ROM along with the right GAPPS, and followed the instructions carefully.
First few attempts I got stuck at the beginning of rom flashing process, than I found a solution, where I needed to delete the first line in the META-INF\com\google\updater-script file, then the flashing came trough, but somehow to quick I thought.
After everything was wiped/cleaned/flashed I click on “reboot system now” after which the phone should reboot into the new rom, but nothing happens, the phone acts "dead", it won't turn on, or boot into recovery mod. I was sure that I've bricked my phone, but luckily I was able to get it back on using the APX method with nvflash and boot flash.
But then the phone starts with the official ICS 4.0.4, as if nothing was flashed.
After another day of searching for a solution, I've found out that there are different partitions for different rom's, than I realized that I was trying to flash
Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM
LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly
Jelly Bean on a ICS device wich logicaly should run on a different partition, so I downloaded a ICS based ROM EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1 and got the same issue when flashing, where I had to delete the first line in META-INF\com\google\updater-script, but than the flashing process went trough and seemed more genuine than before as it took longer to finish, so I was happy for a moment, and rebooted the device, and voila nothing...he's deaaaad again.
Can someone please help me to find out where the problem lies.
Thanks for any help, I hope someone takes the time to read this.
No one here to help...
Finally I've managed to install TWRP over CWM with AIO Tollkit, to see if the problem was with CWM.
The flashing process/time seemed similar, but the phone actually booted this time, but not into the new "flashed" custom ROM, but into the old stock one which should be wiped/deleted...
Dont worry too much....
Just use the All In One Tool Kit by spyrosk.....just wipe everything....as I suspect that all your partitions have been disturbed.....for the link for this tool, check my signature
Flash the one from JellyCream.... (it is new bootloader ROM on the dev section) or if you want the 4.3 based CM ROM, then find the one from tonyp....
You will loose the data on the Internal SD card....if you have a backup on the external, then restore form it....
Edit: Eaglesblood ROM is not supported by the developers as far as I know....
Finally
Thank you for replying/helping :good:
As it seems, it was a bootloader issue (ord/new). My phone has the new one, and I thought that the ROMs I've downloaded
Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM
LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly
EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1
would run with the newBL, since they ware recently updated or made, and there was no clear info about the boot loader version.
Now after 3-4 Days of struggling, I've tried a ROM which is made and clearly stated for the newBL,ParanoidAndroid v2.6 "p990-2.6-14-newbl-tonyp.zip" and flashed it without any problems. I didn't have to wipe the whole internal storage with AIO Toolkit, I've followed the usual flashing procedure.:victory::laugh::good: the new rom looks awesome. I hope that I won't have any lock screen or random reboot issues, like before.
Now I'm gonna help a guy, who has the same problem.
I was working on getting 4.4 AOSP kitkat on my Atrix HD, and it was going great. While backing up with CWM, it failed on the data, but I figured I could just restore my files from a back up. When I went to put the rom on it, I got some no_contexts error and it said somethign about metadata. I tried to restore the backup and got a md5 fail. I used the advanced restore to let it skip the data part, but all parts gave a md5 fail. Now for somereason, I'm unable to connect through ADB, though fastboot still works, so I can't try pushing a stock rom. I tried adb sideload, but that didn't even remotely work. I also can't charge my phone, and it has a low battery. Does it charge in fastboot or recovery mode? Please help.
Phew
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
ace_case said:
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
Click to expand...
Click to collapse
I'm glad to hear you got things back into working order! With regards to flashing any custom ROM, the safest way is to use a custom recovery. Currently, as far as I can tell, the only official recovery for the Atrix HD is CWM but that's fine. You do want to be sure that you have the latest, most up to date version of CWM installed. As of right now, I believe that is 6.0.4.4 (http://clockworkmod.com/rommanager, mine already might be out of date again) and that may be where your problems came from when you were wiping and getting errors.
With regards to a close to stock 4.4 for the Atrix HD, there is an official build of CM available here: http://download.cyanogenmod.org/?device=mb886 although the latest build is from February, I can assure you that from running it on my Atrix HD it is definitely much smoother than what Motorola has offered (to date) for this device. There have been promises of official 4.4 support but I haven't seen anything come from that as of today (see here for more info: http://goo.gl/oK34W0)
CORRECTION: The official support for Atrix HD is here: http://download.cyanogenmod.org/?device=moto_msm8960
It is a merged thread for all of the devices mentioned here: http://wiki.cyanogenmod.org/w/Moto_msm8960_Info
I can't vouch for it personally but others have said that it has fixed a lot of bugs since the single device support that ended in February...