Related
Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
try this: http://forum.xda-developers.com/showthread.php?t=867617
There are others like it too. Just don't try flashing the bootloader or sbl !
AbsoluteZero said:
Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
Click to expand...
Click to collapse
Gin's got you on the right path for sure. A couple more items for you:
This post should help with removing the AT&T bootup logo: http://forum.xda-developers.com/showthread.php?t=849789
If you use Heimdall to flash the Rogers stock firmware that is in the post the Gin linked to then you will absolutely need to follow the instructions to use the Heimdall drivers for your captivate when it's connected or it won't see the device when you tell it to start. Like gin said, don't touch primary or secondary bootloader, leave those out and don't try to repartition it.
Restoring the stock firmware will remove the custom kernel that is installed with Cognition (at least it should) and so the Clockwork recovery should no longer be installed once the restore to stock is done. You can double-check once you are back to stock by powering off the phone and then hold both up and down volume + power, let the power button go after it restarts once and you see the I896 for the 2nd time. It should take you to the stock 2e recovery screen. If it does, you should be golden.
HTH
Wow, thanks all,
I used that method without the PIT file,
I just want to say thanks to everyone that offered help,
Goina try to send it for warranty now.
thanks again,
Joe / AZ
Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.
some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...
Sir, I have tried so, somehow, I did not have lucks other had.
roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
..... my bad
I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me
skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.
By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.
same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App
guys same problem here, help us
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Sounds like the wrong kernel for the Rom was flashed.
What rom/kernel were you trying to flash ?
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
So you are going to need to flash the kernel that goes with the holicakes 2.6.35.14 rom.
Should be on the same site.
You can user CMD to fastboot flash boot boot.img and then the rom will boot.
From what I can tell on the rom page there is a kernel download section.
---------------------------------
Looks like he is instructing you to flash the kernel a different way than I have listed above, but both ways will work.
Riomaru said:
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Click to expand...
Click to collapse
DO NOT TRY, FACTORY RESET WILL DO ABSOLUTELY NOTHING AND MIGHT ACTUALLY MAKE THINGS WORSE.
With that out of the way, don't use the AIO software, use fastboot.exe and flash a boot.img to fix the issue.
Riomaru said:
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
Click to expand...
Click to collapse
No need to worry, you haven't had enough experience to know that it is normal. It is normal for the phone to not boot into the rom when the kernel doesn't match. since you have successfully flashed the kernel, you now need to boot into recovery (which I hope you have it installed at this point, if you have not, read how to do it and flash recovery) once in recovery, proceed to flash the HoliRaider rom and you'll be good to go.
in the same boat
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
newbroman said:
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
Click to expand...
Click to collapse
Did you install a recovery?
Also, it was not a good idea to try and install all different types of things once you thought it was messed up. Anytime you think you may have messed up, stop right then, read about the issue, and if you can't find the solution, ask a question. I think you can get out of this but some people aren't that fortunate.
vivid white screen
Thanks for the advice I will press on and do some more reading,
I can still get to CWM recovery and have tried restoring the backup image I made, with the same result.
During the kernal flashing process:-
- is the HTC dev lock supposed to be on or off? It is off and unlocked at the moment,
- is double flashing the kernal what is meant by the instruction 'if this is the first time you flash a kernal, make sure to reflash it', or as is suggested in esloan's post on this thread your supposed to flash a matching rom instead?
Thanks
You did the right thing by flashing the kernel twice. That is what those directions said. After you flash the kernel twice the next step would have been to flash a rom. I believe it is better to use the fast boot commands for doing this entire process. It sounds like you are still on the holicakes kernel.
What recovery do you have? 5.5.4 or WCX Recovery? You will have better results with WCX Recovery. Also watch this video:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
That is by randog. He did a great video and he shows you how to install everything without a program. Do you have the holiradier rom on your phone?
I was on the CWM recovery.
Thanks for the link to Randog's video, I now have a working phone again.
The major difficulties I had was finding wildchild's webpage with the links shown on the video, mainly because searching for wildchild illuminati took me to a forum with no links to any thing vivid, until you register.
I was also a little worried that I wasn't getting ICS in the ATT_ generic rom, but I needn't have. The key seemed to be locking the phone again and running wildchild's PH39IMG.zip. After that the security warning on the Hboot screen disappeared.
I almost messed the rom flashing part. Randog's vivid does this really quickly, my phone was a good 3 minutes behind and the progress bar was stuck around the 10% way after his phone had finished.
Like Randog says in the video follow the steps and you wont brick and you'll have a working phone.
Thanks megatronisabeast
Glad you got it. Sorry, forgot to give out the link.
Sent from my HTC PH39100 using XDA
Afraid to screw up any further
Htc vivid. 1.2dualcore.ICS.*
unlocked boot loader.
Used all in one vivid *toolkit 2.1
http://forum.xda-developers.com/showthread.php?t=1498003.
There were two choices. After boot loader unlock, which I had already done. Using right reading logic, I went to the "next step". Didn't realize ICS meant ice cream sandwich. Dumbass. I used CWM 5.5.0.4. Then I tried to to update the kernel, to*Holicakes2.6.35.14. For some unknown reason. The result is the white screen of death.
.*
I have access to hboot. As well as the recover menu which has a backup and restore option.
NAND restore clockworkmod backup, is available. I'm not sure how proceed.*
At the bottom of the screen:*
RA Revamped
Build: made for the WCX ILLUMINATE SERIES by GINM
I studied quite a bit. Too dumb to get a clear picture of the necessary steps before I began, I guess. Again, what a Dumbass.
I *need a better understanding of the process.
I didn't know about the super guide until it was too late. Rather, I did not understand I had seen the super guide when I saw it. It was from December, called a Holliday guide, so I didn't read it. There were so many guides, it confused me pretty throughly. Sheesh.
I have the htc white screen, reboots every three minutes or so.
I would really appreciate someone who knows to give me some clarification on these issues.
I understand a lot of these issues have been dealt with in this thread. I'm just really apprehensive.
I hope I posted this in the right place.
Thanks in advance,
Microbot2
Microbot, you have done pretty much what I did. If you follow megatronis a Brady's advice you will have a working phone. In fact I'm using it right now. Use the generic att zip an you will have ICS less the ATT bloatware.
Okay mircobot, I am home and can help you. Here is what you should do:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
Watch that video. Shows you what you will need to do to get everything working again.
The next thing, you need to download all of the files you will need for getting your phone working again. I would recommend going here:
http://www.wcxxperia-nce.com/index.php
You will have to register to see the vivid forums.
Next decide if you want to be able to tether (generic build) or if you want stock based rom (ATT vivid ics).
Download the zip file. Follow the instructions in the video and should get you up and running in no time. That would be the easiest way in my opinion.
If you can't get it figured out or need more help just post here and we will try to assist.
Microbot2--vivid
Hey guys, thanks for the prompt reply's and your general bad-assness.
I just woke and will Start on the instructions.
Megatronisabeast, really appreciate it. Newbroman, thank you.
I already feel considerably less worried about this already. I'll let you know how it works out.
microbot2_no PH39img.zip
Note: I updated to ICS from att before I unlocked the bootloader, which is still locked as now the phone can't be seen by the program.
Megatronisabeast, thanks for the link to the video. I am a little closer to understanding now. Unfortunately, I don't have direct access to the internal storage, like the guy in the video did. and I couldn't discern the website URL and he never tells you directly, except for "goto wildchilds site" which i couldn't locate.
I now know that I have access to wildchildes recovery. Unfortunately, I can only see the internal storage if I use WC recovery, ("windows wants to format it") then goto USB-MS. Otherwise the computers don't see it when its plugged up. It says "device not found when I try to do something in AIO_toolkit 1.2 Don't know if that helps.
I did find the wcxrecovery.img
It appears that you have to have access to internal storage to load an image to it. PH39img.zip, which I don't have. I can't seem to find the wildchild ICS image, either. when I start my phone, it looks for the ph39img.zip, doesn't see it, goes to the white screen.
I don't understand how to get the image back,Rather, how to access the internal storage again. is PH39img is the same thing as the ROM? Do I have to load PH39IMG.zip and the wilchild_vivid_ICS.ROM, which, again, I can't seem to find.
This feels like a comedy of errors. I wish I would have studied longer. I usually do. THEN, I find "newbie_proof" all in one toolkit.
I Just wanted it rooted. All I had to do was click "root" instead of "kernel". Man, what was I thinking?
If only I had taken the Red Pill.
Thanks again,
Look at my post above, the link for wild Childs site is there. You have to register to see the vivid forums. That is also where you will download the files needed to set up the ROM, etc. You won't need the Ph39.img since you already have ics. That is for the bootloader. You can actually send a file to your phone in the recovery. since you already have recovery you would need to download the Android sdk tools, so you will have fastboot. You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery. Sorry these directions aren't better, I will try to assist more when I get home, Swyping right now.
Sent from my HTC PH39100 using XDA
Microbot,
The wildchild files you need are in the first link Megatronisabeast cites
wcxxperia-nce.com/index.php (I'm a newbie and cant post the full web address). You have to sign up to the forum to access the files. The vivid forum will appear once you have registered.
The PH391IMG.zip is not your normal PH39img.zip you have to use the one contained in the WCX_generic_ATT.zip on the WCX vivid forum page. You also need to relock the phone. You are probably better off using the fastboot and the windows command prompt for this.
Can you boot into recovery at all?
Do you have another phone? you could use that to copy the PH39img.zip over. Thats what I did.
Mcrobot2---
Hi guys,*
Here is what I think I know:
HBOOT is a bootloader, *like a BIOS.
PH39img.zip is the boot file. Like PH39IMG.zip which appears to be a modified version for WC.
Kernel *is the memory and CPU manager.
ROM is an operating system package, or file placed onto the erasable/programmable part of the phones memory. NAND, I think.
S-OFF/ON *is a security check.
.Apk: compressed java file.
.Jar: *java application file.
.odex *files: helper files with most relevant information to compile and run the concerned application as fast as possible, a JIT Kind of thing.
----
I was able to relock bootloader, Yea!
Thanks megatronisabeast and newbroman.
--history--I updated to ICS from AT&T.
I thought I could skip reading for another three weeks because of newbie-proof AIO 2.1. * wrong!
I wanted to root my phone. *I had unlocked the bootloader with htcdev.*
Found hasoons all in one vivid 1.2. Used WC's recovery. I then flashed with hollicakes kernel, twice. Wsod.
--
Megatronisabeast:*
You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery.
-I'm not sure the exact boot img,*
- I think the zip file would be the rom?
Getting closer.
Thanks again guys. I'm feeling a little thick lately. Like freshman year of college! Weed out classes.
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
apefist said:
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
Click to expand...
Click to collapse
Do you have a sim card in the phone? This was an issue with some Jellybean/ICS roms. It happens to me as well. For some reason when placing a sim card in the phone(it doesn't need to be active) it allows your phone to get reception.
pandam00nium said:
Do you have a sim card in the phone? This was an issue with some Jellybean/ICS roms. It happens to me as well. For some reason when placing a sim card in the phone(it doesn't need to be active) it allows your phone to get reception.
Click to expand...
Click to collapse
Hey,
So this actually worked, thanks for the heads up!
step by step
apefist said:
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
Click to expand...
Click to collapse
Hey, Glad u got your issue resolved..
i am getting my first Android phone (Droid 3 XT862 Gingerbread 2.3 ) and i want to install a custom rom the same way u have..... i was wondering if you or anyone else on the forum could give me step by step guide on how to go about installing the custom rom with the ability to revert back to my original stock OS wen i need to......
i had posted a thread here http://forum.xda-developers.com/showthread.php?t=2378162 and i got some good advise so far:
you or anyone here could reply with the instructions i need or at least send me a link to a tutorial .... as i said this is my first Android so i really dont want to make any mistakes while doing this..
THANX MUCH !!!!!!!
Tha slayer said:
Hey, Glad u got your issue resolved..
i am getting my first Android phone (Droid 3 XT862 Gingerbread 2.3 ) and i want to install a custom rom the same way u have..... i was wondering if you or anyone else on the forum could give me step by step guide on how to go about installing the custom rom with the ability to revert back to my original stock OS wen i need to......
i had posted a thread here http://forum.xda-developers.com/showthread.php?t=2378162 and i got some good advise so far:
you or anyone here could reply with the instructions i need or at least send me a link to a tutorial .... as i said this is my first Android so i really dont want to make any mistakes while doing this..
THANX MUCH !!!!!!!
Click to expand...
Click to collapse
Hey, so this was my process.
First, I made sure that the stock software on the phone was up to date. I did this since that way if you have to go back to stock, you are on the latest version, and you can confirm that you are using the correct rooting application. The root tool I link to below will work on 5.7.906 which I believe is the latest.
Second, root your phone. You will need to go HERE to download the tool. Follow the instructions on the page, and it should go fine. The phone will reboot several times during the process, this is normal. Once the program says it is done, you can go check for the Superuser application in your app drawer (it might be SuperSU or something similar, I can't quite remember).
After you have root access on your phone download the safestrap application for Droid 3 HERE. Make sure you get the one that is specifically for Droid 3. Transfer that file (should be called Droid3Safestrap-3.05.apk) onto your phone.
There are a few ways to transfer files onto your phone. You will also need to do this later to transfer the .zip of whatever ROM you decide on). If you have a micro-sd card that you can put into your computer, that works. Or, you can have the phone on and plug it into the computer and transfer it that way. I believe you can transfer to either the micro SD or the internal memory. I prefer micro SD since you might want to wipe the internal memory to fix things or switch ROMs.
After the .apk is transferred find where you put it using a file manager (I personally use Root Explorer but I think Astro or stock will work), and install it. Go to the new app and run it and it should request root access, which you grant, and it should flash the recovery.
Once you have the recovery installed you can install whatever custom ROM you want, pretty easily. Safestrap is great because even if you screw up the ROM somehow, you can always just boot back into Stock.
Here is where you'll have to chose what custom ROM you want. Now as far as I know, the Droid 3 is fairly limited in its ROM selection. It does have a Cyanogen Mod 10 version, but it is not a stable version and in my experience, doesn't run super great. If you want to try Cyanogen Mod 10, I actually suggest you get the Avatar Rom variant HERE, but keep in mind that apparently you do need a SIM card inserted for the cell signal to work at all. Overall it did seem to run fairly choppy but they are still releasing newer nightly versions (July 20th was the last) so it might have gotten better. One thing to know about these ones is that the camera does not work at all, so if that matters to you just skip these.
Now those two (CM 10 and avatar) are ROMS that will bring the droid 3 up to Android 4.2 Jellybean. If you don't care about getting up to the latest version (Jellybean actually isn't the latest anymore but still pretty darn close), then there are a few other Gingerbread ROMS out there that work a bit better.
HERE is a list of a few other droid 3 ROMs, my favorite Gingerbread one that worked overall really well and stable was Steel Droid. Otherwise, you can just look around and see what's available or what other people are suggesting. Choose your ROM (or several, it's fairly easy to install them so try a few!), and download it. You should get a .zip that is approx. 150-170 MB in size. As an aside you will probably also want to download the corresponding GApps package HERE and put that on the SD card as well. I think some ROMs have that included, but if you boot into a room and it doesn't have the Play store installed, you need to go back into safestrap and install the GApps package over it. You don't have to delete and recreate the rom slot, just go back into install and install it over. When I say corresponding, the different packages go with different versions of Android so for example the one labelled 20110307 would go with Android 2.3.4 which is Gingerbread, the version that Steel Droid uses.
For whichever one you choose, the install process is mostly the same. Reboot your phone, and after the Motorola Logo comes up, you should see the Safestrap splash screen. To get into the recovery menu you have to hit the "Menu" soft-key (the one all the way on the left) within 10 seconds so keep an eye on it.
From the recovery menu go into "Boot Options" You should see 5 options, rom-slot 1-4 and Stock. When you want to switch what ROM you are booting you select on the corresponding slot, and hit activate, then you can reboot through the menu option and it will start that ROM.
To install you will go into "Boot Options" chose whichever rom slot you want (most likely #1). You will have to create that slot, which can take a few minutes. After the slot is created, back out of boot options, and go to "Install". Find the .zip of whichever ROM you chose, and select that to install, and then you can install the corresponding GApps package.
After the install is complete, you can reboot (make sure it says rom slot 1 is selected up to), and it should boot into the Setup process of the ROM. If you ever need to go back to stock, just reboot, go back into Safestrap > Boot options, activate the "Stock" one and boot into that.
A few notes, if you want to switch ROMs, or install multiple ROMs you can do that using the different rom slots with a few exceptions. The Cyanogen Mod 10 and the Avatar Rom (most Jelly bean ones I think) have to be installed in rom slot 1, so if you're doing those and another like Steel Droid, put the Jellybean one in rom slot 1 and the Gingerbread on in rom slot 2. Also if you want to install a different ROM, it's generally best to just completely erase the rom slot and recreate it, then install the different ROM in the newly created rom slot. You can always create backups with Safestrap and restore them with Safestrap. Oh and make sure your phone has a decent charge before doing a lot of the safestrap stuff (I would say at least 60%) you can also have the phone plugged in while doing this stuff, but I'm not always confident it is charging so try and get it charged up before hand.
Finally, if you ever mess up to the point where you're worried that you broke the phone, (boot loops or it is stuck on the Motorola Logo) you can download this restore tool HERE. This should completely wipe and restore the stock software on your phone. It will bring it back one version previous though, so be sure to go through the standard update process to bring it back to 5.7.906 so that the root tool will work. This tool has saved me a few times and is pretty easy to run.
Sorry, I know that is a lot of stuff and looks pretty scary. It really is just a few steps that you should research and make sure you are comfortable doing.
1: Get Root access on the stock software on the phone
2: Install safestrap and flash the custom recovery
3: Boot into recovery and install whichever custom ROM you want
If you have any questions feel free to ask!
Much appreciated !!! ..... i will try these steps as soon as i get my phone..... hope it doesnt make a difference if my D3 is an unlocked GSM phone because all service providers in my country uses GSM
Tha slayer said:
Much appreciated !!! ..... i will try these steps as soon as i get my phone..... hope it doesnt make a difference if my D3 is an unlocked GSM phone because all service providers in my country uses GSM
Click to expand...
Click to collapse
if you are using gms you may need Rom version with a modified build prop, most of the roms threads will have a modified version for GMS, in the OP or somewhere in the thread. if you can't find it just ask in the original rom thread
also some good how to videos here https://sites.google.com/site/tomsgt123/all-videos/videos-page-4
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.