Database Develop

Non-public froyo build updating issues

My phone is running build FRF33B (googling this build number returned no results at all). It was a non public build. I got the phone from Adobe as part of a (kongregate) promotion to get flash developers to edit some games so they could run on froyo, and hence I really don't know what was done to the phone before I got it (there's an unlocked symbol when it boots, and even though it's a t-mobile nexus I'm using it on AT&T's network).
FRF33B is nice and usable (but full of minor bugs which get irritating after a while), and I'd really like to update to the latest stable build, but it's not receiving any of the OTA updates, and trying to install any manually gives me a package signing verification failure.
Does anyone here know how I can update the phone? Do I need to downgrade it somehow? Do I need to root it? Any help would be appreciated.

Downgrade to erd79 would be my best suggestion and it will update to frf91 I hope that helps and if u need a update zip let me know and I can email it to u
Sent from my Nexus One using XDA App

Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.

Option 3: Search around for the FRF91 Universal update.zip, copy it to your SD card, and flash it via stock recovery.

rohandhruva said:
Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.
Click to expand...
Click to collapse
ok I've done this, and flashed the universal FRF91, now the phone is stuck on the animated X, is this normal? Do I just have to wait or did I do something wrong?
edit: it looks like it just rebooted itself.... still not getting past the animated x part though
edit: wiped the phone and tried again, now it works... got to set up everything on the phone again though and download my apps again... oh well. thanks for the help

nexus one to stock

how do i get my nexus one back to stock absolutely every like out of the box stock i ahve the T-Mo version

Download:
http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Extract it, rename the extracted file passimg.zip and copy to the root of the SD card.
Also download:
http://shipped-roms.com/shipped/Pas...RG83 OTA update, possibly from FRF91 too).zip
Rename it to update.zip and copy it to the root of yout SD card.
Power off the phone, hold Vol- and power on. It will boot to the bootloader, detect the passimg file and ask if you wish to install.
After it's done (I think it'll reboot itself, if not, select recovery), power off and power on with Vol- held again. This time dont install the passimg.zip, and choose recovery.
At the Android & warning triangle, hold the power button and press Vol+
Choose install update.
Voilà, a completely up to date, stock phone.

thank you very much for your help!! i was searching through the forums and there was like 20 million ways to do it non specific and i found myself running in circles

Have I bricked my phone???
I followed the instructions above (completely) and now, I do not seem to have a recovery screen...
The phone boots up but because I get FC constantly, I tried to redo these instructions and cannot get a recovery screen. I get the bootloader which re-installs the Passimg.zip, then nothing but an exclamation mark when I try and get recovery.
I did a data wipe B4 as well as a davlik wipe.
Am I done??
Previously CM6.1.0
RA 2.0

alexinmontreal said:
I followed the instructions above (completely) and now, I do not seem to have a recovery screen...
The phone boots up but because I get FC constantly, I tried to redo these instructions and cannot get a recovery screen. I get the bootloader which re-installs the Passimg.zip, then nothing but an exclamation mark when I try and get recovery.
I did a data wipe B4 as well as a davlik wipe.
Am I done??
Previously CM6.1.0
RA 2.0
Click to expand...
Click to collapse
The exclamation mark IS the recovery...the stock one that is.
To access it, press the VOL Down (-) with the POWER buttons

Hi Rusty
Would this work with a phone on ERE36B, kernel 2.6.33 hi-apk?
I have updated my phone which was on Vodafone and now I am FRG83D, but my brothers N1 has the ERE36B version, so just wandering if the steps you outlined above will work on his phone.
Cheers

Yes it will, he can be off the Voda build by copying the above.

Hi Rusty
So is the ERE36B, kernel 2.6.33 hi-apk a Voda build?
I didn't think it was but I know nothing. So the steps will work even on the ERE36B build?
Cheers

Oh yeah, it's not a Voda build, that's EPF30 I was thinking of.
It will still work though. Hell, to be honest, there is an update .zip from ERE36B => FRF91, so that would be less hassle.

sorry for noob question.
Will this re-lock my nexus one (return an unlocked bootloader to default) ? I'm about to send my N1 to HTC for repairs/replacement (my camera is not focusing on distant objects, works on close-ups only) and unlocking voids the warranty

decisa said:
sorry for noob question.
Will this re-lock my nexus one (return an unlocked bootloader to default) ? I'm about to send my N1 to HTC for repairs/replacement (my camera is not focusing on distant objects, works on close-ups only) and unlocking voids the warranty
Click to expand...
Click to collapse
NO. There is no way to relock the bootloader, once it has been unlocked.

futango said:
NO. There is no way to relock the bootloader, once it has been unlocked.
Click to expand...
Click to collapse
So there's no reason to revert even to stock rom, right? Warranty is void, period.
Any advice on this matter? Maybe someone had experience dealing with HTC and can share some thought?

