Related
Hi all,
I have gone through the rooting for dummies guide, but as my intentions are slightly different can anyone help me by briefly writing down the steps for Rooting and Keeping Stock Rom and keeping Stock Recovery so that I can update it when google releases 2.2.
Would highly appreciate it.
You shouldn't have any problems updating to 2.2 if you flash amon's recovery.
Which recovery you have has no bearing; so long as you're rooted, you'll be able to download 2.2 and flash it. If your goal is to make the transition from 2.1 to stock 2.2 as easy as possible then, sure, stay with stock. I figure CM will probably have a 2.2 ROM out faster than most stock phones would have been able to download it via OTA, though, so I'm sticking with CM5.0.6 and will update whenever CM does.
same here.
trusting cyanogen
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am using Enom. With Titanium backup it really doesn't mean much to switch roms
My understanding is that once you install a custom recovery you can not get ota. They show up as available and are clickable but fail. This was the experience described at the last ota. Are you folks that are saying you can still get ota after installing a recovery speaking from experience? In other words did you have a custom recovery installed and sucssesfully update at the last ota?
Thanks guys for the input, but like krabman said, i also heard if you put a custom recovery you cannot get the ota to work! Any confirmation on that?
with custom ROMs and custom recoverys, you will not be able to install OTAs. Most custom ROMs disable OTAs since they kinda break the custom ROM functionality like root access. Most OTAs reboot the phone into recovery to update the software. A custom recovery like Amon RAs recovery can only accept ROMs and updates signed with test keys. Any update released by Google/HTC which is officially signed will not work.
But this should not prevent anyone from installing custom ROMs and recoverys since most cooks include the latest updates very soon, sometimes even before the official releases...
What if you follow the Original Shipping Tutorial to restore you phone's original recovery system?
http://forum.xda-developers.com/showthread.php?t=614850
I would imagine if you followed that you would be back to a completely stock phone that would work with OTA updates.
But, if you don't plan on running any custom roms, why bother unlocking the boot loader at all? If you haven't already done it, I wouldn't.
Amon ra recovery can only accept ROMs and updates signed with test keys. Any update released by Google/HTC which is officially signed will not work. Nor will the stock recovery work since it loses its official signature when it gets ripped so the ota cant use it because it requires an officially signed recovery to install itself with. If this is incorrect then I look forward to being properly schooled. I can say that I have yet to find anyone that had a custom recovery on at the ota last time that was able to get the update and install it ota.
krabman said:
Amon ra recovery can only accept ROMs and updates signed with test keys. Any update released by Google/HTC which is officially signed will not work. Nor will the stock recovery work since it loses its official signature when it gets ripped so the ota cant use it because it requires an officially signed recovery to install itself with. If this is incorrect then I look forward to being properly schooled. I can say that I have yet to find anyone that had a custom recovery on at the ota last time that was able to get the update and install it.
Click to expand...
Click to collapse
Well that's great news. I regret unlocking my phone more every day.
To be honest this is pretty much a non issue as far as ota goes. The stock rom with the ota on it, or in other words the lastest official release, will be available to download here within hours of its release and you can flash it like any other rom. If they do a rolling release it may well be you can download it before it becomes available over the air.
PrawnPoBoy said:
What if you follow the Original Shipping Tutorial to restore you phone's original recovery system?
http://forum.xda-developers.com/showthread.php?t=614850
I would imagine if you followed that you would be back to a completely stock phone that would work with OTA updates.
But, if you don't plan on running any custom roms, why bother unlocking the boot loader at all? If you haven't already done it, I wouldn't.
Click to expand...
Click to collapse
The reason I want to unlock the boot loader is to only use the metamorph and a few other launchers. I am a theme-freak so I could customize the look of the stock rom, but now that you all mention it, I guess I will stick with the Stock find other ways to theme it.
Thanks everyone.
PrawnPoBoy said:
What if you follow the Original Shipping Tutorial to restore you phone's original recovery system?
http://forum.xda-developers.com/showthread.php?t=614850
I would imagine if you followed that you would be back to a completely stock phone that would work with OTA updates.
But, if you don't plan on running any custom roms, why bother unlocking the boot loader at all? If you haven't already done it, I wouldn't.
Click to expand...
Click to collapse
After flashing CM's ROM, I was able to completely restore my phone to shipping state (sans relocked bootloader, of course), and then perform the 2.1-update1 OTA.
So yes, you will be able to update to 2.2 as soon as Google releases the OTA, but you'll have to completely revert back to stock in order to do it?
I'm not really sure about what I'm talking about, but I just wanted to confirm that you CAN perform OTA updates even after flashing a custom recovery image/ROM.
I cracked the screen on my last captivate, which had no problems getting into download mode. This phone will not go into download mode. I've tried all button combos, with all the same results. Either looping ATT logo, or the battery charge icon comes up.
Am I SOL? I'm hoping there's a fix for this, either now or coming out in the future. Im the meantime, should i be careful with my phone? I was planning on going from cognition 2.1.4 to 2.2 beta 5.5. Im a little nervous though, knowing i might brick my phone for good.
someone, please tell me there's a fix!!!
My first captivate had this problem.. I had to send it back to get a new one.
I am also interested in what the story is with phones with no 3 button recovery and no USB download modes.
I recently purchased one that has the defect. CAL Date is 17th August.
Currently debating if I should send it back for a refund or not. (I am in Australia, and the retailer has informed me that all new phones now have this defect due to it being a deliberate disabling by Samsung. So getting a working replacement from them is out of the question.
Does anyone have a newer Captivate than mine that had USB download mode and 3BR working out of the box?
I am guessing the odds of me finding one of the pre August models with 3BR and USB working are pretty low.
Will there ever be a permanent fix for this? (Not OTA update, not much good for people who are not on the AT&T network)
FYI, I bought my phone about a week or two ago via amazon wireless and it was a 7.11.2010 model.
It's a hardware issue. So if it's driving you crazy then try to exchange it, but the leaked froyo one-click odin patched it for me.
bryman27 said:
It's a hardware issue. So if it's driving you crazy then try to exchange it, but the leaked froyo one-click odin patched it for me.
Click to expand...
Click to collapse
Really? You had no 3br before, never did AT&T OTA and got it when you installed Froyo with Odin?
Not sure if I want to use Odin to patch that though, lost one already
Tremere said:
Really? You had no 3br before, never did AT&T OTA and got it when you installed Froyo with Odin?
Not sure if I want to use Odin to patch that though, lost one already
Click to expand...
Click to collapse
yes, yes, and yes
you could see if "adb reboot download" will get it into download mode.
Similar to the other poster, I've also heard that upgrading to 2.2 fixed the "no 3-button download mode" issue. Several people reported it.
j1mb34m said:
Similar to the other poster, I've also heard that upgrading to 2.2 fixed the "no 3-button download mode" issue. Several people reported it.
Click to expand...
Click to collapse
would this mean that cog beta 5.5 would also fix the 3br issue, since it is built on top of the leaked build?
i dont have 3br and cant get the ota since im in australia
ppau0822 said:
would this mean that cog beta 5.5 would also fix the 3br issue, since it is built on top of the leaked build?
i dont have 3br and cant get the ota since im in australia
Click to expand...
Click to collapse
The odin version for sure. I don't know about the clockwork version.
I upgraded to cog 5.5 via ROM manager. I still can't get into download mode. Will it make any difference if i flash with odin? And how do i flash with Odin if i can't get into download mode?
If theres no way i could do this on my phone, is it really worth returning/trying to get a different one? If im just extra careful when i change roms, what are the chances of bricking my phone? Would there be any way to fix it after this happens?
My one and only Cappy could never get into dload or recovery mode at all. Rather than return it, I have found workarounds, but they are definitely risky!!
HOWEVER, tonight I have some interesting news... I have found a way to get into recovery mode like this:
1. Start from phone off, then press power+volume up + volume down, and hold.
2. Wait until the 4th AT&T screen comes on, then release the VOLUME buttons, but still hold power.
3. The phone should go into recovery mode.
I tested this several times and it worked every time!
Now I know this is not download mode, but it is a start for those of us who have trouble (or no) 3 button recovery. My point is, maybe there is a different "combo" that will work.... I'm just saying.
You should be able to get into recovery by simply holding vol up vol down and power until att splash screen comes up first time...
As for not getting into download mode using vol buttons and plugging in usb, ie having to use adb, flashing roms is risky as you may not be able to Odin back to a working phone if something hapoens
Sent from my SAMSUNG-SGH-I897 using XDA App
newter55 said:
You should be able to get into recovery by simply holding vol up vol down and power until att splash screen comes up first time...
As for not getting into download mode using vol buttons and plugging in usb, ie having to use adb, flashing roms is risky as you may not be able to Odin back to a working phone if something hapoens
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes I (and many others) know that vol up+voldn+pwr SHould work, but it doesn't for some of us. I just tried again to be sure.
Yes I know the workarounds are risky, read my post.
I was just saying that if I have found a way to get into recovery with an alternate method of the 3 button deal, then maybe there is an alternate method to get into download mode too.
lourivellini said:
I upgraded to cog 5.5 via ROM manager. I still can't get into download mode. Will it make any difference if i flash with odin? And how do i flash with Odin if i can't get into download mode?
Click to expand...
Click to collapse
Use adb to reboot into download or recovery. If you are rooted you can just type 'reboot download' into a terminal as well.
ROM manager flashes will not fix the 3br as they do not flash any bootloader blocks.(at least in the current releases)
Does the Odin Cog5.5 restore 3br or just the leaked Froyo?
i just bought my cappy a week back....i just rooted it....the 3 button combo is working for me....if u want i can write down any version or manufactoruing date u want to know....just tell me how to(im a noob)
Cog 5.5 didn't fix the 3 button problem for me.
My 3 button access was fixed when I went back to stock 2.1 via 1click odin and then requested the ATT OTA upgrade. It said failure, but my 3 button access worked after that.
After that I used Rom Manager to flash Cog 2.2(don't remember which beta)... lost 3 button access... not sure why. Most threads I've seen on that topic say it shouldn't do that, but it did.
So went back, redid it all, then flashed Cog 5.5 via Odin3... working like a champ now. Easy 3 button recovery and download where I had nada before.
krl66 said:
Cog 5.5 didn't fix the 3 button problem for me.
My 3 button access was fixed when I went back to stock 2.1 via 1click odin and then requested the ATT OTA upgrade. It said failure, but my 3 button access worked after that.
After that I used Rom Manager to flash Cog 2.2(don't remember which beta)... lost 3 button access... not sure why. Most threads I've seen on that topic say it shouldn't do that, but it did.
So went back, redid it all, then flashed Cog 5.5 via Odin3... working like a champ now. Easy 3 button recovery and download where I had nada before.
Click to expand...
Click to collapse
goddam really?
What im planning on is one click flashing back to the original firmware, then seeing if it works, then if now ill try jh3, etc until one works.
Sorry if this has already been addressed, but shouldn't this be a firmware issue?
Brand new Captivate, no 3br. Flashed Cog 2.2b6 right away with Odin and it was enabled
Sent from my SAMSUNG-SGH-I897 using XDA App
I fought with mine all day yesterday trying every trick I found on the net. I finally just downloaded the SDK and did the "adb reboot download" thing and whammo...fixed.
I just got a Nexus One that was ROMed and rooted (has RA-nexus-v2.0.0 recovery) and enom's 2.14.2 ROM. I don't very much like it (seems slow). I am trying to go back to STOCK Android 2.2.2, with Root access, in preparation for 2.3's release. I know how to use ADB so that's not my problem. I've downloaded FRG91 in hopes that I will get an OTA to FRG83G. Now here's where I start getting problems. I go into Recovery, go to Flash Zip from SD card, and try to flash it, but it says it doesn't have signatures. md5sum is correct so that's not it. Can anyone help me out? I've tried doing about 10 different things so far and none of them have worked. Maybe someone else has seen this? TIA.
Have you try to toggle signature verification off?
Here's a rooted 2.2.2 rom
http://forum.xda-developers.com/showthread.php?t=927935
I haven't. I think I might have found a way to get this baby working. I'm working on it now. If I need anymore help, I will re-ask in this thread. Thanks for the tip though, didn't think of that!
Alright. I think I got it to work. Had to do some fenagelling, but I got it back to stock 2.2.2 Official.
Admin, can you delete this post?
You can't flash stock roms without stock recovery, Google's signature is on the stock roms so only stock recovery recognizes it. There is also a option in your custom recovery to turn of signature verification. I wouldn't recommend that you try, because I don't know what would happen. But it's a option, if your that hard pressed to go back to stock. Another note, since the G1 days the devs built their roms to stop OTA updates. So if you flash stock recovery, then you may need a stock rom to receive a OTA. I wouldn't get my hopes up about getting Gingerbread or Honeycomb OTA. I don't see anything on any android forum about this happening, I could be wrong though. If you can get your hands on a stock recovery image then you can flash with adb or fastboot commands. Good luck.
Go here for further assistance
http://forum.xda-developers.com/showthread.php?t=614850
blas4me said:
You can't flash stock roms without stock recovery, Google's signature is on the stock roms so only stock recovery recognizes it. There is also a option in your custom recovery to turn of signature verification. I wouldn't recommend that you try, because I don't know what would happen. But it's a option, if your that hard pressed to go back to stock.
Click to expand...
Click to collapse
Turning off signature verification works fine. No problems whatsoever flashing stock ROM/updates.
blas4me said:
Another note, since the G1 days the devs built their roms to stop OTA updates. So if you flash stock recovery, then you may need a stock rom to receive a OTA. I wouldn't get my hopes up about getting Gingerbread or Honeycomb OTA. I don't see anything on any android forum about this happening, I could be wrong though. If you can get your hands on a stock recovery image then you can flash with adb or fastboot commands. Good luck.
Go here for further assistance
http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
OTA updates have nothing to do with a stock recovery. All newer versions of Amon_RA and CWM custom recoveries have signature verification toggles, so you can install OTA updates without problems.
The only thing is that you need to have a stock ROM (not de-odexed, and not an AOSP build) for the OTA update to install.
I was working on getting 4.4 AOSP kitkat on my Atrix HD, and it was going great. While backing up with CWM, it failed on the data, but I figured I could just restore my files from a back up. When I went to put the rom on it, I got some no_contexts error and it said somethign about metadata. I tried to restore the backup and got a md5 fail. I used the advanced restore to let it skip the data part, but all parts gave a md5 fail. Now for somereason, I'm unable to connect through ADB, though fastboot still works, so I can't try pushing a stock rom. I tried adb sideload, but that didn't even remotely work. I also can't charge my phone, and it has a low battery. Does it charge in fastboot or recovery mode? Please help.
Phew
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
ace_case said:
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
Click to expand...
Click to collapse
I'm glad to hear you got things back into working order! With regards to flashing any custom ROM, the safest way is to use a custom recovery. Currently, as far as I can tell, the only official recovery for the Atrix HD is CWM but that's fine. You do want to be sure that you have the latest, most up to date version of CWM installed. As of right now, I believe that is 6.0.4.4 (http://clockworkmod.com/rommanager, mine already might be out of date again) and that may be where your problems came from when you were wiping and getting errors.
With regards to a close to stock 4.4 for the Atrix HD, there is an official build of CM available here: http://download.cyanogenmod.org/?device=mb886 although the latest build is from February, I can assure you that from running it on my Atrix HD it is definitely much smoother than what Motorola has offered (to date) for this device. There have been promises of official 4.4 support but I haven't seen anything come from that as of today (see here for more info: http://goo.gl/oK34W0)
CORRECTION: The official support for Atrix HD is here: http://download.cyanogenmod.org/?device=moto_msm8960
It is a merged thread for all of the devices mentioned here: http://wiki.cyanogenmod.org/w/Moto_msm8960_Info
I can't vouch for it personally but others have said that it has fixed a lot of bugs since the single device support that ended in February...
So after getting the Nubia Red Magic 3, I was wanting to root it. But my first attempt was a failure and will have to flash my ROM again in recovery. Okay, whatever, no big deal. But here is something weird.
So I found out that there is a global ROM, a Chinese ROM, and an EU ROM for this phone. Apparently, I have the the EU ROM. When flashing the boot.IMG and the recovery.IMG from a global ROM I downloaded, the device would go into a bootloop (or sometimes go straight into fastboot). I figured I download the right ROM from Nubia's website. I clicked on the USA version.
Well then I have my suspicion that I was using the European ROM because I looked at the manual and it was referencing all this "compliance with the EU" regulations and stuff like that inside the manual.
So then I downloaded the EU version of the ROM and sure enough, I'm able to get into recovery again. So that means I download the right ROM. I can unbrick it now. Woop-dee-woop. But I'm still puzzled. Why did they give me a Nubia Red Magic 3 with the European stock firmware if I live in the US? Was the global ROM a separate ROM that didn't come from Nubia? Correct me if I'm wrong but, I'm assuming U.S. users get the EU version of the Nubia red magic 3??
I got a NA version of the phone. I'm not sure if you got the EU version or if through flashing yours ended up with the EU version.
It's always best to check before you start flashing your phone.
Realistically, all versions are the same, but for the roms that are installed on them. So, if you change it before checking, there's no way to tell what was originally on there.
Psyrecx said:
I got a NA version of the phone. I'm not sure if you got the EU version or if through flashing yours ended up with the EU version.
It's always best to check before you start flashing your phone.
Realistically, all versions are the same, but for the roms that are installed on them. So, if you change it before checking, there's no way to tell what was originally on there.
Click to expand...
Click to collapse
Actually I may be wrong. I might have had the NA because the recovery is not the same than the original. I'm going to try that version.
EDIT: I'm pretty much trying to get the NA version but the STOCK version. Aren't the global versions different? What does your recovery look like? Does it have the "update from local storage option" because that's what mine had.
EDIT 2: After looking at the manual, my certified version is NX629J_ENCommon_V2.04 and on another page, it says NX629J_ENCommon_V1.06. I searched for these versions on XDA but got nothing.
chocolote4444 said:
Actually I may be wrong. I might have had the NA because the recovery is not the same than the original. I'm going to try that version.
EDIT: I'm pretty much trying to get the NA version but the STOCK version. Aren't the global versions different? What does your recovery look like? Does it have the "update from local storage option" because that's what mine had.
EDIT 2: After looking at the manual, my certified version is NX629J_ENCommon_V2.04 and on another page, it says NX629J_ENCommon_V1.06. I searched for these versions on XDA but got nothing.
Click to expand...
Click to collapse
See your build number in About Phone.
alanzaki073 said:
See your build number in About Phone.
Click to expand...
Click to collapse
Can't. It won't boot at the moment.
EDIT: So it appears that my phone was using the NA version (not the global). I just need the stock version. I remember that I was on version 1.11 and updated to 1.15 (NOT THE EU VERSION AND NOT GLOBAL VERSION). But after searching everywhere on the Internet, the stock NA ROM hasn't been uploaded yet (or at least I couldn't find it). I searched everywhere. So I'll just have to wait for the NA stock ROM gets uploaded. Before I tried to root it, I remember using the recovery with the "apply update from local storage" option. I'm using the recovery where you have an option to pick two languages, and apply update from OTG.
From what I read here on XDA, you need a flash drive that is FAT32 with update.zip. But when I try to do that, it says something like "can't find OTG". So either it's not recognizing the phone in recovery or it's my flash drive. I'll try again tomorrow, but my best bet is to wait for my version stock ROM to be released. It stopped booting once I patched a different ROMs boot.IMG with Magisk. And yes, according to what some people said on XDA, you need to have the correct drivers for the Red Magic 3 and when I searched for the drivers, one website said to install the " Qualcomm Drivers" but I did that and the OTG still fails to read the USB.
I'll keep trying though. I never give up. I'll keep digging around on XDA for a possible solution.
Hopefully I am correct on all this. I could be wrong though..
chocolote4444 said:
Can't. It won't boot at the moment.
EDIT: So it appears that my phone was using the NA version (not the global). I just need the stock version. I remember that I was on version 1.11 and updated to 1.15 (NOT THE EU VERSION AND NOT GLOBAL VERSION). But after searching everywhere on the Internet, the stock NA ROM hasn't been uploaded yet (or at least I couldn't find it). I searched everywhere. So I'll just have to wait for the NA stock ROM gets uploaded. Before I tried to root it, I remember using the recovery with the "apply update from local storage" option. I'm using the recovery where you have an option to pick two languages, and apply update from OTG.
From what I read here on XDA, you need a flash drive that is FAT32 with update.zip. But when I try to do that, it says something like "can't find OTG". So either it's not recognizing the phone in recovery or it's my flash drive. I'll try again tomorrow, but my best bet is to wait for my version stock ROM to be released. It stopped booting once I patched a different ROMs boot.IMG with Magisk. And yes, according to what some people said on XDA, you need to have the correct drivers for the Red Magic 3 and when I searched for the drivers, one website said to install the " Qualcomm Drivers" but I did that and the OTG still fails to read the USB.
I'll keep trying though. I never give up. I'll keep digging around on XDA for a possible solution.
Hopefully I am correct on all this. I could be wrong though..
Click to expand...
Click to collapse
http://rom.download.nubia.com/Europe&Asia/NX629/NX629J_Z69_EN_WPJ0O_V115.zip
This is v1.15 NA. It's easily available on red magic's website
chocolote4444 said:
From what I read here on XDA, you need a flash drive that is FAT32 with update.zip. But when I try to do that, it says something like "can't find OTG". So either it's not recognizing the phone in recovery or it's my flash drive. I'll try again tomorrow, but my best bet is to wait for my version stock ROM to be released. It stopped booting once I patched a different ROMs boot.IMG with Magisk. And yes, according to what some people said on XDA, you need to have the correct drivers for the Red Magic 3 and when I searched for the drivers, one website said to install the " Qualcomm Drivers" but I did that and the OTG still fails to read the USB.
Click to expand...
Click to collapse
I had tried flashing to global 2.10 and got the same issue. I also had the 'can't find OTG' issue a few times, but eventually it found it.