Related
Hi everyone
I am a noob so be nice to me. I accidently cracked the screen on my Samsung Vibrant and so have a few questions about how to return the phone back to Stock/unrooted (just like befor i flashed). I am fine if i have to lose my contacts, apps. ect...
Background:
I rooted my phone with One-Click-Root/Unroot from XDA (loved it). I then flashed the latest Nero 5.0 ROM from Team Wiskey (Love it). As part of either the root or flashing the ROM(i can't remember which one), I downloaded "ROM Manager" with CWR.
Q #1: Is it as easy returning to stock ROM as just using "Flashing ClockworkMod Recovery" or should I have used "nandroid" (don't know what it does, but I see it talked about) also?
Q #2: I hear people say that you need Odin to return back to stock ROM, but then I hear that is ONLY if you don't have ROM Manager w/CWR. Do I need Odin or do I only need ROM Manager w/CWR?
Q #3: If all I need is ROM Manager w/CWR and it returnes back to what it was before i flashed, can i just us the "Unroot" button on the One-Click-Root/Unroot"?
Q #4(Last Question): Will I recieve OTA's if I have to us Odin and flash a stock ROM, how do I get back to stock and recieveing OTA's?
I understand that there are alot of posts asking how to return to stock but that is from people where something in the programs went wrong when trying to return to stock. I am just wondering what programs (other than ROM Manager and CWR) are need for me to return to stock? Please help, I don't want my phone to be rejected because my warranty is void. Thanks
Noob123
All thats needed to return to stock is a Nandroid backup of your original ROM.
Oh wait.....
Why do people totally fail at this?
What you need now is an original ROM for your device and then flash it from recovery.
So in other words, I need to download a 2.1 Rom (last version i had) from somewhere back on to my computer and then do the same things that i did to flash Nero 5? Is that where Odin comes in? OR, would CWR already have that ROM and everything all in one package?
Like I said, I am a nook. I am suprised that i didnt brick my phone rooting and flashing a ROM the first time. I may be pushing my luck going back to stock. But, it needs to be done if i want my phone fixed.
I would have a look HERE, in the Samsung Vibrant forum. I'm sure you'll find an Official ROM to Flash somewhere in there.
You would just put the .zip on your SD card, restart to Recovery and select the option to Flash from SD
Okay, i am getting it now. However, wont the "Update.zip" (Nero 5.0) be there on my SD memory already? Will i damage my phone if i delete the "Update.zip" and put in the Stock.zip (then do the recovery thing)? So once i get the Stock ROM uploaded on my phone, can i just use the one-click-unroot (from XDA) to have my phone be unrooted and new just like it was when i bought the phone? Will i get OTA's?
Thank you for your help, i am sorry for bugging you but i feel like i am starting to understand it more. These are probably the last questions that i have....probably
Sorry, I'm new to this so sorry if this seems dumb.
So i bought the phone from rogers and immediately updated to froyo 2.2 official release by rogers/samsung.
I read about all the hype online about rooting and custom roms so i decided to give it a shot.
I used the superoneclick method to root my phone and it was successful.
I then used "rom manager - clockworkmod" and created a restore file before i did any flashing to my phone.
after creating a backup, i went on and flashed to the cognition 3.04.
Now my question is. Am i ever able to get my phone back to its original rom, kernel, and modem? the reason i want to know is because i might need to get my phone replaced due to some technical issues with the phone.
Also, does the backup of my phone after rooting play a part in any of this? if so, how?
Im sorry if there is already a post like this one. Its just that i couldn't find the answer through all the hundreds of pages of threads and replies, so I thought it would be easier to post a here with my specific question. Thanks.
regards,
danny
dsu said:
Sorry, I'm new to this so sorry if this seems dumb.
So i bought the phone from rogers and immediately updated to froyo 2.2 official release by rogers/samsung.
I read about all the hype online about rooting and custom roms so i decided to give it a shot.
I used the superoneclick method to root my phone and it was successful.
I then used "rom manager - clockworkmod" and created a restore file before i did any flashing to my phone.
after creating a backup, i went on and flashed to the cognition 3.04.
Now my question is. Am i ever able to get my phone back to its original rom, kernel, and modem? the reason i want to know is because i might need to get my phone replaced due to some technical issues with the phone.
Also, does the backup of my phone after rooting play a part in any of this? if so, how?
Im sorry if there is already a post like this one. Its just that i couldn't find the answer through all the hundreds of pages of threads and replies, so I thought it would be easier to post a here with my specific question. Thanks.
regards,
danny
Click to expand...
Click to collapse
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Christo_69 said:
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Click to expand...
Click to collapse
Dont use that link because it is for att firmaware. I havent seen any prepackaged odin one click for rogers.
This is my captivate. There are many like it buy this one is mine.
Christo_69 said:
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Click to expand...
Click to collapse
Thanks for that. Do you think Odin is the only way to do it or do you think i can use clockworkmod
flashman2002 said:
Dont use that link because it is for att firmaware. I havent seen any prepackaged odin one click for rogers.
This is my captivate. There are many like it buy this one is mine.
Click to expand...
Click to collapse
Do I not use that link in general, or just not to use the firmware given at the bottom? the steps are correct though, no?
also from my searching.
i can put my phone back to my backup point (just after rooting) through clockworkmod. Woud this change my rom back to stock from? how about kernel and modem and all that? would that all get reversed back to my backup point? meaning it will basically be a stock phone. But I think also read somewhere that my kernel and modem does not get changed back to rogers original one. is there a way to do it?
I then found this link: http://forum.xda-developers.com/showthread.php?t=846501
that says i need the original rogers rom for the captivate by the links there no longer work for download. Also on that thread, it was mentioned that the AT&T logo will still come up on startup, which would not be a good idea if i had to send my phone in for warrenty.
I then looked at : http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Here it tells me to flash to a i9000 before i reflash to a rogers firmware in order to remove the at&t logo. it also provides me with a link for the " Official Rogers Stock ROM ", but according to somebody on the first link i posted here, it isnt the "official rom"
Any ideas?
This is where I got the stock 2.2 file from http://forum.xda-developers.com/showthread.php?t=905042.
Edit: I have flashed a bunch of times and have never got stuck with the AT&T startup after flashing back to stock with the odin file.
Akalon said:
This is where I got the stock 2.2 file from http://forum.xda-developers.com/showthread.php?t=905042.
Edit: I have flashed a bunch of times and have never got stuck with the AT&T startup after flashing back to stock with the odin file.
Click to expand...
Click to collapse
Thanks. Do you know if my kernel is going to go back to stock too or is it going to remain the same as the custom rom one?
dsu said:
Thanks. Do you know if my kernel is going to go back to stock too or is it going to remain the same as the custom rom one?
Click to expand...
Click to collapse
If you use the odin file the kernal and modem will revert back to stock.
Akalon said:
If you use the odin file the kernal and modem will revert back to stock.
Click to expand...
Click to collapse
Thanks. So im assuming now that the only time my kernel and modem wont go back to stock is when i flash with CWM. correct?
I haven't tried using the CWM file in that link so I'm not sure if it contains the kernel and modem. As far as custom roms go most if not all come packaged with the kernel and modem of choice.
So.. When I do a "master clear" from http://forum.xda-developers.com/showthread.php?t=731989...
Would everything be wiped? I read somewhere that when you do a "wipe" from your settings it only clears user settings or something. What would a "wipe"
from the recovery menu do?
I flashed to a different rom today thinking it will help my battery issue. When i am flashing from one rom to the next, i do a restore back to my backup before i flash to a new rom. Is this the correct method? or am i supposed to wipe beforehand? The reason i ask is because this is my 2nd rom and my battery issue still seems to be there. I tried other methods of fixing hte battery but nothign seems to work. When i looked into root explorer, i see that there are a lot more files now everywhere, than when i first started. would some of them be from my previous rom? if so how do i remove them?
Hi, Is there any one suceeded to downgrade from leak Jb 4.1 to ICS 4.0.4??
If yes could some one make video or provide step by step procedure.
There is no thread related to downgrade from leak jb 4.1 to ICS 4.0.4
even though many claimed they suceeded to downgrade.
Thanks
amritn said:
Hi, Is there any one suceeded to downgrade from leak Jb 4.1 to ICS 4.0.4??
If yes could some one make video or provide step by step procedure.
There is no thread related to downgrade from leak jb 4.1 to ICS 4.0.4
even though many claimed they suceeded to downgrade.
Thanks
Click to expand...
Click to collapse
I have. You will have to download the correct file from here . (if your phone is Asia retail like mine , download the 2nd one in the list)
Flashing is the same way you did the JB leak. It's via RSD, put the phone in fastboot and flash via RSD.
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Lifehacker7 said:
I have. You will have to download the correct file from here . (if your phone is Asia retail like mine , download the 2nd one in the list)
Flashing is the same way you did the JB leak. It's via RSD, put the phone in fastboot and flash via RSD.
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
My second and last question is( bear with me it's some how long)
1 I was previously in gingerbread 2.3.6,( the phone was asia retail), I flashed directly from gingerbread to jb leak 4.1.
Everything seemed ok and it passed RSD and the phone booted but stuck in motrolla splash screen ( kinda soft brick),
There was error in my lappy running window 7 64bit , mtp usb drive failed to instal(In device manager when i tried to update mtp usb driver it said
newer version of driver already installed),
Now a second scenerio starts Being in softbrick I tried to downgrade from jb to ICS, every firmware except those written with fastboot p3( I guess only chinese version) can be flashed through RSD , otherwise if fimware like 6.7.2 ------mearet or 6.7.2 ------ searet when flashed failed with error in step 4 in rsd like it shows rebooting in bootloader and shows failed error. So my point is only chines firmware with fastboot p3 can be flashed easily. Now I flashed both chinese and hongkong ICS firmware with title fastboot p3-------, and they both flashed correctly and passed but same things happened as jb leak, stuck in M logo and mtp usb driver failed error in my lappy.
Now my last option to fully boot was to go to gingerbread , so I downloaded couple of stock rom like 5.5.1 edem-27searet, it didnot flashed and got error with rebooting bootloader in step 4 or 5. At last I tried fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-180-EDS-20-31-release-keys-ChinaRetail-CN_chn.tar and it booted properly.
Now again I tried two times to go to ICS or jb leak and samething happened, stuck in M logo. But gb firmware always booted properly.
Please read above scenario before replying, because I haven't seen such situation in the whole xda thread for atrix 2 and by googling, Everyone flashed the rom and they said booted properly
My questions are
1 I want to flash jb leak rom or otherwise ICS, what will be my step?? I'm desperate to try these roms. Please keep in mind about my above situation as i'm unable to flash like other people do.
2 Why the above situation happening like softbrick while upgrading and why other firmware file are not flashing except titled with fastboot? Is it related to kernel or bootloader. When I was in xperia S when I updated from gb to ics same scenario occured but i tackeled situation by flashing in kernel. When I was in AT&T Infuse 4g, I tacked the above situation by upgrading from froyo to gb by updating from froyo bootloader to gb one.
But situation about atrix 2 just blow my head, I'm trying from 4 days, read every thread of xda related to atrix 2 , atrix 4g, googled for solution, watched video from youtube, tried every firmware but none solved my problem .
So waiting for solution from my senior XDA's
Thanks
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Lifehacker7 said:
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
Thanks for ur fastest reply
1 True i know our bootloader is locked
2 If we aren't how we can flash chinese firmware on our set?
3 True
4 True At&T firmware can't be flashed on or model and vice versa
5 As per ur question gb version which i can boot is 2.3.6 and the firmware i Flashed is fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
6 Can I take OTA ICS even though my set was not previously in Chinese firmware out of box. By luck or unluck I'm now settled in chinese firmware
7 Now last question is can i go directly to Angeeks jb 4.1 firmware posted in the thread.
Once again thanks :good:
2 I
Lifehacker7 said:
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
A small correction.. If you have a retail phone, you can flash any region firmware as long as it is for this phone. Just don't flash att ones. The radio is different and your phones cdt security number will be increased if you do.
Regarding flashing jb leak, how long did you wait after flashing? First boot usually takes long..
Sent from my MB865 using Tapatalk 2
Ravikirancg said:
A small correction.. If you have a retail phone, you can flash any region firmware as long as it is for this phone. Just don't flash att ones. The radio is different and your phones cdt security number will be increased if you do.
Regarding flashing jb leak, how long did you wait after flashing? First boot usually takes long..
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
About 30 minutes after flashing
More update I Flashed ics hk firmware, and this time it showed android is upgrading 1of 30, then passed 30/30 and then freezed for 25 minutes.
So after waiting for 20 minutes and stuck in android is upgrading I took out the battery and entered into recovery and did factory reset and wipe cached.
Now this time no android is upgrading message came up and stuck in M logo
To try any of the ROMs available ( except the gb ones, official jb leak, and one or 2 ROMs based on that) you should be on an ICS base ( they are built based on the ics kernel).
And to try the angeeks jb ROM, you should be on the JB leak 1st.
ROMs like PA, CM10, 10.1, they all need ics as base.
If nothing is really working out, you should probably give the phone to service station.( tell some lie about how that happened )
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Ok, so... there is a major issue going on here.
You flashed the HK/TW firmware on an international MEARET or SEARET phone, the HK or TW firmware is very much like the AT&T versions and that they lock the bootloader version so that upgrading or downgrading and changing firmware regions are blocked for the most part. There is a file in all the firmware version that tells RSD and the phone if it can or can not flash things... the one everyone knows is the CDT.bin, and the one that not everyone knows about is the CID, and the CID can get you into BIG trouble if you do not know what it is, or why it is there, so DO NOT mess with it, unless you know what you are doing... The CDT.bin on the other hand is part of EVERY FXZ, it will tell RSD if you can flash something for the most part or not.
Your ONLY chance is to flash your PROPER version of ICS firmware through fastboot commands. I will not give directions again, they are posted in several threads in here, do a search in the general section for the commands.... you MUST flash all the same files that RSD lite would to make this work, and you can no skip any of them. I would look for the order and the files to flash in the .xml file that comes with the firmware so that you know the order and partition names and such.
You MUST have the following and at the latest versions, even if you have the drivers installed, uninstall them and reinstall them again.
1) A2 moto drivers
2) Android SDK
3) moto-fastboot command/utility for your operating system
4) The PROPER ICS FXZ file for your phone and region
5) understanding of the comand line and the commands that are needed to flash with the moto-fastboot utility
After you have done all of that flashing, you should be on the proper ICS for your region. If you want to try and do the JB leak again, then it MIGHT, work, but I am not sure if it will or not.
It is a real bad idea to flash other regions firmwares to your phone, unless they are leaks, and have been tested to work on your regions handset, just for future reference.
jimbridgman said:
Ok, so... there is a major issue going on here.
You flashed the HK/TW firmware on an international MEARET or SEARET phone, the HK or TW firmware is very much like the AT&T versions and that they lock the bootloader version so that upgrading or downgrading and changing firmware regions are blocked for the most part. There is a file in all the firmware version that tells RSD and the phone if it can or can not flash things... the one everyone knows is the CDT.bin, and the one that not everyone knows about is the CID, and the CID can get you into BIG trouble if you do not know what it is, or why it is there, so DO NOT mess with it, unless you know what you are doing... The CDT.bin on the other hand is part of EVERY FXZ, it will tell RSD if you can flash something for the most part or not.
Your ONLY chance is to flash your PROPER version of ICS firmware through fastboot commands. I will not give directions again, they are posted in several threads in here, do a search in the general section for the commands.... you MUST flash all the same files that RSD lite would to make this work, and you can no skip any of them. I would look for the order and the files to flash in the .xml file that comes with the firmware so that you know the order and partition names and such.
You MUST have the following and at the latest versions, even if you have the drivers installed, uninstall them and reinstall them again.
1) A2 moto drivers
2) Android SDK
3) moto-fastboot command/utility for your operating system
4) The PROPER ICS FXZ file for your phone and region
5) understanding of the comand line and the commands that are needed to flash with the moto-fastboot utility
After you have done all of that flashing, you should be on the proper ICS for your region. If you want to try and do the JB leak again, then it MIGHT, work, but I am not sure if it will or not.
It is a real bad idea to flash other regions firmwares to your phone, unless they are leaks, and have been tested to work on your regions handset, just for future reference.
Click to expand...
Click to collapse
Thanks jim for the gr8 info,
Would you recommend me for OTA update to Ics from here? It's saying update available
Do my mobile boot in this scenario?
Any consequences taking OTA.
Thanks again for help
amritn said:
Thanks jim for the gr8 info,
Would you recommend me for OTA update to Ics from here? It's saying update available
Do my mobile boot in this scenario?
Any consequences taking OTA.
Thanks again for help
Click to expand...
Click to collapse
I would not take any OTA, since we have FXZ files that are properly made for the regions our phones are made for, if you know what I mean. The only difference is that an FXZ will wipe your phone clean and you have to resync with google for calandar and e-mail and contacts and apps and such.
With out knowing the EXACT firmware you are on right now, I can not really tell you how safe an OTA or an FXZ will be for you. I am only guessing at this point, that you are still on the HK/TW firmware, and why I suggested you flash the MEARET/SEARET firmware by hand with the moto-fastboot commands, to get you where you should be again, before you try the JB leak, or whatever you are after.
Need to make decision!
Hi guys!
For first, sorry for my bad english. I hope you can understand me. Greeting from Belarus!
I have ME865 with United Arab Emirates warranty.
I flashed my Atrix 2 from 2.3.6 to 4.0.4 6.7.2_EDEM-18-MEARET. It worked fine.
Then I flashed official 4.1.2 leak, rooted it.
Which region firmware I need choose to success downgrade from 4.1.2 to 4.0.4?
Really need your answer! Thanks!
I have some bugs on JB:
1. Can't send and recieve mms.
2. APN dissapear after every reboot. Fix - after reboot turn on/off airplane mode.
3. Bad GPS. Fix - install GpsFix app.
4. Recieve USSD message with sound.
_________________________________________
Just had flash 4.0.4 mearet. All works.
jimbridgman said:
I would not take any OTA, since we have FXZ files that are properly made for the regions our phones are made for, if you know what I mean. The only difference is that an FXZ will wipe your phone clean and you have to resync with google for calandar and e-mail and contacts and apps and such.
With out knowing the EXACT firmware you are on right now, I can not really tell you how safe an OTA or an FXZ will be for you. I am only guessing at this point, that you are still on the HK/TW firmware, and why I suggested you flash the MEARET/SEARET firmware by hand with the moto-fastboot commands, to get you where you should be again, before you try the JB leak, or whatever you are after.
Click to expand...
Click to collapse
As per your question jim I'm currently in android version 2.3.6
system version 55.91.109.ME865.ChinaRetail.en.CN
Model number ME865
build number 5.5.1-1_GC-109
Kernel version 2.6.35.7-g8b6f7f9
[email protected]#1
And I flashed this firmware to get fully boot fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
-Also tried different firmware like jb 4.1 leak flashed passed booted but stuck in M logo splash screen.
-Flashed both ICS build from china and hk/tw and stuck in M logo as in jb
-Tried searet and Mearet firmware for both ICS and Gb build but failed after 5/21 rebooting to bootloader and failed
-And at last I tried fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar passed and booted.
Jim What will be my next move??
Can I try fast boot method as u mentioned or OTA update to ICS
Thanks
amritn said:
As per your question jim I'm currently in android version 2.3.6
system version 55.91.109.ME865.ChinaRetail.en.CN
Model number ME865
build number 5.5.1-1_GC-109
Kernel version 2.6.35.7-g8b6f7f9
[email protected]#1
And I flashed this firmware to get fully boot fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
-Also tried different firmware like jb 4.1 leak flashed passed booted but stuck in M logo splash screen.
-Flashed both ICS build from china and hk/tw and stuck in M logo as in jb
-Tried searet and Mearet firmware for both ICS and Gb build but failed after 5/21 rebooting to bootloader and failed
-And at last I tried fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar passed and booted.
Jim What will be my next move??
Can I try fast boot method as u mentioned or OTA update to ICS
Thanks
Click to expand...
Click to collapse
But you are supposed to be on SEARET/MEARET as your "real" "home" firmware, correct?
If you are supposed to be on SEARET/MEARET, then I would go here, and grab the ICS FXZ file for the SEARET/MEARET firmware, and use the fastboot commands to try and flash it. As always there is no guarantee, and there is always a chance of brick so be careful.
The reason I am really pushing for using the fastboot commands, as I mentioned earlier, that since you are "manually" flashing the parttitions one at a time, from the command line, there will be no checks to see if the proper CDT.bin is on the phone before it does it, and this will save you, in that you should be able to put your "correct" firmware on the phone, I hope.
I have one last question, are you 100% sure that you actually purchased an international MEARET/SEARET phone, and not an HK/TW version of the phone? This is just a thought, since you did say that you were unable to flash any firmware besides the ME865 china HK/TW version... which does bring up that concern.
jimbridgman said:
But you are supposed to be on SEARET/MEARET as your "real" "home" firmware, correct?
If you are supposed to be on SEARET/MEARET, then I would go here, and grab the ICS FXZ file for the SEARET/MEARET firmware, and use the fastboot commands to try and flash it. As always there is no guarantee, and there is always a chance of brick so be careful.
The reason I am really pushing for using the fastboot commands, as I mentioned earlier, that since you are "manually" flashing the parttitions one at a time, from the command line, there will be no checks to see if the proper CDT.bin is on the phone before it does it, and this will save you, in that you should be able to put your "correct" firmware on the phone, I hope.
I have one last question, are you 100% sure that you actually purchased an international MEARET/SEARET phone, and not an HK/TW version of the phone? This is just a thought, since you did say that you were unable to flash any firmware besides the ME865 china HK/TW version... which does bring up that concern.
Click to expand...
Click to collapse
Jim You are genious, Now with fastboot command i'm in the stage where I was 4 days ago pure stock. The firmware which didnot flashed through RSD , flashed with fastboot commands. But with fastboot commands moto-fastboot.exe flash grfs grfs.img, showed error as failed no such partitions. But even without that i'm now booted in stock Sereat gingerbread firmware. Now I will flash ICS firmware through fastboot and will update if anything goes wrong wrong or write
Thank u:good:
Update whatever I do I get stuck in splash screen or M logo after flashing ICS fxz file or Jb file using any method either fastboot
or RSD even though i'm fully stock now 2.3.6 sereat
amritn said:
Update whatever I do I get stuck in splash screen or M logo after flashing ICS fxz file or Jb file using any method either fastboot
or RSD even though i'm fully stock now 2.3.6 sereat
Click to expand...
Click to collapse
Make sure you are getting your FXZ files from a well known good source.
This is the best one:
http://sbf.droid-developers.org/edison/list.php
Try and flash the ICS one, I think it is this one, that you want:
http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Try it with RSD lite version 6+ ONLY, then if that does not work, try it with the fastboot commands again.
You should not try and flash the p3 files, until you get to ICS first. I think it all has to do with the bootloader versions, and why you can not go from GB to JB. You have to go to ICS then JB, I am pretty sure of that.
jimbridgman said:
Make sure you are getting your FXZ files from a well known good source.
This is the best one:
http://sbf.droid-developers.org/edison/list.php
Try and flash the ICS one, I think it is this one, that you want:
http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Try it with RSD lite version 6+ ONLY, then if that does not work, try it with the fastboot commands again.
You should not try and flash the p3 files, until you get to ICS first. I think it all has to do with the bootloader versions, and why you can not go from GB to JB. You have to go to ICS then JB, I am pretty sure of that.
Click to expand...
Click to collapse
Jim no matter what I do i cannot upgrade my firmwawre either to ICS or jellybean, Always stuck Im motrolla splash screen at the last stage of boot. But if i return to gingerbread on both chinese and asian retail(using fastboot or RSD) it's working.I've tried everything. It's out of my mind now.
There is something that is causing my mobile not to boot. If u do have any idea, please help me.
Apart from that I want to know do we have ICS stock kernel in zip format which we can flash?
If other ppl had same problem and solved it pls share with me. This seems something new, softbrick in ICS everytime no matter which region firmware i flash apart from AT&T firmware. I'm trying since 5 days.
Pls reply xda senior member or anyone those in similar case.
amritn said:
Jim no matter what I do i cannot upgrade my firmwawre either to ICS or jellybean, Always stuck Im motrolla splash screen at the last stage of boot. But if i return to gingerbread on both chinese and asian retail(using fastboot or RSD) it's working.I've tried everything. It's out of my mind now.
There is something that is causing my mobile not to boot. If u do have any idea, please help me.
Apart from that I want to know do we have ICS stock kernel in zip format which we can flash?
If other ppl had same problem and solved it pls share with me. This seems something new, softbrick in ICS everytime no matter which region firmware i flash apart from AT&T firmware. I'm trying since 5 days.
Click to expand...
Click to collapse
get it done from moto service center
Sent from my ME865 using xda premium
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.
Hello co-A510 users,
I've been lurking for quite a while and I repeatedly see questions about "how to get the JB bootloader?". Followed by the answer "Go back to stock ICS, then get the OTA.". Usually followed by the follow-up question "B-b-but... how?"
This post attempts to answer that follow-up question, for most folks, in the easiest way possible.
The Six Steps to Stock:
Step 1: Download the Stock Acer OS (rom zip)
- Go to http://www.acer.com.au/ac/en/AU/content/drivers
- Select Tablet >> Iconia A >> A510 in the product list
- On the new web portion that will appear, select the "O.S." tab, and download your appropriate build (mine is WW.GEN 1)
Step 2: Flash the OS (rom zip)
- Save the zip in your SD card
- Enter your custom recovery, and flash it
- After the successful flash, reboot your system
- CWM will ask you if you want to keep your custom recovery, say NO. Remember, you want to go back to stock. So let the zip do it's job
Step 3: Check your System Date and Time
- Once booted, make sure that your date and time (time zone included) is correct.
Step 4: Check for System Updates
- Go to Settings >> About Tablet >> System Update >> Check now
Step 5: Wait
- If a pop-up is saying that you're on the latest version, try again at a later time.
- If there's no pop-up saying you're on the latest version, wait. It's a 252MB JB rom downloading in the background.
Step 6: OTA Update
- Once the JB zip is downloaded, a pop-up will say "Install Later, More details, Install Now"
- Select Install Now
- After a few familiar windows, you will now be on the JB recovery, and the JB rom. Ready for the adventure ahead.
This is nice, but a little info regarding why installing JB bootloader would be nice (if I remember correctly one of the things is to reduce the screen flicker, but that's what I THINK), and also how to root and get back in custom ROM road
Oh, and also, is there a way to know what verion of tab we have if we're already on custom ROM?
Lusanagi said:
This is nice, but a little info regarding why installing JB bootloader would be nice (if I remember correctly one of the things is to reduce the screen flicker, but that's what I THINK), and also how to root and get back in custom ROM road
Oh, and also, is there a way to know what verion of tab we have if we're already on custom ROM?
Click to expand...
Click to collapse
The main reason that you would want to have the JB bootloader, is to fix the audio stutter bug of the ICS bootloader.
(If you're on the ICS bootloader, play some music files, then turn your screen off. The CPU throttles down to the point of slowing down your music player.)
About how to root JB, I think it should deserve it's own thread. I simply follow the one here, it's pretty complete already (I rooted my stock JB just an hour ago):
http://forum.xda-developers.com/showthread.php?p=35907925#post35907925
And yes, whatever ROM you are on, you almost always have the settings >> about phone menu.
what I meant was get the appropriate build (either WW.GEN 1 or AAP.AU2); I did enter About Phone, but wasn't able to find any of that data (obviously)
Lusanagi said:
what I meant was get the appropriate build (either WW.GEN 1 or AAP.AU2); I did enter About Phone, but wasn't able to find any of that data (obviously)
Click to expand...
Click to collapse
Ah... good point. What I personally did was to restore my nandroid back-up from my stock image.
As an alternative, I would say flash NoThrills' optimized WW Gen1 rom. However, I do admit that it is something that I never tried as base. And it's a "do it at your own risk" thing.
Firmware version 1.073 A510 ICS
After flashing you will have stock firmware 1.73.00 WW GEN with closed bootloader.
Flash the fastboot mode (with unlock bootloader).
Run the restore.bat in the extracted archive folder.
After flashing tablet upgraded to firmware version AV051_A510_1.034.00_WW_GEN1 by OTA.
First post in 4PDA
Sorry for my english .. :cyclops:
salisbury_steak said:
Hello co-A510 users,
I've been lurking for quite a while and I repeatedly see questions about "how to get the JB bootloader?". Followed by the answer "Go back to stock ICS, then get the OTA.". Usually followed by the follow-up question "B-b-but... how?"
This post attempts to answer that follow-up question, for most folks, in the easiest way possible.
The Six Steps to Stock:
Step 1: Download the Stock Acer OS (rom zip)
- Go to http://www.acer.com.au/ac/en/AU/content/drivers
- Select Tablet >> Iconia A >> A510 in the product list
- On the new web portion that will appear, select the "O.S." tab, and download your appropriate build (mine is WW.GEN 1)
Step 2: Flash the OS (rom zip)
- Save the zip in your SD card
- Enter your custom recovery, and flash it
- After the successful flash, reboot your system
- CWM will ask you if you want to keep your custom recovery, say NO. Remember, you want to go back to stock. So let the zip do it's job
Step 3: Check your System Date and Time
- Once booted, make sure that your date and time (time zone included) is correct.
Step 4: Check for System Updates
- Go to Settings >> About Tablet >> System Update >> Check now
Step 5: Wait
- If a pop-up is saying that you're on the latest version, try again at a later time.
- If there's no pop-up saying you're on the latest version, wait. It's a 252MB JB rom downloading in the background.
Step 6: OTA Update
- Once the JB zip is downloaded, a pop-up will say "Install Later, More details, Install Now"
- Select Install Now
- After a few familiar windows, you will now be on the JB recovery, and the JB rom. Ready for the adventure ahead.
Click to expand...
Click to collapse
Hi,
I'm keen to update my bootloader, and have been trying to get it done for a while now.
However, i got stuck while following your instructions... at the beginning already!
At that url you quoted, there are only UPDATE files. They won't work, tried already. Those need you to have stock rom.
Where can you get a real stock rom zip?
Thanks!
.A.
Sent from my LG-D802 using XDA Free mobile app
Hi.
I am trying to get stock jb Rom on my 511 (sorry, i know 510 is in the threat).
Cwm 6.0.4.5, jb bootloader, cm11 and rooted. Full wiped and formated.
Downloaded 4.0 from Acer, edited update.zip 1. line ond got cwm error 7 device probably encrypred.
Tried same with 4.1 from Acer and got cwm error too.
Dont know what to do now?
Could anyone provide help?
Update.............
Now i am on ics, but ota updates could not be downloaded because of unstable network. Flashing update.zip via sd ends in red android logo (tried editing 1st line) after 1/3 progress?
DAMN...
I must search a little bit under my old account (because I've forgotten sometimes the username
Pls gave a look here
http://forum.xda-developers.com/showthread.php?t=2046832
Any idea how to solve this? http://i83.photobucket.com/albums/j293/socalrailroader/IMG_20120430_012752.jpg
x4x3 said:
Sent from my LG-D802 using XDA Free mobile app
Hi.
I am trying to get stock jb Rom on my 511 (sorry, i know 510 is in the threat).
Cwm 6.0.4.5, jb bootloader, cm11 and rooted. Full wiped and formated.
Downloaded 4.0 from Acer, edited update.zip 1. line ond got cwm error 7 device probably encrypred.
Tried same with 4.1 from Acer and got cwm error too.
Dont know what to do now?
Could anyone provide help?
Update.............
Now i am on ics, but ota updates could not be downloaded because of unstable network. Flashing update.zip via sd ends in red android logo (tried editing 1st line) after 1/3 progress?
DAMN...
Click to expand...
Click to collapse
monacoo said:
Any idea how to solve this? http://i83.photobucket.com/albums/j293/socalrailroader/IMG_20120430_012752.jpg
Click to expand...
Click to collapse
Hi both of you, I know I am terribly late, but I have basically the same problem.
I wanted to go back to the latest stock version because I am selling the tablet.
Before I had all kinds of CM and then NoThrills and wanted to go completely stock.
I managed to get 4.0/ICS with all Stock options, but I couldn't find a way to upgrade to JB with any "official" method.
The standard OTA search says "Unstable network connection" and the SD card update.zip ends with the red triangle robot.
Personally the journey is at an end for me, since I don't care, it will stay on ICS.
Maybe one has to fiddle with the bootloader lock/unlock, but I am tired of it.
Sorry for not being helpful, just saying I have the exact same problem.