Related
I am tired of waiting for my update to appear. Does anyone have, or know of a thread where I can get the .183 update and use it with RSD?
im in the same boat
it's in the General forum...
http://forum.xda-developers.com/showthread.php?t=1056779
Here ya go: http://forum.xda-developers.com/showthread.php?p=13328724
This has the 1.8.3 update .sbf file and the newest version of RSDlite. FYI, flashing this .sbf *should* NOT erase your data or put your phone in a factory reset state. Enjoy your faster upload speeds!
Sent from my Blue Steeled Atrix
Thanks to both of you. Dling right now
hey all - I got a new D3 replacement today after the touch screen stopped working on the old one. it came with 5.7.906 installed. i am confused as to weather there is a way to unbrick it if i manage to muss it up when i go back to cm9. i love cm9 and hate the stock rom but considering this is my 5th D3 i am not willing to flash roms if i have no way to return to stock in case of hardware malfunction so i can get a new one under waranty
i appreciate any information on the topic
As long as you can get to the Moto Bootloader, then it is 90% likely that you can unbrick it. The tools can be found here:
http://forum.xda-developers.com/showthread.php?t=1255198&page=23
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
ovelayer said:
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
Click to expand...
Click to collapse
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
redsox985 said:
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
Click to expand...
Click to collapse
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
ovelayer said:
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
Click to expand...
Click to collapse
Oh, ok, so these are just the 5.6.890 FXZ files?
redsox985 said:
Oh, ok, so these are just the 5.6.890 FXZ files?
Click to expand...
Click to collapse
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Q9Nap said:
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
redsox985 said:
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
Click to expand...
Click to collapse
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Q9Nap said:
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Click to expand...
Click to collapse
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
redsox985 said:
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
Click to expand...
Click to collapse
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Q9Nap said:
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Click to expand...
Click to collapse
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Q9Nap said:
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Click to expand...
Click to collapse
Nope, XT862 with WiFi tether hacked radio. Request sent.
redsox985 said:
Nope, XT862 with WiFi tether hacked radio. Request sent.
Click to expand...
Click to collapse
yeah, i'd make sure your'e on fully stock 890 with no modifications before flashing 894; it should work. request accepted.
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
nemiroG1 said:
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
Click to expand...
Click to collapse
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
redsox985 said:
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
Click to expand...
Click to collapse
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Q9Nap said:
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Click to expand...
Click to collapse
I never did get around to formatting my SD card. Stock recovery only sees the EXT SD correct?
I'm currently chatting with Moto... This is odd. I'm going to start my own thread for it to leave this one be.
Hi guys, need some advice. I have read allot of confusing/conflicting info on this and I just want some clarification as a precaution.
I have a P1000 and am currently on the latest nightly of CM9 but I read about MTD and possible brick if flash incorrect rom. What I want to know is, is it safe to re-stock using Overcome and also to come back directly to CM9 or do I need to follow some other procedure first?
I previously came straight from Overcome to CM9 without issue but not sure if same goes for going back?
Sorry if this has been covered but couldn't find any clear cut answers.
Thanks in advance.
Actually I don't think it will cause hard brick.
At most you need to restock using Odin.
But no, you can't convert an MTD partition (running yaffs2) back to Overcome ext4 fs.
You need to restock with Odin with pit file selected.
EDIT: the updater can convert FROM ext4 to YAFFS2, so you go from Overcome to CM9 direct but not the other way round.
priyana said:
Actually I don't think it will cause hard brick.
At most you need to restock using Odin.
But no, you can't convert an MTD partition (running yaffs2) back to Overcome ext4 fs.
You need to restock with Odin with pit file selected.
EDIT: the updater can convert FROM ext4 to YAFFS2, so you go from Overcome to CM9 direct but not the other way round.
Click to expand...
Click to collapse
Well there isnt really any other brick then "hard" brick. If you can still use download/cwm etc then its not bricked at all. I think the term is just used far too loosely nowadays.
When I mentioned stock with Overcome I was referring to overcome safe stock guide/files, So its safe to re-stock with them after using CM9, I just need to repartition etc?
Thnx for reply bud.
pretty much it.
restock to GB-stock-safe-V5 with repartition should get rid of MTD safely.
MTD and EXT4 are different partition styles. All you need to do, as per priyana, is go to download mode, run odin, select the .pit file, check the re-partition and shoot. That will get you back to the stock partition style.
Actually....BML and MTD are partition type.
EXT4 and YAFFS2 are filesystem types.
Sent from my GT-P1000 using XDA
Can anyone help me?
I've did the exact thing that you're not supposed to do. Flash fra a MDT rom to a non MDT rom. Now whenever i try ti reflash to stock rom i'll get a bootloop. Not just with this rom but with all other roms. But if i try to flash the AOPK rom with MDT partition it boots fine.
How do i partition that MDT partition to stock?
Wrong to say not supposed to.
That in fact is how most if not all of us get to mtd rom.
How else to go to mtd if not from non mtd.
To flash back to stock, flash with Odin with pit file selected and repartition checked.
Sent from my GT-P1000 using XDA
Ok Safety Advice:
1st to go back from MTD to any file system whether RFS or EXT4 a FULL RESTOCK with with REPARTITION is mandatory (no workaround or shortcuts around that).
2nd Safety Advice. Since the dawn of the MTD CM9 has requires repeated attempts to restock. I would say you need to Strip the stock safe package from the bootloaders (just Delete boot.bin and sbl.bin files from the tar archive). They aren't needed anymore after you have jumped Ship from Froyo to GB. Also Bootloader bad flash is the only way really to brick a Samsung Device as you may have known.
Just my 2 cents.
So, it is not as easy as ABC to revert back to GB from CM9?
I see that GB-Stock-Safe-v5 has got everything in the package (including the dbdata.rfs that gives many people trouble). If after flashing it with a pit still does not work, what else can we do?
I found this youtube on moving from MTD back to BML, but on Samsung EPIC.
www.youtube.com/watch?v=ds9rwAoI2IQ
I know it's probably a stupid noobie question, ... but I did forgot to do this simple thing so many times:
You did a factory wipe and cache data wipe, right?
did you flash it like documented in the picture attached by phlooke here ?
http://forum.xda-developers.com/showthread.php?p=20974872
priyana said:
did you flash it like documented in the picture attached by phlooke here ?
http://forum.xda-developers.com/showthread.php?p=20974872
Click to expand...
Click to collapse
Oh, I am not the one in trouble (knock on the wood). I give comment because I also see his post on AOKP while I'm learning about the ROM. He mentioned that he already did repartition:
http://forum.xda-developers.com/showthread.php?t=1523174&page=168
Ah I see.
Well, I don't know what he did.
But if he re-stock. he should at least boot up the JQ1 stock rom and confirms everything is ok, which I am sure it was not yet ok for him.
He shouldn't go ahead with Overcome Kernel yet.
You have to proceed logically and rule out each possible cause of problem.
you cannot go back from mtd to ext4 so easily. you need to flash gb stock package via odin or heimdall to go back to ext4 from mtd. cwm will not work
Actually going back to stock means going from mtd to bml, not ext4.
And it will then format the partitions with RFS file system.
You only get ext4 if you flash overcome kernel.
Sent from my GT-P1000 using XDA
Already tried flashing stock rom with odin, and checking re-partition, didn't help.
Anyway it's working now ^^
@jakk212 -Please post your problem at ONE thread buddy. I'm sure you did not even see my reply at the AOKP thread.
----
And STOP flashing GB-stock-safe over and over again. I am very greatful teamovercome created it but sometimes there are easier and better solution than forcing it down your throat.
-----
As I said in the AOKP post, (actually the link I provided with it)
what I did was, I reverted to a 2.3.3 gingerbread STOCK downloaded from sammfirmware OR check.fus downloader attached it with .pit file(please search or use the one included with ODIN) while checking the repartition.
After finish, mostlikely you will still be in the bootloop because many ROMs do not inclide dbdata.rfs.
Flash dbdata.rfs.tar (please search).
when u r done flashing dbdata, reboot, and wait on the 'samsung' boot for as long as 10minutes for it to update the partition and retrieving and reading and updating.
Don't assume it is on a bootloop forever before you waited at least 10 minutes on SAMSUNG boot.
Jakk212 said:
Already tried flashing stock rom with odin, and checking re-partition, didn't help.
Anyway it's working now ^^
Click to expand...
Click to collapse
Anyway it's working now
(without telling us who tried to help, what did you do, for the benefit of others)
oh well... all good for you. That is good to hear.
Just wish you can share.
Ah! I missed that one short sentencd.
priyana said:
Anyway it's working now
(without telling us who tried to help, what did you do, for the benefit of others)
oh well... all good for you. That is good to hear.
Just wish you can share.
Click to expand...
Click to collapse
Dude relax;
I've followed the overocme stocksafe guide, but when flashing i've also included the modem.
So i've did the same as before but flashed the modem and it worked.
Sorry for spamming.
To keep the overview, here the place where you can find all the stock ICS builds made by me.
Flashable CWM versions available (no full wipe required) as well es NVFlash versions (full wipe only).
The CWM versions can only be installed by those already running new unlocked bootloader + CWM.
Essential update November 16:
New NVFlash versions (v28E & v28G) are available.
New features:
fixed bootloader, so Smartflash will work again for everyone
CMW Recovery 6, no more too big font in CWM, also no more /cache errors
fixing sizes of recovery partition and boot partition
NO full wipe required!! New NVFlash version can backup your /data partition and restore later (Internal SD will still be wiped!)
Noob-secure flashing process. Telling the user exactly what to do and asks for confirmation before doing anything.
Stock LG ICS content for internal SD card can be flashed as well (user is asked) - gives some extra music, apps, videos
No more deodexed version. I think odexed works best.
Google Now (Online-version) preinstalled, still about 25 MB free space in /system partition
additional widgets from SU660 preinstalled
the new installation scripts are available for both Windows and Linux (tested by me extensively)
Windows APX driver included (for Linux not needed)
some minor things. A custom kernel by me will come as soon as we get the final kernel sources!
New CWM ZIPs are available as well! Please be aware that they do not upgrade bootloader (=fix of Smartflash Bug), CWM (from 5 to 6) or fix partition sizes for boot and recovery partition (were too small, could cause problems lateron). Only NVFlash version does that. So you might prefer to, as a one-time-upgrade, use NVFlash version. You can, with the new NVFlash versions, backup and restore your /data partition, so your settings and apps won't be lost. Only Internal SD will still be wiped.
The new ICS builds are available in download folder, in subfolder "Second Generation ROMs (improved, recommended)".
Click to expand...
Click to collapse
All downloads: http://d-h.st/users/gueste/?fld_id=7336#files
The new ICS builds are available in download folder, in subfolder "Second Generation ROMs (improved, recommended)".
Deodexed version of v28G also includes some more widgets (those from the Addon-packages).
You have to read the installation instructions on NVFlash versions and CWM versions in this thread here: http://forum.xda-developers.com/showthread.php?t=1986097 (installation procedures are explained in first post).
Downloading NVFlash version of v28G. Thanks Stefan! :highfive:
[email protected] said:
Downloading NVFlash version of v28G. Thanks Stefan! :highfive:
Click to expand...
Click to collapse
Now I'll go buying something to eat and then I'll make the deodexed versions of v28G
And I'm gonna head for CWM 28G version. A million thx Stefan!! :good:
Update. ....and it of course works well! Thanks!
i know it's a noob question but.. why the kdz is obvious bigger(size) than your rom?
and one more question.. can you replace the logo in the bootloader with lg original one?
Stefan Gündhör said:
Now I'll go buying something to eat and then I'll make the deodexed versions of v28G
Click to expand...
Click to collapse
Ok, I'll wait for that version
Thanks.
BR.
RobYyY said:
i know it's a noob question but.. why the kdz is obvious bigger(size) than your rom?
Click to expand...
Click to collapse
Because of the high compression I chose for the archives! Sometimes compression works more effective, sometimes not.
You can believe me that I ONLY removed demo videos (~26 MB) and the Rom updater app and the LG remote controlling app (both together about 2-5 MB or something).
Thanx a ton for your rom Stefan.... its amazing.... can you brief about the advantages of the new V28G over the older version, is it highly recommended to upgrade to the newer one....??
sandeeppandey said:
Thanx a ton for your rom Stefan.... its amazing.... can you brief about the advantages of the new V28G over the older version, is it highly recommended to upgrade to the newer one....??
Click to expand...
Click to collapse
So far I can tell you it has got a new kernel and many updated apps and binaries. I don't know the exact changes though. But upgrade of course is highly recommended! You can make an upgrade without full wipe from my v28E version.
A millions thanks Stefan, downloading now v28g flasheable zip, you're best.
Can someone confirm if smartflash is working with the new bootloader...?? I tried to flash the new V28G baseband but was unable to get the phone in software upgrade mode....
Try to enter smartflash with battery inserted
Sendt fra min LG-P990 med Tapatalk2
Stefan Gündhör said:
Because of the high compression I chose for the archives! Sometimes compression works more effective, sometimes not.
You can believe me that I ONLY removed demo videos (~26 MB) and the Rom updater app and the LG remote controlling app (both together about 2-5 MB or something).
Click to expand...
Click to collapse
i wasn't refering to zip.. kdz is bigger than system.img
sandeeppandey said:
Can someone confirm if smartflash is working with the new bootloader...?? I tried to flash the new V28G baseband but was unable to get the phone in software upgrade mode....
Click to expand...
Click to collapse
Smartflash is working again!!!!!
I'm at v28G NVFlash version currently. I just flashed v28G BB with Smartflash.
Can somebody please try if it works for CWM version v28G as well??
If NOT, then you will just have to install the updated recovery image with different CWM. I will soon provide it. I'm not sure yet if the NVFlash bug is related to recovery.img.
RobYyY said:
i wasn't refering to zip.. kdz is bigger than system.img
Click to expand...
Click to collapse
The kdz contains multiple images and the baseband. it's not only system image. the kdz contains system.img as well which has the same size.
Might be a silly question, but can anyone tell me, in few words, what the difference is between LGP990_ICS_v28G_Stock_NewBL_Root_CWM_initd_NVFlash.7z
and
LGP990_ICS_v28G_Stock_Root_initd_4CWM-NewBL_NoFullwipe.zip ?
I just want something stock with maximum smoothness, I don't care about flashing new stuff and all that
which is the better ?
-rebuild the phone (install all program and everything) from startup ( nvflash )
-v28e --> cwm --> v28g ?
i wan't a stable, smooth, good working rom without any issue
Are you Angel sent by God for 2x user??
and buddy.. can you replace the logo in unlocked bootloader with original lg one?
SamS1989 said:
which is the better ?
-rebuild the phone (install all program and everything) from startup ( nvflash )
-v28e --> cwm --> v28g ?
i wan't a stable, smooth, good working rom without any issue
Click to expand...
Click to collapse
why not flashing v28g directly with NVFlash?
if you are on my v28e already you can use CWM of course
Hi all, I've recently broke my MM so i went to go and get it fixed... I did but now the software update is back to 2.1 before, it was at 2.3.7 and i would like to update it to anything better then this version maybe like 2.2 froyo or something else!!!
Thanks in advance.
Motorola Milestone
2.1
In my signature there is a link to a guide. That's describes everything step by step.
The only extra things you have to do is to install the 2.2 devtree and baseband update (they are needed to custom roms).
You can download the devtree update from HERE.
And the baseband update from HERE.
Erovia said:
In my signature there is a link to a guide. That's describes everything step by step.
The only extra things you have to do is to install the 2.2 devtree and baseband update (they are needed to custom roms).
You can download the devtree update from HERE.
And the baseband update from HERE.
Click to expand...
Click to collapse
So am I just supposed to download them and then put them on the root of my sd card and do the boot in recovery thing and update it from there?
Not in the root directory.
Put them in /OpenRecovery/updates
That way they will be easily accessible from within recovery.