decisa said:
So there's no reason to revert even to stock rom, right? Warranty is void, period.
Any advice on this matter? Maybe someone had experience dealing with HTC and can share some thought?
Click to expand...
Click to collapse
I have sent 2 phones into HTC with unlocked bootloader. I have not had any problems getting a replacement phone. Just give it a try.
I did return them to stock. Stock rom, stock recovery.

Edit: I tried it and it worked! So no need to answer but thanks anyway
Hi,
I wonder if this will also work for my phone?
Where am I at the moment? I have a Nexus One SLCD (Vodafone Europe) with AmonRa 1.8.0.1 Recovery and FRG83 installed. Bootloader is locked. No root. Now I get the update notification for FRG83D but can't install it. The N1 reboots and stops with a verification error. Now I think that I can't install FRG83D because of the AmonRa recovery.
As I don't have the need to install Custom ROMs (tried CM 6.0 but didn't like it so went forward to FRG83 Stock ROM) and still have no need for root I just want an N1 that just works with OTA from Google => absolute Stock (recovery and ROM) without waiting for Vodafone
So I wonder if that method descriped in this thread will bring me to my goal of a stock recovery and stock ROM on my N1 SLCD. Does FRG33 work with SLCD? I had a "broken"/dark display in recovery and ROM because of AMOLED/SLCD once and would like to not have that problem again
Greets. Grimsrud

Hi Rusty
With regards to update .zip from ERE36B => FRF91, when I go to this link from another thread, I get the 404 Not Found page. The link I am using is:
android.clients.google.com/packages/passion/signed-passion-ota-43546.cc653ee4.zip
Any other links I can try to get the update.zip ERE36B => FRF91?
Cheers

grimsrud said:
Edit: I tried it and it worked! So no need to answer but thanks anyway
Hi,
I wonder if this will also work for my phone?
Where am I at the moment? I have a Nexus One SLCD (Vodafone Europe) with AmonRa 1.8.0.1 Recovery and FRG83 installed. Bootloader is locked. No root. Now I get the update notification for FRG83D but can't install it. The N1 reboots and stops with a verification error. Now I think that I can't install FRG83D because of the AmonRa recovery.
As I don't have the need to install Custom ROMs (tried CM 6.0 but didn't like it so went forward to FRG83 Stock ROM) and still have no need for root I just want an N1 that just works with OTA from Google => absolute Stock (recovery and ROM) without waiting for Vodafone
So I wonder if that method descriped in this thread will bring me to my goal of a stock recovery and stock ROM on my N1 SLCD. Does FRG33 work with SLCD? I had a "broken"/dark display in recovery and ROM because of AMOLED/SLCD once and would like to not have that problem again
Greets. Grimsrud
Click to expand...
Click to collapse
You can grab the update at this link: http://shipped-roms.com/shipped/Pas...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
Place it to your sdcard root and boot into RA recovery, where you would flash from zip

Never mind. I have found the link for the download.
signed-passion-ota-43546.cc653ee4.zip from a search on the net.

gravufo said:
The exclamation mark IS the recovery...the stock one that is.
To access it, press the VOL Down (-) with the POWER buttons
Click to expand...
Click to collapse
Thank you for the quick answer...Me bad
It's All good...I put this stock ROM on my phone with update to FRG83D...installed RA 2.00 to make a nandroid of it, then restored my lovely CM 6.1 back. When gingerbread comes out, I'll just restore the stock ROM and install update (until Cyanogen comes out with a ROM)
Thanks again

Well, I have come across a problem. My brothers N1 has an unlocked bootloader. The N1 is running ERE36B, so the passimg file is not working.
Does the N1 have to be unrooted so we can get the FRF91 build on the phone?
Sorry if it's a noob question and all, but any help would be appreciated.
Cheers

Unlocked bootload makes no difference.
However, there is another way, extract the .img files from the passimg.zip and use fastboot to flash the system.img and boot.img.

[Q] Custom Rom on A854 (Want Froyo)

ok guys i have looked EVERYWHERE. I joined this forum just to ask this question, as the name suggests, i was a recent iphone/ipod touch jailbreaker and just recently switched to android, and am currently not very familiar with the terminology and exploits..
I have been using a rooted A854 on Ntelos. It is a pretty locally based company near charlottesville, va. It is quite similar to telus in canada, but with very close ties to sprint in the shenandoah valley.
when i originally tried to root via a vulnerable recovery with rsd lite and a froyo, prerooted version, it kept failing so my friend downloaded and installed universal androot which worked like a charm. The only thing was that nandroid wasnt possible via that method, and i still didnt have Froyo.
Recently, when i installed ROM manager, I was able to flash Clockworkmod's open recovery, and was able to successfully make a nandroid. I am however interested in installing a custom ROM with froyo.
I have looked into Motofrenzy and Cyanogen 6 (unofficial port for Milestone)[/URL] which were available via nandroid restore.
When i was looking it was telling me to put the file for the rom in nandroid/adbrecovery but i have no such location on my sd card.
It also says that in order for me to maintain 3g access, i need the local 3g band file, which is also not available from the rom sites.
if anyone was successful in flashing a custom rom to the A854 via nandroid restore with custom 3g bands, could you please help me.
Also any additional help would be appreciated...
Thanks in advance
~iphoneconvert
Links:
android DOT doshaska DOT net/cm6
dext3r DOT komodin DOT org/

