Related
[ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g
ABOUT
--------------
These Odin flashable tar.md5 packages contain the stock AT&T 2.3.6 Gingerbread release for the Samsung Infuse 4G with root added.
For those who are interested, there are also rooted options below that have busybox and are deodexed and zipaligned. An option is also provided below that includes CWM recovery and a few extras.
These rooted Odin packages do not contain bootloaders. Have rainbow distortion and want GB bootloaders to fix that? See question 1.) in the FAQ below for an explanation, warning, and link to a separate package that contains and flashes Gingerbread bootloaders.
The first two versions below use the stock UCLB3 kernel and have stock recovery. The third option below uses Entropy's Daily Driver (April 5th, 2012 test kernel with working MHL HDMI out), and includes red CWM recovery. For more information about Entropy512's kernel, go HERE.
INSTALL
--------------
1.) Download Odin from HERE and extract the program from the .zip file.
2.) Download the version you want. Use a program like 7zip to extract the Odin flashable tar.md5 from the .rar file.:
**** OPTION A ****
I997UCLB3-root.rar
Features in this version
- Stock kernel
- Stock recovery
- Rooted
******* OPTION B *******
I997UCLB3-root-deodex.rar
Features in this version
- Stock kernel
- Stock recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
************ OPTION D *************
I997UCLB3-CWM-root-deodex.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- Get extra mods HERE
Want to try some different kernels, like Zen Arcade's Infusion-Z? Odin kernel packages are HERE.
3.) Install Samsung Kies to install the latest Samsung USB drivers. This can be found HERE.
Reboot PC. Then, attach phone via USB, and allow drivers to install.
4.) In recovery, wipe all user data and wipe all cache data, BEFORE flashing. If you don't do this, I can't guarantee that your phone won't loop at the AT&T boot animation, or that you won't have other issues.
Put phone in Recovery Mode (Turn phone off, disconnect USB cable, hold power button and both volume buttons, release power button when Samsung logo appears, continue to hold volume buttons until recovery screen appears.). In recovery, choose and follow prompts for options to wipe user data and to wipe cache data.
5.) Place phone in Download Mode (Remove battery, hold down both volume buttons, replace battery, attach USB cable, and then continue to hold volume buttons until the phone enters Download Mode.).
6.) With phone in Download Mode, open the Odin exe. In Odin, if the phone is recognized, the window under ID:COM will turn yellow.
7.) In Odin, click on "PDA" and browse to the tar.md5.
8.) Select the tar.md5. Make sure it shows up in the PDA window, and then click on Start. Do not power off or disconnect the phone while Odin flashes the package and reboots the phone.
9.) You're finished. You now have stock AT&T 2.3.6 Gingerbread (UCLB3) with root.
NOTES
----------------
a.) If you skipped step 4.) and your phone boot loops at the AT&T boot animation, hold down the power button and both volume buttons until you enter recovery. In recovery, wipe all user data and wipe all cache data. Reboot and the phone will boot into rooted 2.3.6 Gingerbread.
b.) If everything has been done correctly, the Setup Wizard will appear when you first boot Gingerbread. If the phone first boots into Gingerbread, and you don't get the Setup Wizard, go to Settings / Privacy / Factory data reset and choose "Reset Phone".
FAQ
-----------------
1.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin. If something happens to cause a flash of these bootloaders to fail, then you run the risk of bricking your phone. See THIS post and THIS post for more of an explanation of why bootloaders weren't included in the rooted UCLB3 Odin packages.
2.) Isn't there a way to root stock UCLB3 Gingerbread without flashing these Odin packages?:
Yes. See THIS how-to thread that I put together for an explanation of how to root stock UCLB3.
3.) How do I get CWM recovery if I flashed a version with the stock kernel?:
If you didn't flash Option C with CWM recovery already included, you can flash a custom kernel that includes CWM recovery by using SGS Kernel Flasher on the phone. Find and install SGS Kernel Flasher in Android Market / Google Play Store. Then, place the zImage of a compatible custom kernel that includes CWM recovery on your internal sdcard, and flash using SGS Kernel Flasher. Entropy's Daily Driver, includes red CWM recovery, and can be found HERE.
4.) My phone is displaying something that looks like this: Phone-!-PC. What is this, and can I use these Odin packages from here?
That is still download mode. If you reach that screen, a flash has been interrupted or has failed, and you are in a type of backup download mode. Reset Odin, and start over with your flash. These packages will flash in this mode, just as they will in regular download mode.
THANKS
-----------------
ChainsDD for root bits
Entropy512 for his kernel
NunHugger for 8 lockscreens, extended power menu, and accurate battery mod
gtg465x for posts on how to dump factoryfs.rfs
imnuts for posts on how to create Odin images
Przekret for the Samsung UCLB3 leak
Everyone in the Infuse 4g XDA forum
Hope this helps someone out. Please use this thread for any questions or comments about using the Odin packages. It's okay to ask UCLB3 related questions here also, but remember, I didn't create the firmware. That one is on Samsung / AT&T, and these are just packages provided to make it easier to get root and /or CWM recovery with that firmware.
Good Job, bro.
Very nice. Thanks
Sent from my MB865 using xda premium
Using this for a day. And I like it very much. All functionas that I need is working perfectly for now. With root I can customize stock as I want. Thanks. As for me this is best ROM out here!
Is there any interest in a deodexed version also in this format?
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Is there any interest in a deodexed version also in this format?
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes there is. The deodexed version has a lot less lag. I ran the leak for about a month when it was released and then i flashed the deodexed version and you can tell a big difference.
Sent from my MB865 using xda premium
Yeah, when I was using UCLB3 (on CM9 now), I had it deodexed and preferred it that way.
When I get home from work, I'll make and upload a deodexed version in this format.
Sent from my SGH-I997 using Tapatalk 2
Thanks for taking the time to do that.
Sent from my MB865 using xda premium
jscott30 said:
Is there any interest in a deodexed version also in this format?
Click to expand...
Click to collapse
Cant tell about this for sure. I've used only UCLB3 stock and [UCBL3] [Dev]astation [2.3.6]. First is good and have many usefull functions and they are working fine (fast GPS, Car Holder, correct bluetoth and many other). Second one is a lot faster but not all functions are working, GPS is realy slow also stability is not so great for me. Right now current your ROM is good for me becouse it has thing that I needed being on UCLB3 - ROOT. If deodexed version will add speed and will not make this ROM less stable, than people will love it. Me for sure =)
dredik said:
If deodexed version will add speed and will not make this ROM less stable, than people will love it. Me for sure =)
Click to expand...
Click to collapse
This will just optimize system apps and framework stuff that depends on .odex files, and will make it easier to mod system and framework files. Nothing major; everything will still work like stock. I'll keep the stock version available also.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
This will just optimize system apps that depend on .odex files. Nothing major; everything will still work like stock. I'll keep the stock version available also.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
jscott,
The tar you packed was with the stock kernel, correct?
qkster said:
jscott,
The tar you packed was with the stock kernel, correct?
Click to expand...
Click to collapse
Correct. This package uses the stock kernel. That being said is there any interest also in another version w/ Entropy's Daily Driver
and CWM recovery in this format? I'll have to get Entropy's permission, but can do that also.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Correct. This package uses the stock kernel. That being said is there any interest also in another version w/ Entropy's Daily Driver
and CWM recovery in this format? I'll have to get Entropy's permission, but can do that also.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
So if everything on stock hdmi works too then?
Thanks...
Edit: Never mind i decided to flash this with other infuse and will update later the result...Thank a lot....
jscott30 said:
Correct. This package uses the stock kernel. That being said is there any interest also in another version w/ Entropy's Daily Driver
and CWM recovery in this format? I'll have to get Entropy's permission, but can do that also.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I was curious, mostly.
2 wks ago, I had put together a method to root the UCLB3 when we saw a spike in how to root this thing in the Q/A everyday. It consisted of a cwm-flashable that installed busybox and superuser, then deleted most ATT bloats. And then installed google talk video from the G-Nex.
To get to cwm, I had a Heimdall-1-click of Entropy's DD kernel. I suppose any GB insecure kernel would work too. Entropy's latest would be nice because it would also have HDMI and CWM recovery.
After the kernel flash, you can boot into recovery and flash the cwm package.
And then UCLB3 would be "rooted", busybox and SuperUser.apk. Plus some bonuses (Gtalk, Gvoice, Terminal Emulator and minus ATT bloats. It was painful but I left Facebook and a few others in place)
Once you started with the Tar for Odin, I made a Heimdall-1-click for this rooted ROM as well. What was odd was that I had corrected the vold.fstab for the external sdcard access, before copying over the factory.rfs.
After the package was put together, the vold.fstab reverted back to mm2 instead of mm1 for the stock kernel.
Odd...
I didn't know if that happened to you or not.
Anyway, imo, I don't think you need to worry about another version with Entropy'd DD, I think most users should be able to use SGS-Kernel flasher to get to cwm.
About the deodex aspect, dman already made up a deodex version...I thought it was odd that others didn't use it. It may also be redundant too, but that's just my opinion.
I think the Odex apk do not make dalvik caches. Thereby, have a fast boot time and less chance of cache corruption. I've been using the odex rooted version with the stock kernel, and have noted an initial lag, but after leaving the phone alone for 20 minutes, it is pretty responsive and snappy.
This stock rom is missing Lidroid's, Battery mod, and a few other things..but then, after you add those, lol..we are running vagabond, spartan, pharmnerd midagu's etc...
If anyone wants a heimdall 1 click...
qkster said:
I was curious, mostly.
2 wks ago, I had put together a method to root the UCLB3 when we saw a spike in how to root this thing in the Q/A everyday. It consisted of a cwm-flashable that installed busybox and superuser, then deleted most ATT bloats. And then installed google talk video from the G-Nex.
To get to cwm, I had a Heimdall-1-click of Entropy's DD kernel. I suppose any GB insecure kernel would work too. Entropy's latest would be nice because it would also have HDMI and CWM recovery.
After the kernel flash, you can boot into recovery and flash the cwm package.
And then UCLB3 would be "rooted", busybox and SuperUser.apk. Plus some bonuses (Gtalk, Gvoice, Terminal Emulator and minus ATT bloats. It was painful but I left Facebook and a few others in place)
Once you started with the Tar for Odin, I made a Heimdall-1-click for this rooted ROM as well. What was odd was that I had corrected the vold.fstab for the external sdcard access, before copying over the factory.rfs.
After the package was put together, the vold.fstab reverted back to mm2 instead of mm1 for the stock kernel.
Odd...
I didn't know if that happened to you or not.
Anyway, imo, I don't think you need to worry about another version with Entropy'd DD, I think most users should be able to use SGS-Kernel flasher to get to cwm.
About the deodex aspect, dman already made up a deodex version...I thought it was odd that others didn't use it. It may also be redundant too, but that's just my opinion.
I think the Odex apk do not make dalvik caches. Thereby, have a fast boot time and less chance of cache corruption. I've been using the odex rooted version with the stock kernel, and have noted an initial lag, but after leaving the phone alone for 20 minutes, it is pretty responsive and snappy.
This stock rom is missing Lidroid's, Battery mod, and a few other things..but then, after you add those, lol..we are running vagabond, spartan, pharmnerd midagu's etc...
If anyone wants a heimdall 1 click...
Click to expand...
Click to collapse
I run a deodexed version and think having a odin version of it is just a extra way of having a lb3 deodexed available for me to use if need be. I dont use heimdall so odin is my preference.
Sent from my MB865 using xda premium
tmease1 said:
I run a deodexed version and think having a odin version of it is just a extra way of having a lb3 deodexed available for me to use if need be. I dont use heimdall so odin is my preference.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yes. I know that some odd people prefer Odin and others prefer heimdall. Jk..
Some use both. Either way, nbd.
I was thinking that there was already a deodex uclb3.
qkster said:
Yes. I know that some odd people prefer Odin and others prefer heimdall. Jk..
Some use both. Either way, nbd.
I was thinking that there was already a deodex uclb3.
Click to expand...
Click to collapse
I use both odin and heimdall...too
qkster said:
Yes. I know that some odd people prefer Odin and others prefer heimdall. Jk..
Some use both. Either way, nbd.
I was thinking that there was already a deodex uclb3.
Click to expand...
Click to collapse
Odin ftw .
Yeah, I get that great options have already been presented to do all of this. Didn't mean to step on any toes.
Some posters were asking for an Odin option, so I made one. I personally prefer Heimdall myself, but maybe Odin is easier for some.
This is mainly just another tool to get rooted stock UCLB3. Hopefully it helps some.
When I get home, I'll still do a deodexed version, but agree that it's easy enough to use SGS Kernel Flasher to get CWM recovery.
Sent from my SGH-I997 using Tapatalk 2
qkster said:
After the package was put together, the vold.fstab reverted back to mm2 instead of mm1 for the stock kernel. Odd... I didn't know if that happened to you or not.
Click to expand...
Click to collapse
qkster, that didn't happen to me when I made this package. But, that is probably because of the process I used to get the factoryfs.rfs. I got everything exactly how I wanted on the phone, including setting up vold.fstab after switching kernels back and forth during the root process, and then I did a system dump using dd on the phone after doing a factory reset.
Well i was trying to flash SC v7 and was following the steps as directed, Installed Bootmenu Manager and downloaded the bootmenu files and gave me error about logwrapper.sh and i ignored it and selected custom recovery mode. Since then am stuck in bootanimation and it wont go beyond boot animation so is there a possible Soln?
And when i try to reflash the stock ICS i get an errorassert failed apply patch check("system/app/AABSync.apk". and so on so installation aborted
Is there a fix for Getting back to stock ICS..
THX in advance..
kc92iyngr said:
Well i was trying to flash SC v7 and was following the steps as directed, Installed Bootmenu Manager and downloaded the bootmenu files and gave me error about logwrapper.sh and i ignored it and selected custom recovery mode. Since then am stuck in bootanimation and it wont go beyond boot animation so is there a possible Soln?
And when i try to reflash the stock ICS i get an errorassert failed apply patch check("system/app/AABSync.apk". and so on so installation aborted
Is there a fix for Getting back to stock ICS..
THX in advance..
Click to expand...
Click to collapse
You have to use the patched fxz. You will have to use the proper fxz and patch it with the pieces from the Chinese forum that posted here a week or so ago... that is what I used to make the US AT&T version script that I posted. You can't use the ICS OTA as a backup.. it is a patch for 2.3.6 ONLY.
This one:
http://forum.xda-developers.com/showthread.php?t=1799702
This is just a patch that you apply over YOUR proper 2.3.5 fxz.
Well am now on 2.3.6..
THX again.
kc92iyngr said:
Well am now on 2.3.6..
THX again.
Click to expand...
Click to collapse
How can you be at 2.3.6 and flash scv7? that is ONLY for people on ICS?
Just go to the noob thread and follow the fxz instructions for 2.3.6.
NO i was on 4.0.4 and by the time i replied i had fxz back to 2.3.5 and ota to 2.3.6..
Hey guys so i got a used Atrix 2 AT&T (MB865) running 2.3.6. Every time i reboot the phone all the data seems to get wiped and the android setup screen appears. I tried to FXZ to 2.3.5 using RSDLite and the correct replacement packages and the phone goes through the process but when it says its done the phone goes into stock recovery. I try rebooting out of stock recovery and the phone boots back into 2.3.6 with the setup screen but the problem is still there. Also, when i try to OTA to ICS the update installs, but the phone goes to stock recovery after reboot. Please help
Atrix 2
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Apex_Strider said:
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Click to expand...
Click to collapse
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Popwii said:
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Click to expand...
Click to collapse
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
41rw4lk said:
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
Click to expand...
Click to collapse
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Popwii said:
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Click to expand...
Click to collapse
First, make sure your drivers and RSDlite are up to date. This isn't totally necessary, but you might as well have a clean slate to go from. So make sure your phone is unplugged from your pc, uninstall MotoDeviceManager, reboot, then install it again from here.
RSDlite 6 is here
After everything is fresh, connect your phone and give it a few minutes to detect and install your drivers. Once that's done, boot into fastboot and verify that it sees your device, if you're already in fastboot then just verify.
Code:
fastboot devices
On your phone screen it should tell you what bootloader version you have, it should say 0A.72, if not, then stop and post back what it says. Otherwise, open RSDlite, and try to flash the Official ICS FXZ you downloaded previously. By the way, the FXZ should be named InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip and the MD5sum should be 2BF9CCD528C05D26523ACC5B38AC76C6 if neither of those match, you need to make sure you have the right FXZ and make sure that the MD5sum matches what I posted.
So, if all is well and everything checks out, point RSDlite to the FXZ and start the flash, be patient. If it still fails, then you might try this. It's a way to flash the Official AT&T ICS FXZ without RSDlite, just download it, extract it, and follow the simple instructions in the readme.txt. Make sure RSDlite is closed before you run the .bat file. If you have to resort to this method, and it works for you, make sure you find Alteredlikeness around here and thank him, he put the script together.
If none of that works, then post back and we'll go from there.
Ok so i booted into fastboot and it says the bootloader is 0A.65
Popwii said:
Ok so i booted into fastboot and it says the bootloader is 0A.65
Click to expand...
Click to collapse
Alright, your bootloader is still for 2.3.6, obviously the OTA attempt never flashed the new one, or it never went properly. You might download the 2.3.6 FXZ here the MD5 sum for it is FCC0FBFDEDEAE084F90E34BF2523EB27
Flash it with RSDlite, that will hopefully get you on a clean and stable GB 2.3.6 After that, if you want to get on ICS and need some help, post back, or if getting back to 2.3.6 doesn't work, post back.
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Popwii said:
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Click to expand...
Click to collapse
How did you get into the state you're in originally? Did you try to flash something? A rom? A FXZ? You said you got a used Atrix2, was it messed up from the get go? Anyway, download this unzip it and follow the directions in the readme.txt. You'll need to unzip the Official ICS 4.0.4 FXZ that you downloaded previously as well. Basically unzip the ICS FXZ on your desktop (not the 2.3.6), then unzip the restore script and put everything in your unzipped 4.0.4 FXZ, put your phone into fastboot mode and run the restore-to-ics.bat file. Post back with results.
*Note - keep an eye on your bootloader version, if it changes from 0A.65 do NOT try and flash anything Gingerbread, you'll have to stick strictly to ICS if that changes.
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Popwii said:
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Click to expand...
Click to collapse
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
41rw4lk said:
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
Click to expand...
Click to collapse
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Popwii said:
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Click to expand...
Click to collapse
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
41rw4lk said:
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
Click to expand...
Click to collapse
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Popwii said:
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Click to expand...
Click to collapse
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
41rw4lk said:
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
Click to expand...
Click to collapse
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Popwii said:
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Click to expand...
Click to collapse
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
41rw4lk said:
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
Click to expand...
Click to collapse
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Popwii said:
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Click to expand...
Click to collapse
You should try to downgrade to 2.3.5 and start from the beginning. Since your system is borked and you can't update, hopefully downgrading will at least get you to something stable that you can work with. The noob guide will tell you how to downgrade from 2.3.6 to 2.3.5, just pay attention because you'll most likely have to replace some FXZ files since the 2.3.6 you're on is most likely from an OTA.
About 1/3rd of the way down the page you'll see "How to flash the FXZ once applying the OTA update and get back to 2.3.5", follow those instructions.
Hi i was wondering if anyone could post a stock jb rom, or factory reset their device and upload a backup of it? I have one but the wifi is damaged in it. Thanks in advance.
Comet1966 said:
Hi i was wondering if anyone could post a stock jb rom, or factory reset their device and upload a backup of it? I have one but the wifi is damaged in it. Thanks in advance.
Click to expand...
Click to collapse
What's the current state of your device? Rooted, stock or custom ROM? Do you have the Sprint version?
Grab the stock JB firmware and flash it via RSD Lite. See http://forum.xda-developers.com/showthread.php?t=2095536 for reference and links.
Stock JB firmware can be found here: http://sbf.droid-developers.org/asanti_c/list.php
Rsd lite isn't working for me, sprint version running cm10.1
What steps have you taken up to the point where RSD fails? I'm sure we can help you recover a stock firmware.
Sometimes it takes multiple tries until a full FXZ flash completes.
I download it, and I edit the xml and delete the 2 lines, then I go to flash it and it says failed 1/23, but I am having some fastboot driver issues..
What's the error output? You have two options at this point. You can use this xml file from my FXZ package: http://d-h.st/6gu
Or, you can utilize this open recovery Stock Sprint Jelly Bean nandroid from XDA user kabaldan: http://d-h.st/N0p
...good luck.
I might try the XML file and maybe that will work, if not I will do the .zip
Guys i was on Liquid smooth rom v2.5 before (used it with BMM on JB leak 1 china). I used atrix2bootstrapper to flash razr M boot image and got bootloop. I fxzd back and then reverted back to leak 1, rooted again and installed leak 3.. Now i'm on Leak 3 rooted. The question is i have not installed atrix2bootstrapper this time. Do i need to make any change to the logwrapper file? or shall i directly install BMM and start flashing rom (MIUI to be precise). Will it any way affect the logwrapper file or will it create another logwrapper.bin file after installing BMM. Hope reply will be soon :fingers-crossed:
fxz = fresh system..
Edit: oh wait.. how do u txz leak one then go to leak 3?
Sent from my Google Eyelids while sleeping..
mohammadumair said:
Guys i was on Liquid smooth rom v2.5 before (used it with BMM on JB leak 1 china). I used atrix2bootstrapper to flash razr M boot image and got bootloop. I fxzd back and then reverted back to leak 1, rooted again and installed leak 3.. Now i'm on Leak 3 rooted. The question is i have not installed atrix2bootstrapper this time. Do i need to make any change to the logwrapper file? or shall i directly install BMM and start flashing rom (MIUI to be precise). Will it any way affect the logwrapper file or will it create another logwrapper.bin file after installing BMM. Hope reply will be soon :fingers-crossed:
Click to expand...
Click to collapse
If you haven't installed atrix2bootstrapper then, no, you don't have to edit the logwrapper file. Yes, you can just install bmm and start flashing.
Brought to you by time and relative dimensions in space.
I used the fastboot file(non-AT&T) leak 1. Before this i did go into AP fastboot, then recovery and formatted the system completely. Then fxzd it. Something strange did happen. The RSD lite said "status FAIL!". Then as soon as i removed the USB cable it booted automatically. Strangely enough it did boot into Leak1 JB after a whole 5minutes!. Regret using A2bootstrapper with BMM.
I didnt get the answer to my problem. Should i change the logwrapper extension or not?... Thank You
1BadWolf said:
If you haven't installed atrix2bootstrapper then, no, you don't have to edit the logwrapper file. Yes, you can just install bmm and start flashing.
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Thanks bro. Anyway whats with the bug saying miui ui (not supporting qHD) dislocation problem. If the problem is big, i better use liquid smooth or mokee. Which is the rom maximum no. of A2 users running?
mohammadumair said:
I used the fastboot file(non-AT&T) leak 1. Before this i did go into AP fastboot, then recovery and formatted the system completely. Then fxzd it. Something strange did happen. The RSD lite said "status FAIL!". Then as soon as i removed the USB cable it booted automatically. Strangely enough it did boot into Leak1 JB after a whole 5minutes!. Regret using A2bootstrapper with BMM.
I didnt get the answer to my problem. Should i change the logwrapper extension or not?... Thank You
Click to expand...
Click to collapse
If you've flashed back to ICS via FXZ, then flash JB leak 1, then rooted and installed BMM then I don't think you'll need to do anything with the logwrapper. That procedure should only be necessary if you installed a2bootstrapper after flashing the FXZ. So, I guess the short answer is, no.
mohammadumair said:
Thanks bro. Anyway whats with the bug saying miui ui (not supporting qHD) dislocation problem. If the problem is big, i better use liquid smooth or mokee. Which is the rom maximum no. of A2 users running?
Click to expand...
Click to collapse
I don't know much about MIUI. I have installed it a few times on various devices but didn't keep it long as I prefer AOSP based ROMs. So hopefully someone that knows about MIUI will answer that for you.:thumbup:
Brought to you by time and relative dimensions in space.
Not found any problems with miui
No problems with miui except that there is no miui camera and also there is screen rotation problem.