Related
I have an ATT Captivate which I managed to update from original Android 2.1 to 2.2 firmware, version I897UCJI6.
This was before ATT release their official 2.2 update.
I also managed to unlock the phone.
I have to admit I am totally ignorant of this stuff, and I was lucky enough not to brick my phone during those updates.
I am very unhappy with the battery life of my phone, and I read that the Gingerbread dramatically improves this aspect.
So, shall I upgrade to Gingerbread?
If yes, I am confused with the many sites which offer advice with how to do this, some contradicting with others. (One indicated to reverse back to 2.1 before upgrading to 2.3, other didn't say that, etc etc)
Should this upgrade be successfull, what happens to the lock/unlock status?
Do I need to unlock again?
Which is a trusted site?
Any advice?
Thank you for any help
UnLock stays after flashing.
As for a trusted site.... Ummm you found it. Xda...
Thank you
Will this upgrade really improve battery life?
If not I'll stay with 2.2
I got Max of 18 or so hours on froyo, I can go over 2 days now. Ymmv though.
Thanks again
I assume this would be the thread to follow, right ?
http://forum.xda-developers.com/showthread.php?t=1233620
Which indicates the use of this file : I897UCKH3_noboot.tar.md5 (dated 8/24/2011, 305191 KB)
I did find another file somewhere, presumably doing the same thing - that file name is:
I897UCKH3_HOME.tar.md5 (dated 8/19/2011 298421 KB)
I stated before I am kind of ignorant, and easily confused with all those information.
Which one is the right file?
Am I on the right track?
If you going to use KH3 without bootloaders you need to flash This bootloaders first.
Is there a thread for novices, where all those terms are explained, or where the procedures to be followed are explained for somebody who who can follow indicated steps (without really knowing the meaning of all those terms) which could lead to 100% success?
I don't mind reading a little, but I don't have time to become an expert (and I'm sure many readers here are like me, looking for plain simple advice on how to upgrade their phones, without having the skills and knowledge to do it)
Reading those posts here can be sooo confusing...
Somebody recommends you to do this, somebody recommends you to do that, and the poor you have no clue what they're talking about...
Simple if you want Gingerbread you need new bootloaders (except Cyanogenmod and MIUI). Bootloaders are like the BIOS in your computer. If you mess up the bootloaders you can hardbrick your phone.
Got it
Next logical question would be WHY the person who indicated how to upgrade to Gingerbread (http://forum.xda-developers.com/showthread.php?t=1233620) did not tell in his post that you need new bootloaders.
Or at least I do not see that in his post.
Which means that a novice like me can ruin his/her phone very easy..
No bootloader ODIN packages are made for people that already have the GB bootloaders. So you don't get a hard brick.
http://forum.xda-developers.com/showthread.php?t=1232703
I believe this is what you want to use.
mirceani said:
Got it
Next logical question would be WHY the person who indicated how to upgrade to Gingerbread (http://forum.xda-developers.com/showthread.php?t=1233620) did not tell in his post that you need new bootloaders.
Or at least I do not see that in his post.
Which means that a novice like me can ruin his/her phone very easy..
Click to expand...
Click to collapse
Flashing a GB ROM without GB bootloaders won't ruin your phone. May cause a bootloop, but not a hard brick. Cezar is super picky about things being safe. If you had hit the link he had for tips and tricks, it says something about bootloaders.
After reading all related posts, I am still confused - pls help:
I understand that if I follow Cesar's link, I need bootloaders first.
If I follow Przekret's link, I do NOT need bootloadres first (they are included)
So how do I decide which route to follow ? In the end I get the same result, GB 2.3.4 - correct?
I am currently on Froyo, UCJI6, rooted and unlocked.
Do I loose my rooting (I understand that unlocking stays)
Again, which method should I use (Cesar or Przekret) ?
Thank you
If you need bootloaders, don't use Cezars.
As these are stock roms, you will lose root. But if you flash any custom ROM, it should be rooted.
No method is incorrect. I would flash Bootloaders firs because there seems to be less chance to hard brick (I've noticed sometimes ODIN doesn't flash one bootloader after another). Thats my personal experience, but like I said neither of the methods are incorrect, I just never used the one with bootloaders included since I already had them when KH3 came out, so I can't speak for that package myself.
How do I know if I need bootloaders or not?
Unless you bought that phone modded with the GB bootloaders you need them. No real way to know except flashing a GB rom like cezars package. If it works You didn't need them, If it din't work then you soft bricked your phone and you might need a jig to get in to Download mode again.
mrhaley30705 said:
If you need bootloaders, don't use Cezars.
As these are stock roms, you will lose root. But if you flash any custom ROM, it should be rooted.
Click to expand...
Click to collapse
sorry for my ignorance, what is a "stock rom" and what is a "custom ROM" ?
prbassplayer said:
Unless you bought that phone modded with the GB bootloaders you need them. No real way to know except flashing a GB rom like cezars package. If it works You didn't need them, If it din't work then you soft bricked your phone and you might need a jig to get in to Download mode again.
Click to expand...
Click to collapse
OK
since I bought the phone from ATT a year ago, running 2.1, I would assume that I do NOT have them, so I do need them
mirceani said:
sorry for my ignorance, what is a "stock rom" and what is a "custom ROM" ?
Click to expand...
Click to collapse
A stock rom is that package that Cezare and pretzel posted. A custom rom is Fusion V, Pinnacle, Fasty II, among many many other. All those are based on the stock KH3 that cezar and prertzel posted
Hi I found a similar article on androidforums.com so I thought id make one here as a lot of people still seem to not know how to flash basebands and go from there. Ill start from the beginning.
For those who don't understand what this is about.
Old Baseband = If you have the Stock Froyo (2.2) Android system on your phone then you have the OLD BASEBAND, and you do not need this unless you updated to past 2.2.2 then continue reading if you wish to root your phone the easy way.
New Baseband = If you updated to the Stock Gingerbread (2.3) Android System on your Optimus One, then you fit this category, Lg have implemented a new baseband in this update which makes any Roms based on the old baseband not function, as well as making it more difficult to root your phone
FLASHING OLD BASEBAND
If you're already on official Gingerbread version you will need to downgrade your version to Froyo 2.2.2 using KDZ Updater. This is because the new Gingerbread contains the new baseband, and the Froyo firmware is the old baseband.
To do this please go onto this link that contains kdz and the stock Froyo 2.2.2 Rom required to flash. The reason you need 2.2.2 is its the easiest and proven version to work with Gingerbreak to root your device.
http://forum.xda-developers.com/showpost.php?p=13396506&postcount=1
Notice: If by some ACCIDENTAL reason, your phone gets stuck in EMERGENCY MODE during flashing, follow the instructions on this link how to use KDZs functions to continue flashing the firmware you downloaded in Emergency mode.
http://forum.xda-developers.com/showthread.php?t=1275523
FLASHING NEW BASEBAND
The Kdz File for new baseband is below, use the same method as above only using the v20G .kdz file instead of the 2.2.2 v10E update.
This will update your phone to the official LG 2.3 firmware, in which the new baseband originated.
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/ANEUBK/V20g_00/V20G_00.kdz
If then stuck on LG Logo OR boot animation, try pulling and putting in your battery, turning on your phone and holding down volume down and home key, this should reset your phone to factory and then you will be able to boot into the stock gingerbread.
ROOTING
The easiest way to get root privileges on Old Baseband (2.2.2) firmware device is by using Gingerbreak apk. Just download it, install it and run it.
forum.xda-developers.com/attachment.php?attachmentid=600902&d=1305802958
To get Root access on the New Baseband (2.3.3) use SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
Or direct link to the latest version
forum.xda-developers.com/attachment.php?attachmentid=778098&d=1320906597
Make sure, after you download the program, you go into your cmd, then go into the ADB folder, drag the ABD exe file into command prompt, delete the .exe part and add devices, so it look like this
OR
Download the ADB.zip attachment on this post, EXTRACT it so cmdXP and cmd7 are located inside the ADB folder in the Superoneclick directory, and run either version, depending on your windows version (This links you directly into ADB app, instead of manually dragging ADB.exe int cmd, really its just for your convinience.)
Then all you have to do is type the following lines.
adb devices
press enter
adb shell
press enter
then type in the following directly after
echo 1 > /data/local/lge_adb.conf
press enter.
Then go into Superoneclick.exe, select auto method and run root, this should then eventually root your device.
***WARNING***
Some Antivirus softwares will detect Superoneclick as a Virus.
IT IS NOT A VIRUS, just the types of exploite code it uses makes some antivirus software think of it as malicious. Just disable your AV for 5 mins before you extract Superoneclick.
RECOVERY
There's two popular custom Recovery versions for O1 - AmonRa and ClockworkMod
The easiest way to flash ClockworkMod Recovery is by downloading ROM Manager app from the Market (free or donate version doesn't matter) and choose to flash the latest recovery version and choose the option to Reboot in Recovery mode.
For Other Recoveries including Amonra there are a few links, but here is the one that has flashable zips
http://forum.xda-developers.com/showthread.php?t=1523050
Just flash the zip files in Clockworkmod recovery menu, after you install that through Rom Manager if you wish to use a different recovery.
Now that you got the right baseband + your device is rooted and loaded with a custom recovery you may install any Rom you wish that is based on the correct baseband such as
Mik_os 6.5.8 Cyanogenmod port (OLD BASEBAND).
http://forum.xda-developers.com/showthread.php?t=946354
[UNOFFICIAL][DEV/GEEKS-ONLY] Cyanogenmod 9 (Android 4.0.3)[BETA][NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1558213
OFFICIAL CYANOGENMOD Rom [NEW BASEBAND]
http://get.cm/?device=p500
Oxygen ROM 2.3.2 (Android 2.3.7)[NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1325386
Next time, search better
Also posted in wrong thread, this is developmentthread...
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
fundoozzz said:
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Guys i did a search and looked into the sticky how to, and the only thing about downgrading baseband is using LGMDP, and kdz is only "mentioned" as a tool for unbricking your phone and flashing old firmware, new users would not know to use kdz.
Also this is a universal guide to root ANY lg optimus one together with having the old baseband, without having to mess around with SDK or LGMDP.
All members have to do now is look at this thread and all their questions are answered hopefully...
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
I hear a lot about the new baseband making ROMs incompatible, but is there any advantage to the new baseband?
its not that they are making roms incompatiable, its that they are not designed for those Roms,
So far there has been no reports of any advantage having a new baseband, Lg engineers obviously decided on it for some reason, but the old baseband is more than fine, and in fact i have read several reports that with the new baseband gsm reception got worse in areas that they used to have fine reception, but thats all speculation.
Your best bet is to try for yourself, but if you want to make use of Roms such as miks cyanogen mod or others you have to use the old baseband.
There are other Roms available on the new baseband, so its upto you.
I suggest what rom you would like to install on your phone first, then pick the baseband it requires, as its only a simple flashing of your firmware.
Also note Gingerbreak.apk doesnt root any stock firmware past the 2.2.2 update.
Personally i pick the functionality and advantage of having a custom rom such as cyanogenmod over an update to the baseband
Does this guide work for Optimus T (LG P509) ? I have got one recently and currently using stock 2.2 on it. I don't know the difference between LG p500 and LG P509. I'm coming from T-Mobile G1 on which I'm using CM 7.1. Thanks for guidance.
Sent from my Dream/Sapphire using xda premium
Hi,
Doing a little search i found this thread
http://forum.xda-developers.com/showthread.php?t=960278
looking at it, i assume you can use this guide for p509, but i can not be 100% sure, try finding the t-mobile 2.2 kdz file, but yes not 100% sure the main difference.
deniso177 said:
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
Click to expand...
Click to collapse
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
As you already quoted it, i said that this method is different from Doks.
As for wiping all data completely, so its all brand new and neat, then try to fiddle around with internals and possibly have a bug result from it.
KDZ is what is used to UNBRICK your phone in the first place, so go do some research before posting unnecessary things.
Lastly how about you show some respect and keep your negative and rude comments to yourself, if you dont like this method dont do it, dont abuse people in the process.
terratrix said:
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Click to expand...
Click to collapse
And yep exactly, i personally prefer completely reinstalling something to make it work properly, then doing things dodgy.
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
ichigo200 said:
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
it means your phone is past the firmware update that gingerbreak works on,
as it says in the first post, use kdz and the file in the link to flash your phone to that firmware, and then gingerbreak will work
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
A warning to anyone tempted to do this. Like the original poster, I also have an LG Optimus T. I am technically savvy (15 years IT experience) and I followed the directions to the letter, but the end result is a bricked, unrecoverable phone. Had I known the risks involved, I would have been perfectly content with Froyo and waited for the official upgrade to arrive.
Here is how mine failed: during the kdz update process, while the phone was on the "Emergency Mode" screen, the kdz updater program threw an exception and crashed. This caused the phone to be permanently locked in emergency mode. The buttons are unresponsive and the only way to turn it off is to remove the battery. With the battery in, it immediately goes to the emergency screen. No combination of button presses (eg, hard reset) does anything. The computer will still see the devices but only if I remove the battery and start the phone up by inserting the USB cable.
I have tried every method for recovery I could find including the following. In each case, I tried it with the modem device listed in device manager both disabled and enabled, as instructed in other recovery threads I found.
Flashing the original .kdz ROM in emergency and cs_emergency modes. When I did, it failed with an exception 4008.
Flashing the original .dz ROM with all of the tools I could find. LGMDP and LGDP2 could see the phone's COM port but beyond that, they could not communicate with the phone in any way. I couldn't even retrieve the IMEI number.
Updating the phone with the LG update software. It actually detects that the phone needs an update and starts to do one but it fails at the point where it tries to communicate with the phone.
Based on other posts I found for the same problem, I believe the phone is completely unrecoverable. I spent over six hours trying to solve the problem and I'm kicking myself for even trying this. I have put in a repair claim with LG and I'm waiting for instructions on how to proceed.
I would not recommend you try this unless you are not worried about destroying your phone. I imagine most installs go without a hitch but if the buggy kdz updater software crashes like it did for me, your phone will likely be bricked permanently.
Click to expand...
Click to collapse
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
In short, don't mess with KDZ unless you really have to.
Click to expand...
Click to collapse
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
I have used KDZ more than 2 dozen times -.- Just used it again this morning. I never ended up with a bricked phone mind you. They favour LGMPD since it's more updated, while KDZ is a little old but still very good.
There is a fairly equal share of bricked phones using LGDMPD, eventhough they got it back by using other people's NV2, they need to hope they are lucky to escape the long arm of the law.
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
Mate your the one who clearly doesnt get it.
And i read your post on androidforums, you even managed to brick your phone installing custom recovery, clearly your phone software is buggy, not kdz, kdz is capable of recovering while in emergency mode as well, but of course there are freak accidents.
EVERYTHING has a WARNING.
Every single Rom, Kernel, Recovery also carry a chance of bricking your phone.
I have used Kdz dozens of times and never had a problem with it, in fact, its what solved my problems in the first place.
And exactly wat terra said, the way LGDMPD works can also cause bricked phoes or taking shortcuts to make things half work.
You have to know what your doing, and follow instructions TO THE WORD, and you should be fine, if your going to skim read then you brick your phone doing the simplest of tasks (such as repeatedly flashing zips without reloading recovery...)
I will always prefer kdz as thats what the firmware comes with originally + i prefer doing clean installs any day.
Please Help...
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
shreyas.kukde said:
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
Click to expand...
Click to collapse
Hey mate, well no gsm is normally caused by the wrong baseband, so flashing back to the old one should fix the problem, try to re-flash the stock froyo given in the link on first post and see if that works, and if still no coverage then its a hardware problem and Lg should replace it for you, just dont forget to flash back to stock again if you rooted it, then they should fix it within the warranty.
So I've always owned samsung phones...fell in love with amoled and never looked back...and i gotta tell you, my short spurt with the one xl with having to flash kernels and rom separably and unlocking bootloaders and what not man! i really miss the simplicity of being able to root with odin and never having to look back...everything just worked as it should (the biggest inconvenience we had was having to flash an older kernel on the sg2 before flashing anything above gb) but here I am, ready and willing to embrace the atrix's sexy design but limited development...but I need some clarification that simple searches and reading through threads dont seem to explain quite as thoroughly as other devices portals.
1.) I understand the concept of a bootloader and how it needs to be unlocked in order to flash ROM's and kernels and write to specific partitions of the phone, I just want to ensure that this device has an unlockable bootloader with the latest firmware that it ships with
2.) even more important than bootloader unlocking is root...i see references to SBF's and qslite or something...is this similar to odin for samsung? do i use an SBF (perhaps the equivalent of an RUU for htc or .tar for samsung??) to flash firmwares onto the device, and will a modded version provide SU?
3.) no roms! thats unacceptable. if i can obtain root and recovery, trust me when i say that even while i cant build from source, ill put SOMETHING together, even if its only rooted/themed stock. but what are the odds of rom from other devices being ported?
4.) cheesecake. wtf.
which one of these threads should i use for the latest firmware on the atrix to root?
http://forum.xda-developers.com/showthread.php?t=1785401
http://forum.xda-developers.com/showthread.php?t=1940594
which one of these threads should i use for the latest firmware on the atrix to unlock bootloader?
http://forum.xda-developers.com/showthread.php?t=1896526
http://forum.xda-developers.com/showthread.php?t=1985031
does hash's safetrap work for backups on the ahd? i read that flashing is disabled currently, but id still like to backup
gosh so many questions! hope the trolls dont come out on sundays...........................
hapticxchaos said:
So I've always owned samsung phones...fell in love with amoled and never looked back...and i gotta tell you, my short spurt with the one xl with having to flash kernels and rom separably and unlocking bootloaders and what not man! i really miss the simplicity of being able to root with odin and never having to look back...everything just worked as it should (the biggest inconvenience we had was having to flash an older kernel on the sg2 before flashing anything above gb) but here I am, ready and willing to embrace the atrix's sexy design but limited development...but I need some clarification that simple searches and reading through threads dont seem to explain quite as thoroughly as other devices portals.
1.) I understand the concept of a bootloader and how it needs to be unlocked in order to flash ROM's and kernels and write to specific partitions of the phone, I just want to ensure that this device has an unlockable bootloader with the latest firmware that it ships with
2.) even more important than bootloader unlocking is root...i see references to SBF's and qslite or something...is this similar to odin for samsung? do i use an SBF (perhaps the equivalent of an RUU for htc or .tar for samsung??) to flash firmwares onto the device, and will a modded version provide SU?
3.) no roms! thats unacceptable. if i can obtain root and recovery, trust me when i say that even while i cant build from source, ill put SOMETHING together, even if its only rooted/themed stock. but what are the odds of rom from other devices being ported?
4.) cheesecake. wtf.
which one of these threads should i use for the latest firmware on the atrix to root?
http://forum.xda-developers.com/showthread.php?t=1785401
http://forum.xda-developers.com/showthread.php?t=1940594
which one of these threads should i use for the latest firmware on the atrix to unlock bootloader?
http://forum.xda-developers.com/showthread.php?t=1896526
http://forum.xda-developers.com/showthread.php?t=1985031
does hash's safetrap work for backups on the ahd? i read that flashing is disabled currently, but id still like to backup
gosh so many questions! hope the trolls dont come out on sundays...........................
Click to expand...
Click to collapse
Okay, your bootloader (if it is from att) is not getting unlocked. That is the best way to put it because AT&T ruins everything. Firmware flashing, there is a utility out now. It's the best way to get back to stock. Razr HD roms should be portable, we wont know for sure until we have something to test. Cheesecake is worthless now so don't even worry about it. Moto blocked us from accessing their servers. It really seems like you aren't going to like this to be completely honest. You are probably more of a nexus 4 or gs3 guy....
SirHoover2010 said:
Okay, your bootloader (if it is from att) is not getting unlocked. That is the best way to put it because AT&T ruins everything. Firmware flashing, there is a utility out now. It's the best way to get back to stock. Razr HD roms should be portable, we wont know for sure until we have something to test. Cheesecake is worthless now so don't even worry about it. Moto blocked us from accessing their servers. It really seems like you aren't going to like this to be completely honest. You are probably more of a nexus 4 or gs3 guy....
Click to expand...
Click to collapse
sincerely, ill get by with just root so to sum it all up, no bl unlock or proper recovery, but purely just root (which is fine by me ) which i can obtain by using THIS? seems your the one who made that tool kit so your clearly the man to ask i can use your utility to obtain root, and even retain root after the upgrade to the test build of jb?
your so awesome sirhoover
hapticxchaos said:
sincerely, ill get by with just root so to sum it all up, no bl unlock or proper recovery, but purely just root (which is fine by me ) which i can obtain by using THIS? seems your the one who made that tool kit so your clearly the man to ask i can use your utility to obtain root, and even retain root after the upgrade to the test build of jb?
your so awesome sirhoover
Click to expand...
Click to collapse
Yes you can use that utility to obtain root
Want to downgrade Android version using the RAZR i? Be careful, there are many bricks and things you should know before you do this. Bricked means that the phone is not working or responding to official manufacture software or resetting, essentially a 'hard brick' phone is normally not able to be repaired by the user without exchanging parts inside the phone.
Avoiding Bricked Phones
1. One of the most important rules after you have downgraded/unlocked bootloader is do not accept an Over the Air (OTA) update! Users are reporting that it bricks phones!
2. Do not downgrade from Jelly Bean to Ice Cream Sandwich using RSD Lite, this defnitely results in a hard-bricked phone that cannot be recovered with software. Downgrading using a fastboot can be done yet it is still risky - there are a lot of bricked phones.
Downgrading Jelly Bean to Ice Cream Sandwich
Some users are able to do this while avoiding bricks. There is a huge amount of bricks related to this though. Really know the phone and recovery methods before you try to do it.
Recovering Over The Air brick
If you have unlocked your bootloader and then receive a message notification on your phone or computer saying that there is an update, don't update! This is resulting in a 'soft brick'. If you have a soft brick, download RSD lite (linked below) and flash a ROM.
The Most Common Type of RAZR i Brick
What does the screen say? "Service Required, Code Corrupt"
How? I get about 10 messages per day with this, it's becoming easier to see how the bricks are happening. 1. Using a homemade fastboot or RSD to downgrade from Jelly Bean to Ice Cream Sandwich. Next, the user accepts a Motorola update (called Over The Air). This creates a brick. Then users are trying a popular "unbrick" method which unbricks, then hard bricks. I think the modifcations and downgrade procedures are somehow incompatible, they don't work well together, it is producing the worst kind of brick and it happens here *every day*.
Here I will add links to bricked phones because of the downgrade, there are many more RAZR i threads for bricking from modifications and root in addition to these:
http://forum.xda-developers.com/showthread.php?t=2185954
http://forum.xda-developers.com/showthread.php?t=2126440
http://forum.xda-developers.com/showthread.php?t=2197005
http://forum.xda-developers.com/showthread.php?t=2180972
http://forum.xda-developers.com/showthread.php?t=2191234
http://forum.xda-developers.com/showthread.php?t=2189185
http://forum.xda-developers.com/showthread.php?t=2184877
http://forum.xda-developers.com/showthread.php?t=2157162
http://forum.xda-developers.com/showthread.php?t=2146350
http://forum.xda-developers.com/showthread.php?t=2123324
http://forum.xda-developers.com/showthread.php?t=2173614
http://forum.xda-developers.com/showthread.php?t=2162505
http://forum.xda-developers.com/showthread.php?t=2018998
http://forum.xda-developers.com/showthread.php?t=1945176
http://forum.xda-developers.com/showthread.php?t=2150770
http://forum.xda-developers.com/showthread.php?t=2147442
http://forum.xda-developers.com/showthread.php?t=2095661
http://forum.xda-developers.com/showthread.php?t=2089559
http://forum.xda-developers.com/showthread.php?t=2140305
http://forum.xda-developers.com/showthread.php?t=2138640
http://forum.xda-developers.com/showthread.php?t=2136962
http://forum.xda-developers.com/showthread.php?t=2131564
http://forum.xda-developers.com/showthread.php?t=2127864
http://forum.xda-developers.com/showthread.php?t=2134391
http://forum.xda-developers.com/showthread.php?t=2130903
http://forum.xda-developers.com/showthread.php?t=2121392
http://forum.xda-developers.com/showthread.php?t=2119961
Still want to downgrade? Make sure you have ready enough about recovery etc. and note the huge number of bricks after downgrading Jelly Bean to Ice Cream Sandwich.
Flashing an Original ROM with Motorola's RSD Lite Flash Tool
Use this tool entirely at your own risk. If you modify your phone using this tool, it is your responsibility. This tool is intended to be used by those that have read about ROMs/flashing, including the XDA University guides on this. This should not be used unless you are familiar with these processes. There are many, many new users with bricked phones so don't take this casually! Using this tool to flash wipes all user data. This method of flashing is not known to fix "service required, code corrupt".
The source of this guide is the official Motorola document on this in addition to my own usage.
1. You need to make sure you have the Motorola drivers for the phone installed. You can get them here.
2. You need RSD Lite. You can download that here.
3. You need to download the original ROM that you want to flash. You can download one from here.
4. Your phone should be charged to at least 50%, but I recommend a full charge.
5. Start RSD Lite. Now put the phone in fastboot mode. Connect the phone to the computer.
6. Press the 'browse' button and select the ROM to flash. Your phone should be visible in the lower box on the screen. The ROM information should be visible in the top box to the right.
7. Click the start button. You select the ROM you want and de-compress the ROM. Now flash. When it is finished, it should say that it has completed or failed.
-----Reserved-----
Bricked Moto? Fastboot not responding so can't use RSD lite? Problems switching between Android versions, accepted Over The Air update with unlocked bootloader?
SharpnShiny said:
OK I may be able to help, I've found something.
Bricked Moto? Fastboot not responding so can't use RSD lite? Problems switching between Android versions, accepted Over The Air update with unlocked bootloader? Private Message me!
Click to expand...
Click to collapse
Can you post it here?
Check your mail. :good:
hi
SharpnShiny said:
Check your mail. :good:
Click to expand...
Click to collapse
please post it here .
I have a problem when it begins to vibrate and then turn off. Gets the green light but nothing appears. Can anyone help me?
iMillerp said:
I have a problem when it begins to vibrate and then turn off. Gets the green light but nothing appears. Can anyone help me?
Click to expand...
Click to collapse
Didi you try this solution?
St.Noigel said:
Didi you try this solution?
Click to expand...
Click to collapse
Yes, I tried, but now the message "Service Required Code Corrupt"
When people use that unbrick solution for a 'soft brick', it seems to be 'hard bricking the device' entirely. Personally, I wouldn't use that method for anyone who hasn't used it before.
Hard Brick!! Help
I have the same problem. I tried a few times the unbrick jb to ics method and it works fine, but now after i charged up my battery and would to restart it doesn't load the the software. still having the bootloader logo. i shut it down and unbricked it like this: http://forum.xda-developers.com/showthread.php?t=2184877. After that it reboots, but it says "Service Required Code Corrupt".
Please Help Me!!!!!!
@op
when you used an ota your BOotloader will get a update too thats the problem!
if your bootloader is for jb and you flash ics you will brick. for sure!
if you ever flashed fastboots and never an ota you still have the ics bootloader(i can post later a vers. number of mine ics Bootloader) i think when u downgrade with the correct bootloader you wont get a brick.
but iam not 100% sure. so better dont downgrade!!!
regards
Some users reported that some lines of code in jb fastboots trigger the lock too. But either way, I agree, this phone is quite risky to downgrade!
Nice tuto guy!
but you can add information to unbrick to your tuto...
Excuse my ignorance, but what reason would someone have to downgrade from a "stock" JB to ICS?
I want to know because I'm getting the notification from my carrier that the OTA update is available and I want to know if there's any reason I should not. Currently I'm looking for ways to keep my root(ICS) going into JB and I'm reading about otarootkeep as an option, but I'm wondering if after I upgrade and it doesn't work(lets hope it does), if there's an alternative to root JB without unlocking the bootloader(the same as I have it right now).
Thanks for any replies.
r1c47 said:
Excuse my ignorance, but what reason would someone have to downgrade from a "stock" JB to ICS?
I want to know because I'm getting the notification from my carrier that the OTA update is available and I want to know if there's any reason I should not. Currently I'm looking for ways to keep my root(ICS) going into JB and I'm reading about otarootkeep as an option, but I'm wondering if after I upgrade and it doesn't work(lets hope it does), if there's an alternative to root JB without unlocking the bootloader(the same as I have it right now).
Thanks for any replies.
Click to expand...
Click to collapse
Hi. Well, one of the major reasons that people listed was battery problems. I have to admit, with ICS, my battery lasted 2-3 days. With JB, it last about 1 day. Many people said it was Google Now in JB. I always kept that off, and yet my battery was just 1 day. I did all of the usual things, formatting SD, wiping everything, factory reset, and a lot more, and still just 1 day. There are threads about that, a lot of people not happy with JB battery performance. I know other people had other issues, but just one I had in common with most people was battery.
OK I know there are a few threads on this, I found one about ICS/JB performance that you may be interested in reading: http://forum.xda-developers.com/showthread.php?t=1943058&page=3
Personally, I don't think there's a 'wrong' option, but do know that downgrading from JB to ICS on this phone is creating a LOT of bricked phones. So it would be safer to choose one OS or the other! Good luck!
matheusgallo said:
Nice tuto guy!
but you can add information to unbrick to your tuto...
Click to expand...
Click to collapse
No problem! I know for a fact that OTA bricks can be solved with RSD Lite, so that's one positive note! I'll update as soon as I can.
Dear sir,
I am using JB GB (Unlock & root) flash over RSD , then i Omar rom & now Pillama0.8 , can i use mattgroff homemade fastboot to JB (91.2.26001.Retail.en.EU.zip) and then mattgroff homemade fastboot to ICS (81.5.39001.Retail.en.GB.zip - NOTE:must i use mattgroff JB ADB&FASTBOOT file?)
Switching between 2 anytime without any OTA update is ok right?
Thks
Also using Galaxy tab & used to jump among this 3 from GB to ICS & JB with no problem cause each switch (flash or CWM) will flash alterbridge86 developer GB-Stock-Safe-v5.zip which clean & repartition. Hope some can do that for us too.Thks
Bootloader Stucks
HI all, I really need your help:
I've unlocked bootloader through procedure on Motorola website: bootloader has been locked and phone worked well.
after few days I tried to root my phone using Razr_i_root tool.
message on screen reported that root was complete but phone is keeping rebooting itself.
I've tried to make a Factory recovery but with no success.
Also tried to reflash original ROM with RSD lite but installation was aborted at "gpt installation"
I really don't know how proceed...
PLease HELP MEEE!!!
I have not seen those messages before, I cannot figure out how you got them.
Did you install any modifications at all in the few days after your unlocked the bootloader? If you only unlocked the bootloader and rooted, there should be no problem. Since there is a bootloop problem, there must be a conflict. If you have made any more modifications it will likely be them. I would have said try RSD Lite but if that didn't do anything...p.s. do you have a nandroid backup? Did you flash a recovery? Can you get into recovery?
I've posted about this here and there but I think that I have enough data for a wide audience now.
Let me start at the beginning.
I got an international I9305 from the Nordic region about 2,5 years ago, can't remember exactly which build of Android was on it, but it had a stock FM tuner app which I've used at school to check if the FM transmitter we built over the course of a class project was working. Shortly after that instance I got an OTA update( to 4.3 or 4.4.4, sadly can't recall) after which the app disappeared and I lost FM functionality(I had trouble rooting at the time, so Spirit FM was not helpful)
Currently I'm on a custom stock-based ROM made by @MaHo_66 from his thread here, running the UFPB1 build on NEE CSC(Props to him for doing a fine work with these ROMs ), but either the ROM or AGNi do not implement drivers/libraries/dependencies for FM functionality.
So now I turn to you.
I'm searching for devs that have this device and/or are willing to help with this, I'm way past warranty and will try anything to restore FM functionality, just for the sake of proving that it works. (And maybe this thread helps other people who have this device)
How do I support my statements you ask?
The FM is built into the WiFi/BT chip, which is the BCM4334, or as Samsung references it, the SWB-B53, which is probably a modified/proprietary version of the BCM4334 made by Samsung itself, so not much info on it or a separate datasheet. So we know the chip is there, it's just a matter of gaining access to it. Though the service manual shows the connector to the FM antenna to be grounded, this might not be the case for every single motherboard (as I know mine has worked in the past, there's no way it's grounded(OR it's supposed to be because the headphones are used as the antenna, not sure on this one))
I've attached screenshots of the system info, SD Insider showing that the chip is in fact the one talked about earlier, and shots of the motherboard disassembled. The chip that's right under the power button is the one we're looking for. This proves that the hardware is there, we just need software to run it
Sorry for the long post and thanks for your time in advance, all responses are valued
I won't be able to help that much here but FYI here is an old thread (2012) about this topic in case you missed it: FM Radio Not in most I9305 Firmwares, But it may be Hardware capable.
I take the opportunity to say that your post itself is very clear, well explained and nicely documented and it's a good idea to start it, I really hope you will get some help.
:fingers-crossed:
I've seen that thread, but it seems that the folks back then didn't arrive to a conclusion, and there's not much helpful data on the topic
I've also seen threads like this and this, where there's a lot of speculation talk and little concrete helpful information
And thanks, I study electronics engineering, I am required to provide a lot of data in a clean, well documented manner
xda seems to be choking with traffic today
Nice work! Good to see how we started with a notion and then the process of elimination until we proved it :good::highfive:
The thread @Wood Man mentioned is the one I was referencing to you earlier .:good:
Sent from my Samsung GT-I9305 using XDA Labs
@AlexJumper: I fully concur with the statements of @Wood Man and @alias_ z3d!
Precise, comprehensive where necessary but always concise. I'd be glad if I could read more of such posts on XDA.
Don't know if this thread is helpful; found the thread yesterday after flashing a S3 Mini (i8190) with this ROM.
alias_ z3d said:
Cool I'll have a look and thank your post once I get some back. I think @noc.jfcbs would offer invaluable assistance since he's started a lot of threads I've only got one.
Click to expand...
Click to collapse
But here, alias_z3d is wrong. I've only started three threads and nothing special; maybe a forth is coming soon.
You don't require any support; the way you commenced this thread is excellent.:good:
Spirit FM would be a solution, but either the ROM or the kernel I'm running right now doesn't have drivers for FM, so it won't work for me
Basically I'm looking for a way to implement(port?) drivers from firmware that has them to my current ROM, or a way to flash said firmware through custom recovery.
I've tried to downgrade through Odin, but I've been unsuccessful up to this point.
AlexJumper said:
Spirit FM would be a solution, but either the ROM or the kernel I'm running right now doesn't have drivers for FM, so it won't work for me
Basically I'm looking for a way to implement(port?) drivers from firmware that has them to my current ROM, or a way to flash said firmware through custom recovery.
I've tried to downgrade through Odin, but I've been unsuccessful up to this point.
Click to expand...
Click to collapse
What's your problem with Odin? Maybe, someone or me can help? BTW. Which recovery are you using? What's your bootloader?
Before I tried fiddling with rooting and whatnot, I was on stock 4.4.4 so that's definitely the Knox bootloader, after that I got TWRP when Unified Android Toolkit got support for all I9305 builds, then I was able to flash whatever I tried to through TWRP.
I got back to a 4.1.1 build following instructions from this thread, which describes a SIM unlock procedure but it also promises that
You can update, Root, flash custom and stock rom and everything you want. It will stay unlocked
Click to expand...
Click to collapse
(Thinking about it again, I may have misunderstood that )
Anyways, then I got to flashing one of MaHo's ROMs, the build that I'm on right now is I9305XXUFPB1.
But when I was trying to downgrade to find a build that had FM functionality, in one instance I got bootlooping and no recovery access, in another Odin failed to flash(because of it trying to flash an older bootloader over Knox's bootloader) and I had to emergency recover via Smart Switch.
It flashed a newer build though, and since that, every time I flash older firmware through I get bootloops. (Or I just suck at making Odin-flashable packages )
Here's what UAT has to say, seems like I have the latest bootloader now
Oh and I currently have TWRP 2.6.3.0 as custom recovery
noc.jfcbs said:
@AlexJumper: I fully concur with the statements of @Wood Man and @alias_ z3d!
Precise, comprehensive where necessary but always concise. I'd be glad if I could read more of such posts on XDA.
Don't know if this thread is helpful; found the thread yesterday after flashing a S3 Mini (i8190) with this ROM.
But here, alias_z3d is wrong. I've only started three threads and nothing special; maybe a forth is coming soon.
You don't require any support; the way you commenced this thread is excellent.:good:
Click to expand...
Click to collapse
Yes he doesn't need support it looks great I said that in regards to structuring a thread before I checked it out
I think your being modest considering you've got one pinned
Sent from my Samsung GT-I9305 using XDA Labs
AlexJumper said:
Before I tried fiddling with rooting and whatnot, I was on stock 4.4.4 so that's definitely the Knox bootloader, after that I got TWRP when Unified Android Toolkit got support for all I9305 builds, then I was able to flash whatever I tried to through TWRP.
I got back to a 4.1.1 build following instructions from this thread, which describes a SIM unlock procedure but it also promises that
(Thinking about it again, I may have misunderstood that )
Anyways, then I got to flashing one of MaHo's ROMs, the build that I'm on right now is I9305XXUFPB1.
But when I was trying to downgrade to find a build that had FM functionality, in one instance I got bootlooping and no recovery access, in another Odin failed to flash(because of it trying to flash an older bootloader over Knox's bootloader) and I had to emergency recover via Smart Switch.
It flashed a newer build though, and since that, every time I flash older firmware through I get bootloops. (Or I just suck at making Odin-flashable packages )
Here's what UAT has to say, seems like I have the latest bootloader now
View attachment 4168400
Oh and I currently have TWRP 2.6.3.0 as custom recovery
Click to expand...
Click to collapse
In the attached screenshot you see my Bootloader I9305XXUEMKC, I think it's still the one from 4.3 JB. And I definitely suggest to upgrade TWRP to 3.0.2-1 that I also use. I personally won't go to higher custom TWRP versions that are out, because I read about some issues with them; e.g. @alias_ z3d had issued a warning in rodman01's RR thread.
How about just to flash through Odin Chainfire's CF-Auto-Root for Android 4.1.1 again, and - if that works - to start from there
samsung
GT-I9305 m3zh m3 smdk4x12 exynos4 JRO03C.I9305ZHALI8 4.1.1 18 650 167 Download 8319b7feffffdc083ef73450acb1d145 476 430
Click to expand...
Click to collapse
Finally, this week I just rooted an i8190 via Odin and had initially a bad experience but finally a very easy solution. At the end of the ROM flash by Odin, the device automatically booted into system as this was ticked in Odin. It was constantly booting, I assume a bootloop, and after about 2 hours I lost patience. Took the battery out, inserted it again, and started into recovery (home+vol up+pwr). At that time, still the stock recovery was installed i.e. no real capabilities. But at least, I could wipe cache and data. Did that and initiated a boot into system. And that was it. Booting took about 2 minutes, and I had a rooted i8190. Next thing I did, was to flash TWRP 3.0.1 onto the i8190 by Heimdall.
So my course of action is:
1) Go back to 4.1.1
2) Flash CF Auto Root
3) Flash TWRP
4) Flash whatever else
Am I correct?
AlexJumper said:
So my course of action is:
1) Go back to 4.1.1
2) Flash CF Auto Root
3) Flash TWRP
4) Flash whatever else
Am I correct?
Click to expand...
Click to collapse
Affirmative. If I had to play with this device I'd try the following but not knowing if it works:
NO WARRANTY - Use at your own risk, I'm not responsible for bricking your device.
Flash the above linked CF AutoRoot tar.md5-file through Odin, which hopefully reverts you to the desired 4.1.1 (unless this file works try the other CF AutoRoot for 4.4.4 - that's actually the one, with which I rooted an i9305 months ago)
Flash TWRP 3.0.2-1 via Odin or apps like Flashify (the one I use) or Flashfire etc.
Further flashes depend on your desire. Other ROM (hopefully with FM radio drivers), baseband/modem etc.
Instead of using Odin you could certainly also take Heimdall. I used Heimdall only once thus far for the mentioned i8190 to flash a TWRP-3.0.1.img (explained here and here a bit more in detail).
I searched the web like hell for Samsung ROM FM radio driver but no joy.
Ok so I got back to the 4.1.1 build from the thread I linked in my previous post, apparently my bootloader somehow changed..
The CF Auto Root file though seems to be based on a slightly different build than the one I've got now (JRO03C.I9305ZHALI8 while I have JRO03C.I9305XXALI5), should I flash it or is there a possibility it breaks something?
Nevermind, it worked flawlessly
I also updated TWRP to 3.0.2-1.
Now to find a way to get to the builds I need
AlexJumper said:
Ok so I got back to the 4.1.1 build from the thread I linked in my previous post, apparently my bootloader somehow changed..
View attachment 4169145
The CF Auto Root file though seems to be based on a slightly different build than the one I've got now (JRO03C.I9305ZHALI8 while I have JRO03C.I9305XXALI5), should I flash it or is there a possibility it breaks something?
Click to expand...
Click to collapse
Super. I thought the main intention was to bring the device back to 4.1.1, and that was accomplished.
Is it (still) rooted?
If it is, I wouldn't continue with CF-AutoRoot as its only purpose is to get a device rooted.
If you still need root, I personally would continue but I don't know if you might brick the phone.
noc.jfcbs said:
Super. I thought the main intention was to bring the device back to 4.1.1, and that was accomplished.
Is it (still) rooted?
If it is, I wouldn't continue with CF-AutoRoot as its only purpose is to get a device rooted.
If you still need root, I personally would continue but I don't know if you might brick the phone.
Click to expand...
Click to collapse
No, I needed to get back to 4.1.1 as a start because flashing older builds was a pain with 4.4.4 and its bootloader.
AlexJumper said:
No, I needed to get back to 4.1.1 as a start because flashing older builds was a pain with 4.4.4 and its bootloader.
Click to expand...
Click to collapse
The e.g. i8190 has a FM receiver. Maybe it works if you grab some commits from firmware of the i8190 and incorporate it into your ROM. I know you can't compare S3 LTE and S3 Mini with their totally different hardwares but...
That would require them to have the same FM chip at least(which I doubt), as well as libraries/dependencies I guess.
noc.jfcbs said:
In the attached screenshot you see my Bootloader I9305XXUEMKC, I think it's still the one from 4.3 JB. And I definitely suggest to upgrade TWRP to 3.0.2-1 that I also use. I personally won't go to higher custom TWRP versions that are out, because I read about some issues with them; e.g. @alias_ z3d had issued a warning in rodman01's RR thread.
Click to expand...
Click to collapse
3.1.1-0 was not a custom TWRP!
It was official
Iller Chiller said:
3.1.1-0 was not a custom TWRP!
It was official
Click to expand...
Click to collapse
Yeah it was officiall twrp 3.1.1-0 for me from team win website. However I don't think I made it clear in my post.
Sent from my Samsung GT-I9305 using XDA Labs