Related
I'm inviting all you guys shoot me down for the noob i am.
I've search and i have found, I've read but only partially understood.
the background:
-Nexus one on vodafone epf30
-Downgraded to erd79 using fastboot (via Terminal in Mac-osx).
-Rotted and installed Amon recovery with sucess.
-At this stage i tried to install a variety of different pre rooted roms
- upgraded to frf91 OTA after giving up on trying to root froyo
I basically just would Froyo 2.2 rooted on nexus one.
I've found a variety of different methods and techs but haven't had any success i can downgrade again and again but each attempt i reach the update.zip stage and simply get a varification failed message.it's likley ive missed something here?!
I'm on mac and I'm sure I'm not having the update.zip.zip issue. ive checked and double checked, (that same issue caught me out before on symbian).
Does anyone dhave a simple deffinitive soloution or can point me in the right direction/
im aware this post will cause a shower of "search you noob SCUM!" style posts.
cheers in advance
http://forum.xda-developers.com/showthread.php?t=712983
Read from:
"By Popular Demand (Credit to lox):
Update.zip to flash with custom recovery"
Download, update using AmonRa's recovery, reboot to bootloader, flash new radio from any Froyo ROM thread in Development, reboot, enjoy.
hi, thanks for your reply. I'm pretty sure i have tried this method. if i down grade to erd79 can i apply this from there or should i go up to ere27 ? and does this require amons recovery or can it be done from a standard recovery?
Sorry im a symbian migrant :-( this is all new and exciting
ok so i down graded again to erd79 then rooted and installed AMONs recovery
installation of update.zip fails with the verification failed, is there something about AMONs custom recovery that im missing should what could be the cause for the verification to fail. im pretty sad now.
maybe there is a way to flash pre rooted Froyo directly using super boot?
maybe i need to be up
You've already installed a custom recovery. Basically you are done the whole rooting process.
No more need to downgrade or anything of the sort. Now you just go into recovery and flash what you want, no other steps.
Now you should be able to flash any custom rom meant for unlocked users.
You may be trying to flash the official 2.2 rom, try looking for a 2.2 for root users. Or try flashing CyanogenMod 6.
Are you sure you have Amon's Recovery because my buddy though he had it and he didnt which is why he couldnt install a rooted froyo ROM. Try http://forum.xda-developers.com/showthread.php?t=702191
ok ill give that rom a shot though i think my main issue could be the fact im using mac os x the downloader in safari automatically unzips .zip files so maybe recompressing the zip is causing the varification to fail.
ill have a go when im home and at a faster net connection work is like 0.2 up and down makes me feel ill!
Oh ok. I have a MAC aswell but I use google chrome for my browser.
OMG! mods lock this down! no need for anything more to be added!
MAC = FAIL
Windows+win
all you have to do is download using anyother browser DONT USE SAFARI!
and success will be yours! rebooting now to pre rooted custom frf91 WOOP!
Hey OP,
Actually you can still use Safari as it does unzip the file automatically but it also downloads the zip file so you end up with both. At least my MAC does this. MAC's are great, Safari on the other hand is junk so don't blame the whole computer for the browsers fault.
I just got a Nexus One that was ROMed and rooted (has RA-nexus-v2.0.0 recovery) and enom's 2.14.2 ROM. I don't very much like it (seems slow). I am trying to go back to STOCK Android 2.2.2, with Root access, in preparation for 2.3's release. I know how to use ADB so that's not my problem. I've downloaded FRG91 in hopes that I will get an OTA to FRG83G. Now here's where I start getting problems. I go into Recovery, go to Flash Zip from SD card, and try to flash it, but it says it doesn't have signatures. md5sum is correct so that's not it. Can anyone help me out? I've tried doing about 10 different things so far and none of them have worked. Maybe someone else has seen this? TIA.
Have you try to toggle signature verification off?
Here's a rooted 2.2.2 rom
http://forum.xda-developers.com/showthread.php?t=927935
I haven't. I think I might have found a way to get this baby working. I'm working on it now. If I need anymore help, I will re-ask in this thread. Thanks for the tip though, didn't think of that!
Alright. I think I got it to work. Had to do some fenagelling, but I got it back to stock 2.2.2 Official.
Admin, can you delete this post?
You can't flash stock roms without stock recovery, Google's signature is on the stock roms so only stock recovery recognizes it. There is also a option in your custom recovery to turn of signature verification. I wouldn't recommend that you try, because I don't know what would happen. But it's a option, if your that hard pressed to go back to stock. Another note, since the G1 days the devs built their roms to stop OTA updates. So if you flash stock recovery, then you may need a stock rom to receive a OTA. I wouldn't get my hopes up about getting Gingerbread or Honeycomb OTA. I don't see anything on any android forum about this happening, I could be wrong though. If you can get your hands on a stock recovery image then you can flash with adb or fastboot commands. Good luck.
Go here for further assistance
http://forum.xda-developers.com/showthread.php?t=614850
blas4me said:
You can't flash stock roms without stock recovery, Google's signature is on the stock roms so only stock recovery recognizes it. There is also a option in your custom recovery to turn of signature verification. I wouldn't recommend that you try, because I don't know what would happen. But it's a option, if your that hard pressed to go back to stock.
Click to expand...
Click to collapse
Turning off signature verification works fine. No problems whatsoever flashing stock ROM/updates.
blas4me said:
Another note, since the G1 days the devs built their roms to stop OTA updates. So if you flash stock recovery, then you may need a stock rom to receive a OTA. I wouldn't get my hopes up about getting Gingerbread or Honeycomb OTA. I don't see anything on any android forum about this happening, I could be wrong though. If you can get your hands on a stock recovery image then you can flash with adb or fastboot commands. Good luck.
Go here for further assistance
http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
OTA updates have nothing to do with a stock recovery. All newer versions of Amon_RA and CWM custom recoveries have signature verification toggles, so you can install OTA updates without problems.
The only thing is that you need to have a stock ROM (not de-odexed, and not an AOSP build) for the OTA update to install.
hey guys i just got my nexus one 2.3.3
im confused what 2 do first
root, unlock bootloader
what 2 do first?
and i preffer to do all these things WITHOUT adb, bcoz adb never works with me
You can't unlock bootloader without ADB (or actually without fastboot, but if you can't get ADB to work, then you probably won't be able to get fastboot to work - since they work the same way).
My suggestion is - do nothing. At least until you'll be able to follow one of the guides and get ADB and fastboot to work. Then you can decide yourself, whether you want the bootloader unlocked or not, and how will rooting benefit you.
what are the benefits of unlocked bootloader?
i just wanted it to get it rooted and flash CM7 on it
It has been discussed a lot, please search to get A LOT of answers.
In a very short version, the benefits are:
Safe radio updates (using fastboot)
Ability to flash whatever you want whenever you want - which is, permanent ability to have root access, regardless of the currently used OS.
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
shiyou said:
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
Click to expand...
Click to collapse
If there's lock icon at the bottom of boot splash screen, it means the bootloader is already unlocked. Is it used one?
yes its used, i guess that guy alrdy unlocked it for me
another problem
i have serius wifi issue, its different from the other wifi problem
if i connect to my wifi its authenticating, then disabled
i dont even go to sleep its just says disabled after authenticating, i tried reconecctint but same things happens again...
i installed wifi fixer but that doesnt work either
also, my 3g drops after 4 sec and i cant get it to work afterwards
Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them.
i tried factory reset but didnt work...
This is exactly the reason why I suggest not touching your phone.
You either don't understand what exactly I'm guiding you to do, or don't understand the difference between various maintenance/repair operations. Flashing a new ROM and wiping user data from custom recovery ISN'T the same as doing "factory reset" from within already-installed ROM. Flashing 2 ROMs with different base (for example, lightly modified stock and CM7, or CM7 and MIUI, etc) introduces enough difference on the SW size to (almost) make sure that any problem which persists in both new ROMs, is coming from HW.
In any case, I suggest either waiting for someone with much more patience than myself (which isn't hard - patience isn't one of my strengths) to explain you some basics that you're not willing to learn yourself by reading, reading and some more reading, or to give your phone to someone who knows what he's doing.
dude....
i rooted and flashed many roms b4, this isnt my first android phone
i just got confused data wipe with factory reset....
Ok well now I need to know if you have a custom recovery, if so then just 5X wipe plus 3X system wipe and flash a new ROM, if not then do you have root access if not I'll walk you through the process.
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
i know how 2 root,flash,wipe, nandroid and all
i did it many times b4
i think i wont use nightly builds, but a stable? or RC?
which should i take?
How about cm7.1 RC1 that is the latest version of cyanogen mod.
rugmankc said:
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
Click to expand...
Click to collapse
why not clockwork recovery 3? the cyanogenmod rc1 states that i need that?
should i use gingerbeak? im on 2.2.3 and install the recovery afterwards?
ok i rooted it with gingerbreak and flashed clockworkmod recovery on it
after that i went into recovery and couldnt find nandroid backup so i rebooted again
i tried to make a backup via rom manager and it ended up with a "!" icon
i tried to go into recovery again and again i got the "!" icon
I don't know anything about Gingerbreak
But, on CWMod 3.+, it has been unstable for a lot of people--I don't recommend it
If you have Rom Manager--flash something like 2.5.1.4??
Still recommend Amon_Ra
I am not sure, but if you get the exclamation, you may not be rooted
If you are experienced at flashing, I would as another poster suggested--get to know your phone and study hard info from the Rom threads you want to try before trying.
What color was recovery--did it say ClockWork
I don't think you will see the name Nandroid in Clockwork--just Clockwork backups
A couple more suggestions, if you want
Back up sd card regularly--you will lose it on occasion--if you need to reformat it, use sdformatter outside of phone
Partition sdcard with zero swap
Wipe all (data/caches) multiple times before flashing new rom, including System
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
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.