Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
razorseal said:
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
Click to expand...
Click to collapse
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Are you unlocked??
Sent from my MB860 using XDA App
Paschalis said:
Are you unlocked??
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
As long as he's on 1.8.3. that shouldn't matter.
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Paschalis said:
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Refer to the link I sent him...
Unlocked as in rooted?
I'm running gingerblur, so yes, I'm rooted so i have access to cwm...
Can I just flash that? And yes I'm on 1.8.3
Flashing via sbf?
Sent from my MB860 using XDA App
mpalatsi said:
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Click to expand...
Click to collapse
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
razorseal said:
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA. Edit: actually, that one is modified with the unlocked bootloader.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Edit2: If it makes you feel any better, I personally used the method you described in the OP to upgrade. Wasn't that hard or "complicated".
feisty_noodle said:
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Click to expand...
Click to collapse
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
I'm in the same boat. I'm on ginger blur and 1.83 and I just want to update, unlock and root.I would like to revert back if need be.
Sent from my MB860 using XDA App
razorseal said:
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
Click to expand...
Click to collapse
This link was exactly what I used.
As far as upgrading in the future, you can use the resources found here, on XDA. People will be dissecting new updates to remove the nasty bits (bootloaders and such).
If you decide that you want to play with custom ROMs, you can do that, too.
You will NOT be able to use OTA's unless you backtrack to a fully stock ROM via official OTA's or SBF's. This can be done, but will require some careful work on your part.
For the bootloader unlocking--go read the Pudding thread here. It is very a straightforward procedure.
Edit: if your first Motorola boot screen has the word "Unlocked" in the upper left corner, then you are unlocked. If not, then ...
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Paschalis said:
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Click to expand...
Click to collapse
well then I should stay from that link that was provided here considering it's an sbf file...
Paschalis said:
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
feisty_noodle said:
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
Click to expand...
Click to collapse
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
razorseal said:
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
Click to expand...
Click to collapse
Yes, zomgunlock-lite.sbf is the contents of "pudding".
That is your bootloader that has the unlock code. Just follow Ken's instructions from the page you linked to.
Also, here is the link for an easy root method after you are done.
If you are still scared, watch the videos of the process here. I didn't have time to look too carefully, but it clearly shows what the bootloader screen should look like when you've successfully unlocked.
Good luck, I have to sleep now.
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
razorseal said:
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
Click to expand...
Click to collapse
You are not in a bricking situation! Take a deep breath.
I have not seen this, but others have ...
http://forum.xda-developers.com/showthread.php?t=1062727
Do some homework.
I am really going now.
I just reflashed.... I guess something got corrupted it works now
alright, off to unlocking, and doing the radio tweak along with battery % and att logo removal
Related
Ok, so right now I have:
System Info:
Version.4.1.83.MB860.ATT.en.US
Android Version:
2.2.2
It is rooted I have sideloading enabled. I don't know what program I used to do this with, it's been a long time. I remember there being a "beforeroot.bat" and "afterroot.bat" or something like that.
Anyway, I want to get the Alien ROM.
So, how do I do this? Do I need to update to the newest OTA? What method is the best for unlocking the bootloader? I have heard not to use PUDDING cause it uses RSD and I'm not supposed to use RSD?? Confused.
First of all DO NOT OTA. It may cause hard brick if you do not know what u are doing.
1. Unlock bootloader with pudding
2. Fastboot flash tenfars CWM
3. Backup everything with titanium backup
4. Download and install alien with CWM
Search is your friend on this one.
Sent from my MB860 using XDA Premium App
You do use pudding and RSD lite ONLY to unlock your bootloader then you uninstall it and start flashing with fasboot or tenfar's CWM. Hope that clears things up a bit.
The OTA is not a bad thing to get. I got it when it was leaked. There really is no need to flash back to older build unless you are a dev and even they dont really have the need to flash back to an older build.
The only way the OTA will brick your device is if you try to use rsd to go back to an older build.
The easiest process for getting to alien is:
1- Go here and use pudding--->http://forum.xda-developers.com/showthread.php?t=1136261
2- Go here to get Tenfars CWM installed(need this to flash ROM's)-http://forum.xda-developers.com/showthread.php?t=1138541
3- Go here to get your Alien on- http://forum.xda-developers.com/showthread.php?t=1186537
armonwilson888 said:
First of all DO NOT OTA. It may cause hard brick if you do not know what u are doing.
Click to expand...
Click to collapse
Why? The person I am about to quote says otherwise.
armonwilson888 said:
Search is your friend on this one.
Click to expand...
Click to collapse
I've been researching for a few days now, but there is SO MUCH information, most conflicting, that its extremely difficult to follow if you are not well versed in this stuff, or haven't done it before.
Dirtburgler said:
The OTA is not a bad thing to get. I got it when it was leaked. There really is no need to flash back to older build unless you are a dev and even they dont really have the need to flash back to an older build.
The only way the OTA will brick your device is if you try to use rsd to go back to an older build.
Click to expand...
Click to collapse
This what I have read. I don't think you can brick your phone UNLESS you go back to 1.83 or whatever after you unlocked the bootloader, because those are not compatible (something about a fuse or something.....yada yada)
Dirtburgler said:
The easiest process for getting to alien is:
1- Go here and use pudding--->http://forum.xda-developers.com/showthread.php?t=1136261
2- Go here to get Tenfars CWM installed(need this to flash ROM's)-http://forum.xda-developers.com/showthread.php?t=1138541
3- Go here to get your Alien on- http://forum.xda-developers.com/showthread.php?t=1186537
Click to expand...
Click to collapse
Perfect information. The only thing I don't get is this:
What is RSD? Here's what my assessment on the topic is, please correct me if (when) I'm wrong.
RSD is a tool given by motorola to flash ROMs to phones. CWM is a 3rd party tool similar to RSD made by a member named Tenfar.
Is this correct?
Also, the pudding thread in general is obscenely cluttered and has no instruction. I'm concerned with this. They mention 1.83, so should I stay with what I have? What I don't get is that if I'm flashing a ROM, what does it matter what version I have now, if it's going away? I don't get it.
Ooh, one last thing: If I install a ROM, does that mean I will not receive any more OTA update notifications? I would hope so, because if I tried to install an OTA over a ROM wouldn't that completely FUBAR everything?
RSD is motorolas tool for getting builds onto their devices and shouldnt be used at all for themost part. RSD will brick your phone if you try to go back to an older build. ie: 1.26,1.57, or 1.83. Your already on 1.83 so use RSD to flash the Pudding,(only takes a few seconds) then you have to use fastboot to actually unlock the device. This is explained in the pudding thread. CWM is how we get ROMS on our device by only flashing what is needed. CWM leaves the bootloader alone so you dont have to worry about Hard bricking your device. It is however possible to soft brick your device with CWM but a softbrick can be easily recovered. I have the leaked OTA and cant RSD back to an older build, but i have been flashing roms on a daily basis with no problems at all. Just read the directions twice and then read them again and im sure you can figure out how to unlock your device and get rolling with these hot roms.
Explaination on how to use fastboot is in the pudding thread as well as the UNlocked only CWM thread.
Here is the link to Pudding sbf.http://www.multiupload.com/FLZR9I9CNX
be sure to unzip the pudding zip first. should just be a .sbf inside
The pudding part- download the pudding sbf- put phone in rsd mode by powering in while holding the volume button up. launch rsd and load the pudding sbf and hit start. Only takes a second and the phone will reboot. Once it has rebooted, turn phone off and turn back on while holding down on the volume. fastboot should pop up first them press up on the volume and it will say entering fastboot. This is where you open a command prompt in windows(after you have put the fastboot files on the root of your c:\ drive. The fast boot files are here- http://diamantephoto.com/fastboot.rar
Put all the files that are in the fastboot zip on your c: drive and not in folders. (my computer-> C:\ drive put all the fastboot files here and not in a folder.) open command prompt and type cd\. this gets you to the root of your c: drive. should just see c:\ not cd\windows. type fastboot and you should activity then back to a c:\ prompt. once that is done you type (fastboot oem unlock) follow directions on Pudding thread from there.
Its easiest to flash pudding if your still on 1.83.
You can still do it if your on GB already
Ok, great. I'll step out of my comfort level (aka leap many thousands of yards out of my comfort zone) and try this when I get my SD card in from Amazon.
Just to clarify/simplify:
Since I have 1.83, I use RSD to flash Pudding.
Using Fastboot, I unlock the device.
Using CWM, I install Alien.
From that point on, if I want another ROM, I fire up CWM and install it there, and I shouldn't have any issues.
Is this all correct?
Also, what if I had updated my phone with the gingerbread OTA? What would the steps be then?
One more thing, do I have to have an SD card for any of these steps?
it's great for you to do it by yourself, as you're going to learn a lot more that way, if you're a little wary about using RSD and all that sort of thing, here's a cool script that'll do it for you
http://forum.xda-developers.com/showthread.php?t=1182871
Alcapone263 said:
it's great for you to do it by yourself, as you're going to learn a lot more that way, if you're a little wary about using RSD and all that sort of thing, here's a cool script that'll do it for you
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
Do I need an SD card for this?
k4zyn said:
Do I need an SD card for this?
Click to expand...
Click to collapse
no, you download that script on your computer and run it (following the instructions on the script, of course)
k4zyn said:
Do I need an SD card for this?
Click to expand...
Click to collapse
I updated the previous post a little, An sd card is the safest bet for flashing around. the sd is used for CWM flashing. put file on sd flash with cwm etc. SD not needed for pudding or unlocking bootloader
You may or may not be notified if there is an OTA update. IF you have rom installed and an update becomes available come back to forums to see if its safe to do it before you allow it, bt in most cases I dont think it will notify you if your on a Modded Rom.
If your already on GB then process is similar for unlocking. You have to unlock to use the Good CWM. The locked bootloader CWM can be troublesome.
If you want the OTA GB then unlock your bootloader then OTA up to GB. Then fastboot flash recovery Tenfars CWM, then your free ROM it up
Alcapone263 said:
no, you download that script on your computer and run it (following the instructions on the script, of course)
Click to expand...
Click to collapse
Right, I understand how the script works, I was just concerned because I'd read somewhere in this great nether that an SD card was required for one of the ROMS.......maybe I misread it though.
Dirtburgler said:
I updated the previous post a little, An sd card is the safest bet for flashing around. the sd is used for CWM flashing. put file on sd flash with cwm etc. SD not needed for pudding or unlocking bootloader
Click to expand...
Click to collapse
Makes sense! Thanks everyone.
k4zyn said:
Right, I understand how the script works, I was just concerned because I'd read somewhere in this great nether that an SD card was required for one of the ROMS.......maybe I misread it though.
Click to expand...
Click to collapse
well, that script unlocks your bootloader and installs CWM onto your phone. after that, you might need an SD card for flashing custom ROMs.
Alcapone263 said:
well, that script unlocks your bootloader and installs CWM onto your phone. after that, you might need an SD card for flashing custom ROMs.
Click to expand...
Click to collapse
Understood, thanks very much
Alcapone263 said:
well, that script unlocks your bootloader and installs CWM onto your phone. after that, you might need an SD card for flashing custom ROMs.
Click to expand...
Click to collapse
new tenfar's rom has an option of internal and external sd...so I am not sure if you have to have an external sd card...
orly?
the plot thickens.......
While I'm here, does TiBu back up everything? like, contacts, texts, email setups, etc?
k4zyn said:
orly?
the plot thickens.......
While I'm here, does TiBu back up everything? like, contacts, texts, email setups, etc?
Click to expand...
Click to collapse
TiBu backs up user apps and app data (settings). Do not backup system apps with it as you might have problems upon restoring.
For everything else you can use Mybackup Root ( Sms/MMS/Bookmarks/settings).
OK fellas. Had newest version of CM7 on the phone (phone is unlocked, rooted, etc). Keep getting random shut-offs while in stand-by. Decided to go back to official AT&T ROM.
Started flashing phone via RSD Lite. Got an error, no changes were made. Flashed again, got a different error. Stuck in boot loop. Erased cache and userdata via Fastboot, flashed AGAIN. Stuck in boot loop STILL.
Basically I can't get into the phones stock recovery, I get to the triangle screen and pressing above the search button does nothing. The phone loads up to the AT&T screen, then reboots and keeps looping at the animated "M" logo - not the M Dual Core logo. Any ideas fellas? 'cause I'm out of them. I even tried flashing a different recovery with the Atrix Fastboot Tool I found on here and got an error.
ffffffuuuuuuuuuuuuuuu
NickS_ said:
OK fellas. Had newest version of CM7 on the phone (phone is unlocked, rooted, etc). Keep getting random shut-offs while in stand-by. Decided to go back to official AT&T ROM.
Started flashing phone via RSD Lite. Got an error, no changes were made. Flashed again, got a different error. Stuck in boot loop. Erased cache and userdata via Fastboot, flashed AGAIN. Stuck in boot loop STILL.
Basically I can't get into the phones stock recovery, I get to the triangle screen and pressing above the search button does nothing. The phone loads up to the AT&T screen, then reboots and keeps looping at the animated "M" logo - not the M Dual Core logo. Any ideas fellas? 'cause I'm out of them. I even tried flashing a different recovery with the Atrix Fastboot Tool I found on here and got an error.
ffffffuuuuuuuuuuuuuuu
Click to expand...
Click to collapse
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Alcapone263 said:
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Click to expand...
Click to collapse
I just did this (completely unrelated to thread) and it gave me a totally fresh device. Perfect. Thanks!
My question: Can att still tell that at one point my Atrix was unlocked/rooted?
SielickiN said:
I just did this (completely unrelated to thread) and it gave me a totally fresh device. Perfect. Thanks!
My question: Can att still tell that at one point my Atrix was unlocked/rooted?
Click to expand...
Click to collapse
once you unlock your bootloader, it burns a fuse that motorola can check on to see if the device has been tampered with. that's why people say once unlocked, always unlocked.
it's possible to hide the 'unlocked' text at boot, but it's not possible to hide the burned fuse.
Alcapone263 said:
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Click to expand...
Click to collapse
Trying to flash CWM, it's giving me an error..
Failed to process command flash:recovery error (0x180002)
Click to expand...
Click to collapse
Ruh roh
Alcapone263 said:
once you unlock your bootloader, it burns a fuse that motorola can check on to see if the device has been tampered with. that's why people say once unlocked, always unlocked.
it's possible to hide the 'unlocked' text at boot, but it's not possible to hide the burned fuse.
Click to expand...
Click to collapse
Do they actually check that? Or is just theoretically they can...?
SielickiN said:
Do they actually check that? Or is just theoretically they can...?
Click to expand...
Click to collapse
it's a theoretically they can sort of deal.
NickS_ said:
Trying to flash CWM, it's giving me an error..
Ruh roh
Click to expand...
Click to collapse
it's because you don't have an unlocked bootloader, flash pudding through RSDlite.
Alcapone263 said:
it's a theoretically they can sort of deal.
it's because you don't have an unlocked bootloader, flash pudding through RSDlite.
Click to expand...
Click to collapse
I had one, does flashing back to the AT&T stock rom re-lock it? I thought it didn't.. regardless I'm currently flashing pudding with the version of RSDLite in his thread which is slightly different than the one I was using. (red logo vs blue)
Alcapone263 said:
it's a theoretically they can sort of deal.
Click to expand...
Click to collapse
I'm sorry to reply so much and take your time, (by the way thanks for the information, really appreciate it)
I've been having (i'm assuming) hardware issues with this phone and I only got it yesterday so I want to swap it at a local ATT store tomorrow. Can I do that without worries in my current state? Will they eventually notice and bill me? Or will I be safe?
NickS_ said:
I had one, does flashing back to the AT&T stock rom re-lock it? I thought it didn't..
Click to expand...
Click to collapse
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
SielickiN said:
I'm sorry to reply so much and take your time, (by the way thanks for the information, really appreciate it)
I've been having (i'm assuming) hardware issues with this phone and I only got it yesterday so I want to swap it at a local ATT store tomorrow. Can I do that without worries in my current state? Will they eventually notice and bill me? Or will I be safe?
Click to expand...
Click to collapse
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Alcapone263 said:
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Click to expand...
Click to collapse
Thanks SO much. Really appreciate your help.
Alcapone263 said:
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Click to expand...
Click to collapse
Thanks so much man. I have a replacement phone on the way due to the random shut offs considering people have been reporting it with the stock GB rom too, and it's believed to be a hardware malfunction, I just wanted it to appear more "stock" when they received it to avoid any question asking. Would really suck if I bricked it before hand haha.
I actually like the stock ROM on this phone anyway, probably won't be going back to CM7 once the new one comes in. It's rebooting now with the pudding SBF, we'll see if she still loops or not. If it still loops, I'll flash the modified CWM and the fruitcake ROM and report back. You guys are super helpful, thanks again!
you're welcome, both of you. glad i could help, when i was new i had a lot of help from the community here and i like to give back as much as possible. since i'm no programmer, all i can do is help answer questions for people and make sure they don't screw up their devices.
i hope you get your problems worked out, this is an amazing phone with awesome developers.
also, if you enjoy the stock ROM i would highly suggest for you to check out Aura, it's simply amazing for being a moto-based ROM.
Alcapone263 said:
you're welcome, both of you. glad i could help, when i was new i had a lot of help from the community here and i like to give back as much as possible. since i'm no programmer, all i can do is help answer questions for people and make sure they don't screw up their devices.
i hope you get your problems worked out, this is an amazing phone with awesome developers.
also, if you enjoy the stock ROM i would highly suggest for you to check out Aura, it's simply amazing for being a moto-based ROM.
Click to expand...
Click to collapse
Will do, thanks!
Oh snap! Phone just rebooted. Flashed the modified CWM via fastboot, cleared the userdata, cache & dalvik cache once more and it booted up! No need for fruitcake I guess, but I'm off to check out those Aura roms haha.
I hard bricked my first one it was also rooted and unlocked and att sent me a new on on,the warrenty for free
Sent from my MB860 using xda premium
NickS_ said:
Will do, thanks!
Oh snap! Phone just rebooted. Flashed the modified CWM via fastboot, cleared the userdata, cache & dalvik cache once more and it booted up! No need for fruitcake I guess, but I'm off to check out those Aura roms haha.
Click to expand...
Click to collapse
well i'm glad you got your problem sorted out! before you flash any ROMs though, be sure to do a complete backup of your phone as it is right now. it'll help you in case of PDS corruption later on.
What exactly is PDS corruption? And what do you recommend I do a backup with? I've actually never done a backup for any of my many android devices.
EDIT: guessing nandroid, lol google ftw
NickS_ said:
What exactly is PDS corruption? And what do you recommend I do a backup with? I've actually never done a backup for any of my many android devices.
EDIT: guessing nandroid, lol google ftw
Click to expand...
Click to collapse
i'm sure you have CWM installed by now, use Romracer's and do a full backup of your device. just keep it on your phone, with a copy of it backed up on your computer.
the PDS partition is a place on our phone that holds a lot of information about our device, if it gets corrupted you can experience a lot of touchscreen issues. just better to be safe. i flash my phone every 2-3 days and haven't experienced anything, but other people have, so like i already said; better safe than sorry
Currently on Wet Dream 1.4.3, stock kernel. Another post in here got me interested in updating my webtop to the 2.3.6 version in the Fruitcakes thread. (Question Zero: as multiupload appears to be down, does anyone know if they're being mirrored elsewhere?)
Question One: Flashing the fruitcake zip using romracer's recovery erases the webtop partition & installs the new version, correct? Is it functionally the same as using moto-fastboot to erase the webtop partition and then flash the new image file? I'm comfortable doing either, just unsure of any differences between these methods.
Question Two: Assuming this all works as advertised, will I need to redo the webtop-over-HDMI procedure?
O) Check out the OP for Wetdream, you can get it there.
1) I wondered that myself, but the results are pretty much the same either way I believe... One odd thing tho, i moto-fastbooted, with erase, and was suprised to see some settings carried over...
2) I didnt have to (on DS 4.4 lite). Tho I did have to reinstall busybox to get webtop2sd working, but you may not be using that
http://www.youtube.com/watch?v=JmvCpR45LKA
What was the point of that??
I'm running the same setup, and I had no problems just flashing the fruitcake in recovery.
Sent from my MB860 using XDA App
Thanks for the advice. I just flashed it through recovery & it went smoothly. (My husband says "I want that...", to which I respond "let me unlock your bootloader then!")
sheeparecurious said:
Thanks for the advice. I just flashed it through recovery & it went smoothly. (My husband says "I want that...", to which I respond "let me unlock your bootloader then!")
Click to expand...
Click to collapse
ugh. I love you.
I'd be like "yeah, baby. you can unlock WHATEVS you want. ".
<3
I sold my TFP and was wondering if there are any tutorials on how to flash back to stock?
get outta here ya apple land lover....lmfao you stuck in the apple Matrix. they got you plugged in. they show you a nice new shiny screen n you Jump ship..SMH. its all good man. just busting your chops.
aside from that vv
I could've sworn I saw you said you unlocked your device in other threads. if this is true, there is no way to go back to stock. stock means you have a locked bootloader again. there is no relocking. if you want to go to stock firmware, look in developement section.
If it is unlocked, it will never be stock again. Otherwise, you can just root it and dd the blob file using the method detailed in the thread in the dev section about how to flash any version software,That will revert the kernel and boot and other stuff to stock and also unroot it. Then just do a factory reset/data wipe and you are good to go
I'm not concerned with the bootloader, I just want a stock looking ROM. Is that possible?
Sent from my Transformer Prime TF201 using xda premium
scook9 said:
If it is unlocked, it will never be stock again. Otherwise, you can just root it and dd the blob file using the method detailed in the thread in the dev section about how to flash any version software,That will revert the kernel and boot and other stuff to stock and also unroot it. Then just do a factory reset/data wipe and you are good to go
Click to expand...
Click to collapse
So can I atleast unroot and flash stock kernel and rom?
Sent from my Transformer Prime TF201 using xda premium
demandarin said:
get outta here ya apple land lover....lmfao you stuck in the apple Matrix. they got you plugged in. they show you a nice new shiny screen n you Jump ship..SMH. its all good man. just busting your chops.
aside from that vv
I could've sworn I saw you said you unlocked your device in other threads. if this is true, there is no way to go back to stock. stock means you have a locked bootloader again. there is no relocking. if you want to go to stock firmware, look in developement section.
Click to expand...
Click to collapse
I've had all android my life, never tried apple, don't hate lol ill be back. In the meantime help me out! I'm sticking with my galaxy nexus no iPhone here!
Sent from my Transformer Prime TF201 using xda premium
see the thing is, there have been several people who unlocked, used custom rom, then tried to flash back an official Asus stock rom and bricked their prime.
SO LET ME WARN YOU, IF YOU UNLOCKED, DO NOT TRY TO FLASH AN OFFICIAL ASUS ROM OR YOU WILL BRICK YOUR TABLET. ask Diamondback for proof. you could try unofficial versions. there is a stock rom but has some tweaks added to it like root n some other things. you have to look in developers section on it. I forgot the guy name. I think it may be Jermaine. look for his stock rom thread. just plz make sure to research it thoroughly first. wouldn't want you to brick your prime.
on another note, if you unlocked n flashed a custom rom, didn't you nandroid backup your stock rom first before flashing? if so then you can just flash/restore that nandroid backup you have through CMW manually.
demandarin said:
see the thing is, there have been several people who unlocked, used custom rom, then tried to flash back an official Asus stock rom and bricked their prime.
SO LET ME WARN YOU, IF YOU UNLOCKED, DO NOT TRY TO FLASH AN OFFICIAL ASUS ROM OR YOU WILL BRICK YOUR TABLET. ask Diamondback for proof. you could try unofficial versions. there is a stock rom but has some tweaks added to it like root n some other things. you have to look in developers section on it. I forgot the guy name. I think it may be Jermaine. look for his stock rom thread. just plz make sure to research it thoroughly first. wouldn't want you to brick your prime.
on another note, if you unlocked n flashed a custom rom, didn't you nandroid backup your stock rom first before flashing? if so then you can just flash/restore that nandroid backup you have through CMW manually.
Click to expand...
Click to collapse
Restoring a nandroid in CWM does not grab the kernel, he still has to do the blob method I detailed. I grabbed the blob from the official asus .15 zip and it has worked fine. Done it several times myself. Do that method and you are unrooted, stock recovery. Should be like all stock except for bootloader. You will still need to do a factory reset/data wipe I believe.
Deleted.
Sent from my HTC Mecha using XDA
scook9 said:
Restoring a nandroid in CWM does not grab the kernel, he still has to do the blob method I detailed. I grabbed the blob from the official asus .15 zip and it has worked fine. Done it several times myself. Do that method and you are unrooted, stock recovery. Should be like all stock except for bootloader. You will still need to do a factory reset/data wipe I believe.
Click to expand...
Click to collapse
How did you get back to stock recovery? OP of thread says that method will brick you if you are unlocked and rooted. Or am I looking at the wrong thread?
Sent from my HTC Mecha using XDA
I used this method:
http://forum.xda-developers.com/showthread.php?t=1492887
For what it is worth....that disclaimer was not up when I first tried it. I have the stock ROM with CWM and unlocked bootloader. It has worked fine for me....flashing the blob replaces the recovery with stock. I have done this 3 times without issue.....maybe I am lucky? Seems more like a CYA disclaimer to me. I can see NO reason why it would pose any threat, this code sits above the bootloader and would be the same whether unlocked or locked. the kernel would be the only concern....but it is replaced properly along with the recovery by the blob method
scook9 said:
I used this method:
http://forum.xda-developers.com/showthread.php?t=1492887
For what it is worth....that disclaimer was not up when I first tried it. I have the stock ROM with CWM and unlocked bootloader. It has worked fine for me....flashing the blob replaces the recovery with stock. I have done this 3 times without issue.....maybe I am lucky? Seems more like a CYA disclaimer to me. I can see NO reason why it would pose any threat, this code sits above the bootloader and would be the same whether unlocked or locked. the kernel would be the only concern....but it is replaced properly along with the recovery by the blob method
Click to expand...
Click to collapse
OK.thanks. so just dd that blob file to, in my case, internal sdcard and reboot and that's it, and that puts recovery and kernel back to stock?
Sent from my HTC Mecha using XDA
No. Place it on the sdcard, insert into tablet. When doing dd command, if=input file (file source) of=output file (destination). I used a USB Thumb drive actually, doesn't matter as long as you know where the blob is for the dd command
Make sure you properly locate the file for the if parameter and that you exactly input the value for of. Messing this up will probably brick the tab so be careful
scook9 said:
No. Place it on the sdcard, insert into tablet. When doing dd command, if=input file (file source) of=output file (destination). I used a USB Thumb drive actually, doesn't matter as long as you know where the blob is for the dd command
Make sure you properly locate the file for the if parameter and that you exactly input the value for of. Messing this up will probably brick the tab so be careful
Click to expand...
Click to collapse
Yeah I don't have an SD card.
Was hoping I could just do it from the internal sdcard..oh well thank you for the info
Sent from my HTC Mecha using XDA
You can do it from the internal SD Card/memory. Just have to change the path given for if=
You will need a computer at some point though as I am not sure there is a good method to extract the blob itself within android.
scook9 said:
You can do it from the internal SD Card/memory. Just have to change the path given for if=
You will need a computer at some point though as I am not sure there is a good method to extract the blob itself within android.
Click to expand...
Click to collapse
Cool.laptop I have...so I will give it a shot. Thanks
Sent from my HTC Mecha using XDA
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Thanks for all the hard work
Sent from my SCH-I605 using xda app-developers app
Excellent words of advice from an ERD who KNOWS what's he's talking about... Please take his advice everyone... It will save you A LOT of pain...
Stickied
Thanks for your hours of work. People WILL screw this up, unfortunately.
Sent from my SCH-I605 using xda app-developers app
thejron said:
Thanks for your hours of work. People WILL screw this up, unfortunately.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Yup! I can already see the threads starting.... It is good to know that we can still use Odin though cause I was under the impression that Odin was a no-go at this point... So flashing the factory image from imnuts would be the best resort to get back to stock if we needed to return a device?
shojus said:
Yup! I can already see the threads starting.... It is good to know that we can still use Odin though cause I was under the impression that Odin was a no-go at this point... So flashing the factory image from imnuts would be the best resort to get back to stock if we needed to return a device?
Click to expand...
Click to collapse
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
droidstyle said:
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
Click to expand...
Click to collapse
Thanks buddy! I just checked it out and I am very thankful for your guides as it has helped me and MANY others! I have thanked so many people that my limit is up (for the day) but I appreciate your time that you have put forth to helping people! :good:
I know I'm off topic. I'm not an owner of the note 2 but wanted to say awesome signature to the OP. From one vet to another thank you
Sent from my LG-LS970 using xda premium
droidstyle said:
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
Click to expand...
Click to collapse
I still have plenty of "Thanks" so Thanks, and I am gonna study this weekend, hopefully by then the other issues folks have been having will at least be identified if not corrected.. then it's freedom for me!!
AdamOutler said:
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Click to expand...
Click to collapse
Adam- but we ARE ok flashing with Odin so we can retrun to complete stock correct? your not saying that doing that may completely brick are phones are you? just want to be clear. i only use ODIN to go complete stock..
thank you for your work
dvigue said:
Adam- but we ARE ok flashing with Odin so we can retrun to complete stock correct? your not saying that doing that may completely brick are phones are you? just want to be clear. i only use ODIN to go complete stock..
thank you for your work
Click to expand...
Click to collapse
"Please use Odin as a factory restore tool only"
In Androidstyle's guide thread, Adam asked him to point the unlock guide to his unlock thread, but I don't see an unlock thread from Adam, only the Revision3 thread which has no steps to unlock. I see the video Adam made, but my understanding is that the process has changed and the links to download Adam's ROM are dead on the Youtube page. Anyone have the link to Adam's unlock step by step guide?
wmaudio said:
In Androidstyle's guide thread, Adam asked him to point the unlock guide to his unlock thread, but I don't see an unlock thread from Adam, only the Revision3 thread which has no steps to unlock. I see the video Adam made, but my understanding is that the process has changed and the links to download Adam's ROM are dead on the Youtube page. Anyone have the link to Adam's unlock step by step guide?
Click to expand...
Click to collapse
It's in "Verizon Galaxy Note II Android Original Development". Go up one level and you'll see it. There are only two threads there so it shouldn't be too hard to find.
I don't mean to sound mean but if you really can't figure out how to get to his unlock thread do you really think it's a good idea to be unlocking your bootloader? Maybe you should just stick to a rooted image and read up and learn for awhile before jumping in over your head
Sent from my SCH-I605 using xda app-developers app
LordRalh3 said:
I don't mean to sound mean but if you really can't figure out how to get to his unlock thread do you really think it's a good idea to be unlocking your bootloader? Maybe you should just stick to a rooted image and read up and learn for awhile before jumping in over your head
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
To be fair, the distinction between "Android development" and "Original Android development" is new for many of us. I, too, was wondering how to get back to this thread since I tend to browse XDA through bookmarks instead of the site hierarchies. I didn't realize there was an "original Android development" section until after I double checked the name on the thread jumper. It's not that one is technologically illiterate (I got through all this in one fell swoop with no issues and have rooted and unlocked every phone I've owned since the G1), it's just that it's different. Last device I had didn't have a section for original development, so it wasn't immediately obvious to me (though I quickly understood what it was for). so cut him some slack and just kindly point him to the right direction. I know you said you weren't trying to sound mean, but if you really weren't trying to sound mean you could have just helped him out without all of the extra, unnecessary commentary. You know what they say about assumptions, after all.
Just got the Note 2 on verizon and loving it so much I'm going to hold off for a bit before unlocking & rooting. Normally on all my android phones that is done day 1... but this time w/ the dev community just now unlocking it, I think I'm going to wait a few weeks.
In context, imnuts has put out a Recovery flash-able version of CWM. If one tries his CWM but wants to go back to TWRP then currently it seems that one need to ODIN it. To Adam Outler's point it would be safer to have a Recovery flash-able version of TWRP. [?]
AdamOutler said:
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Click to expand...
Click to collapse
Does the same go for Heimdall aswell then?
trevd said:
Does the same go for Heimdall aswell then?
Click to expand...
Click to collapse
Yes because it does the same job as ODIN but on a different operating system.
Sent from VZW Note 2
Clarkkent434 said:
Yes because it does the same job as ODIN but on a different operating system.
Sent from VZW Note 2
Click to expand...
Click to collapse
That's what I figured , I thought I'd ask the dumb question to explicitly clarify it.