i also have da same phone with ntelos its really a rebranded moto droid not milestone which is a gsm phone so only flash droid roms . in clockwork mod after flashing recovery go to back up current rom and do a nandroid back up . because it only gives da sdcard about 20 sec. to mount it usually say error cant mount just quickly hold down x and power and it will boot into recovery on da second try . go down 2 nandroid do a back up then reboot in clockwork go 2 download a rom and flash away

so your saying that i need to boot into recovery twice? and yeah i know its a rebranded droid but i thought that i needed roms for the milestone (i guess they were referring to the gsm version). Are you sure that any droid rom will work? Because the bootloader is locked down and the roms depend on changing that correct?

OK. i think i found out one of my problems. Since my friend and i were never able to successfully flash a vulnerable recovery, my phones recovery mode kept booting into android default. I had an update.zip with GOTS recovery in it and it would fail signiture verification, but when i booted into recovery through rom manager it would let me into clockworkmods recovery... i updated to it there and it went through so i think i can flash a rom now... if only i werent so chicken

yeah droid1 roms (cdma) i don't know much about open recovery or vulnerable recovery i just used androot 1 click root to get root then used rom manager to flash clockwork mod recovery did a nandroid and been rom surfing ever sense. im on like my 4th 854 and they all have dat boot twice issue it only when u try to like install a rom straight from clockwork

Man, i can not tell you how much you helped me, i have searched everywhere for weeks for what you just told me!
So i can just install roms straight from rom manager and they will all work? freaking beast. Thanks a ton
Oh and btw if you havent overclocked i recommend you do so with an app from the market, milestone overclock... SO HELPFUL, it makes the phone so much faster... i have it set to 1200 mhz and 80 vsel with no distinct loss in battery life.

so which roms have you been using and how did you get froyo

i have da paid version of rom manager so i just flash overclocking kernels from there to go with wuteva rom i flash cause most custom roms max at 800mhz just make sure it says kernels for any rom . i been using a rom i got from the custom rom section on the droid forums called ultimate droid 2.1.0 really customizable if dats a word lol

Ntelos
So you have th ntelos milestone using a custom rom, how did you get your data and mms working ? Do you have the APN setting for ntelos?

I dont have to change those? my data worked but I didn't try mms
Sent from my A854 using XDA App

ntelos
Ahh ok I just finished flashing to cm6.1 and it works flawless then you simply go to voice dial and say open apn's and edit the mms setting to be ----mms.ntelospcs.net then all is well, I have voice, data, and mms all working.

so m tried froyo but it wouldn't recognize my sd... I got back by putting in my other sd and installing cyanogen 5 again... i really want cyanogen 6.1... ugh... imma try again to update to froyo but with my other sd
Sent from my A854 using XDA App

flash back 2 your stock ntelos rom click on voice dialer it should say " say a command " then you say "open APN's" sometimes it takes a couple of tries but it will show a list of APN settings copy it down on a piece of paper . now when you flash another rom do the same thing with da voice dialer but change da settings from verizon to da ntelos settings you wrote down press menu click save changes . reboot now you should have mms working . hope this helps

Ok guys thanks for all this help for everyone here and especially me. If someone wanted to make this into a non question post with maybe a step by step guide? i suppose i could but im feeling awfully lazy right now so yeah..

Ntelos
Yea not much love for the Ntelos folks here so we need to stick together

yeah we really do
Sent from my A854 using XDA App

well today is a new problem, i flashed the liquid frozen yogurt 1.95 and lost my data 3g connection, i can turn it off then back on and it will come on for about 10 mins then 3g will be gone until i turn it off and on again...Any ideas?

well does it switch to 1x or does it just leave... you could also try to toggle airplane mode on/off... every so often my data switches from five bars 3g to 2 bars 1x and toggling airplane mode normally fixes it... but if you lose it completely I recommend you try to either nandroid back to stock or attempt to send mms or call someone and see what happens...
Sent from my A854 using XDA App

also try what eboogie said...
Sent from my A854 using XDA App

I resolved my loosing data connection, there is a setting in the connections and wireless tab that you can choose Home or automatic and it was set to automatic, I changed it to Home and bingo all good...

[Q] [S.O.S.] A rare MILESTONE brick situation!

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

[Q] only boots into recovery

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.