I thought perhaps devs or others might find a Nandroid of a successful installation of the 2.3.4 update for the Verizon R800x useful.
Use at your own risk. I bear no responsibility if you end up with a shiny black brick.
This is the Nandroid I made after my FOTA completed today and I did a factory reset.
What I did:
Before the Update:
Installed the R800x 2.3.3 ftf file.
Rooted with the zergrush method.
Backed up with OTA Rootkeeper.
What I did after the Update:
Shut down and booted into Fastboot mode.
Booted into Recovery via Recovery.img
Ran Factory Reset - Wiped data, cache, and dalvik cache.
Made the Nandroid.
Afterwards, I rebooted and completed setup. I noticed that SuperUser was still in the Apps drawer. Installed Root Explorer and it worked ok. Installed Root Checker and it showed I have full root. I did not have do anything with OTA Rootkeeper.
And the Link: http://www.mediafire.com/download.php?xikhi4dldb0d8dw
EDIT: This is posted for test purposes only. Please be aware that if you restore it over the 2.3.3 kernel, somethings will not work properly or at all. Example WiFi and Camera.
netizenmt said:
I thought perhaps devs or others might find a Nandroid of a successful installation of the 2.3.4 update for the Verizon R800x useful.
Use at your own risk. I bear no responsibility if you end up with a shiny black brick.
This is the Nandroid I made after my FOTA completed today and I did a factory reset.
What I did:
Before the Update:
Installed the R800x 2.3.3 ftf file.
Rooted with the zergrush method.
Backed up with OTA Rootkeeper.
What I did after the Update:
Shut down and booted into Fastboot mode.
Booted into Recovery via Recovery.img
Ran Factory Reset - Wiped data, cache, and dalvik cache.
Made the Nandroid.
Afterwards, I rebooted and completed setup. I noticed that SuperUser was still in the Apps drawer. Installed Root Explorer and it worked ok. Installed Root Checker and it showed I have full root. I did not have do anything with OTA Rootkeeper.
And the Link: http://www.mediafire.com/download.php?xikhi4dldb0d8dw
Click to expand...
Click to collapse
Now all I need is an updated DooMKerneL...
FINALLY!
Many thanks again!
So I need a kernel too to go with this? What will happen if I flash this on 2.3.3 and reboot?
Sent from my R800x using Tapatalk
cell128 said:
So I need a kernel too to go with this? What will happen if I flash this on 2.3.3 and reboot?
Sent from my R800x using Tapatalk
Click to expand...
Click to collapse
The kernel is included in the backup
Extract the boot and flash via fastboot
EDIT: Nevermind, its not there.
Doom said one of his Kernals may work. He posted the version name in 1 if the 2 r800X threads going on today.
Sent from my LT26i using XDA
poo-tang said:
Doom said one of his Kernals may work. He posted the version name in 1 if the 2 r800X threads going on today.
Sent from my LT26i using XDA
Click to expand...
Click to collapse
More testing found it works with the 2.3.3 kernel by Hactyl, so it -should- be fine, but again, use at your own risk.
poo-tang said:
Doom said one of his Kernals may work. He posted the version name in 1 if the 2 r800X threads going on today.
Sent from my LT26i using XDA
Click to expand...
Click to collapse
Trying out the 2.3.3 kernel first.
Ill try newest DooMKernel if this does not boot.
EDIT: 2.3.3 Kernel works PERFECTLLY with 2.3.4
Anyone try using one of the DoomKernel's?
Glad you X users got a brake. Maybe now FXP will bring a full CDMA CM9
Sent from my LT26i using XDA
So if I flash this on my rooted 2.3.3, I'll have 2.3.4 and root?
I am on DoomKernel and am attempting to restore the nandroid with my custom kernel..... anyone know if this is a bad idea?
---------- Post added at 01:34 AM ---------- Previous post was at 01:28 AM ----------
DoomKernel with nandroid restore works great.... no issues so far, but only been using it for 10 minutes, had to flash stock wifi modules.
DubleJayJ said:
So if I flash this on my rooted 2.3.3, I'll have 2.3.4 and root?
Click to expand...
Click to collapse
I wanna know this before I flash this.
scratch that, stock wifi modules do not work, however the phone seems to run fine with DoomKernel, just no wifi....
---------- Post added at 01:41 AM ---------- Previous post was at 01:40 AM ----------
DubleJayJ said:
I wanna know this before I flash this.
Click to expand...
Click to collapse
I just flashed the nandroid to my rooted unlocked bootlaoder 2.3.3 I didnt even flash stock kernel, still on doomkernel. And it works great, but no wifi... need to flash the right wifi modules most likely....
Used doomkernel wifi modules v01 and I have wifi now with DoomKernel on 2.3.4 and root
Just flashed stock 2.3.3 kernel and all seems good. Couldnt get wifi to work with DoomKernel, for now. So am on stock kernel.
How can I update from stock 2.3.3 and DooMKerneL v02 test 2 1.6GHz and not lose data?
savage24x said:
How can I update from stock 2.3.3 and DooMKerneL v02 test 2 1.6GHz and not lose data?
Click to expand...
Click to collapse
Backup 2.3.3
Restore 2.3.4
Advanced Restore Data from 2.3.3
Flash DooMKernel
Am i supposed to extract the file from the zip and place it in the CWM backup file and restore it as a nandriod file or do i just flash the zip like i would a complete rom?? I tried it as a nandroid backup and got MD5 mismatch. i and on 2.3.3 stock with root and a locked bootloader.
EDIT......
OK i got it. I believe that i got a bad file or when i tried to extract it through astro, something went wrong. I ended up redownloading it through my computer and using winzip and got a file with a totally different name.
ErisKlown said:
Am i supposed to extract the file from the zip and place it in the CWM backup file and restore it as a nandriod file or do i just flash the zip like i would a complete rom?? I tried it as a nandroid backup and got MD5 mismatch. i and on 2.3.3 stock with root and a locked bootloader.
Click to expand...
Click to collapse
Unzip an place folder in sdcard/clockwork/backup/
Then go into recovery and I did a nandroid backup in case, then wiped data and factory reset, wipe dalvik ,then go to restore and restore the nandroid for 2.3.4
I did that and its going good no issues... and I have root and unlocked bootloader with DoomKernel
Leraeniesh said:
Backup 2.3.3
Restore 2.3.4
Advanced Restore Data from 2.3.3
Flash DooMKernel
Click to expand...
Click to collapse
When you do advanced restore Data what specifically does it bring back? Apps? Or just things like contacts/etc.
Trying to decide whether I need to go one by one through 40 damn games and ti backup them
Would I still need an unlocked bootloader to get a new kernel? I'm assuming yes.
Sent from my iPad using Tapatalk HD
Related
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
Quick question. Can I do a nandroid restore after wiping data, cache and dalvik?
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
IDMA.DROID.X2 said:
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
IDMA.DROID.X2 said:
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
Click to expand...
Click to collapse
I have a nandroid on my internal that has endured several data wipes and sbf's. It is a backup of my stock phone before flashing anything. I backed it up in both places just in case.
Sent from my cm7dx2 using XDA App
litetaker said:
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Click to expand...
Click to collapse
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
Good to know! I missed the tests done, I thought it backed up everything.
Sent from my MB870 using XDA App
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
jsgraphicart said:
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
Click to expand...
Click to collapse
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
iBolski said:
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
Click to expand...
Click to collapse
Ok, that makes sense. I figured it would be fine but didnt know the technical details.
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
T3HBR1AN said:
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Back in December, I asked the question about nandroiding and if it replaced the kernel. Motcher (and ashclepdia) helped out with this one. Motcher SBF'd to 2.3.4 and then nandroided back to Eclipse 2.0.3 (which is 2.3.5) based and the kernel version came up as 00005 which is the 2.3.4 kernel. So, Nandroiding does NOT replace the kernel.
Here's the posted that he posted about this:
http://forum.xda-developers.com/showpost.php?p=20808392&postcount=20
It may be that the differences are minor enough that it won't cause issues, but if the official 2.3.5 ever comes out, it might be best to always SBF back to 2.3.4 if you have to just to be on the safe side. I guess the moral of the story is, do this at your own risk.
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
bandit1224 said:
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
No. That means the md5-sum hash key that was generated after the backup was created isn't matching with your nandroid backup. It means possibly your backup is corrupted.
Wiping the big three has nothing to do with nandroiding.
Uninstall bsr -either cm7 or orig. Then reinstall cm7 bsr. It worked for me On cm7. BTW Be sure not to use any spaces when renaming.
failed restore
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Sykotyk said:
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Click to expand...
Click to collapse
this is a thread for the motorola droid x2.
oops
Lorenzo VonMatterhorn said:
this is a thread for the motorola droid x2.
Click to expand...
Click to collapse
i've been searching threads with search tool....guess i wasn't paying attention.
Cheers
I'm on amonra 3.12b, I've tried several times to restore a backup. I was recently on Scott's GBE rom and wanted to try out Joelz new ICS rom. Well his ICS rom was giving me problems so I tried to restore the GBE rom backup, but my phone wouldn't boot up, I was stuck at a black screen, but it was still backlit.
I did the nand backup properly, I didn't get any errors. I left all the options as they where I don't touch anything with the check boxes. I then did a wipe/factory reset and then I restored the nand backup of the GBE rom I made earlier. It restored fine, no errors. I don't understand why my backups arent working? Thankfully I still had Scott's rom on my sdcard so I just flash that again and it worked. I have no problem flashing roms, for some reason I just can't seem to restore any backups.
Yesterday, I went through this same problem but with a different error. I was trying to flash Joelz rom but it wouldn't work, so I tried restoring my GBE nand backup but amonra gave me an error. "oops...something went wrong! please check recovery log".
As you can see I'm having a tough time troubleshooting this problem so any help would be very much appreciated, b/c it's getting to be a pain having to re-flash a rom every time I wan't to switch and having no safety net in case something happens, can't backup anything. Thx!
u gotta flash the the boot.img
Read the very bottom where it says more info.
http://forum.xda-developers.com/showthread.php?t=1459347
Yeah...you will need to flash a GB kernel when going back to GB from ICS.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
Yeah...you will need to flash a GB kernel when going back to GB from ICS.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
So if I'm on an ics rom and want to restore a backup that was on gb I need to flash the gb kernel after restoring the gb rom? And than vice versa..
Sent from my ADR6425LVW using XDA App
Yep that is it.
bal1985 said:
So if I'm on an ics rom and want to restore a backup that was on gb I need to flash the gb kernel after restoring the gb rom? And than vice versa..
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
That's correct but you may get a mainver error when you try to do that depending on what kernel/mainver you have.
I have run into that a couple times but it is simple to fix by editing the text file in the kernel to match the mainver version.
jmorton10 said:
That's correct but you may get a mainver error when you try to do that depending on what kernel/mainver you have.
I have run into that a couple times but it is simple to fix by editing the text file in the kernel to match the mainver version.
Click to expand...
Click to collapse
Or just flash the kernel in fastboot. Then you don't have to worry about mainver.
feralicious said:
Or just flash the kernel in fastboot. Then you don't have to worry about mainver.
Click to expand...
Click to collapse
True, either way works fine.
I think it's easier to simply edit that file, but it's really easy either way.
Help !!
Last month i used this method and it worked out well but now it repeatly reboot iteelf and e wt19i keyboards are messed up. Then i tried to use clockward recovery but realised i didnt did any backup since i change sd cards. So i used factory reset and the problem is still unsolved !! And now i cant download any apps from the store cuz all it saidbwas my device isnt compatible for its version. After factory reset im still on andtoid ics and buildnumber 4.1.B
What should i do ? Please help and thanks in advance
which method did you used?
usman_fareed said:
which method did you used?
Click to expand...
Click to collapse
i downgraded to gb 0.58 firmware to root my phone and upgraded it back, it worked fine since then until it often reboot automaticly and now it isnt hricked but i cant download any apps or have a normal looking qwerty pad
do you think if it will recover if i reflash the 4.1.B agn ?
Update it to 0.62 gb. Because it was launched to fix rebooting.
Sent from my WT19i using xda app-developers app
GeneralPag said:
Update it to 0.62 gb. Because it was launched to fix rebooting.
Sent from my WT19i using xda app-developers app
Click to expand...
Click to collapse
so after rooting 0.58 i should upgrade to 0.62 before flashing the lastest firmware ?
kokzhanjia said:
so after rooting 0.58 i should upgrade to 0.62 before flashing the lastest firmware ?
Click to expand...
Click to collapse
I really dont see a point in doing so if you plan to upgrade to ICS.
If you're experiencing problems, you should do it all once again, flash .42 or .58, root it, upgrade it to ICS, install CWM and back it up (nandroid backup), with all the bloatware and everything... just in case... afterwards, start modding, delete bloatware and do whatever you want. In case you screw something up, you can always return to stock rooted ICS (that you backed up) and try again
When i installed ICS i flashed .42 and then i upgraded to ICS... so not even .58 and certainly not .62; it seemed a bit cleaner not to upgrade to higher GB version before upgrading to ICS, since if i wanted to keep root on ICS, i wouldnt be able to erase user data.
Reinstall ROM.
kokzhanjia said:
Help !!
Last month i used this method and it worked out well but now it repeatly reboot iteelf and e wt19i keyboards are messed up. Then i tried to use clockward recovery but realised i didnt did any backup since i change sd cards. So i used factory reset and the problem is still unsolved !! And now i cant download any apps from the store cuz all it saidbwas my device isnt compatible for its version. After factory reset im still on andtoid ics and buildnumber 4.1.B
What should i do ? Please help and thanks in advance
Click to expand...
Click to collapse
You can reinstall ROM. Mount USB on CWM and copy your ROM.zip; Make a Full Wipe. Farctory Reset, Wipe partition cache, and Wipe Cache Dalvik. Next Install your ROM.
loCe45 said:
I really dont see a point in doing so if you plan to upgrade to ICS.
If you're experiencing problems, you should do it all once again, flash .42 or .58, root it, upgrade it to ICS, install CWM and back it up (nandroid backup), with all the bloatware and everything... just in case... afterwards, start modding, delete bloatware and do whatever you want. In case you screw something up, you can always return to stock rooted ICS (that you backed up) and try again
When i installed ICS i flashed .42 and then i upgraded to ICS... so not even .58 and certainly not .62; it seemed a bit cleaner not to upgrade to higher GB version before upgrading to ICS, since if i wanted to keep root on ICS, i wouldnt be able to erase user data.
Click to expand...
Click to collapse
so you mean i could just proceed with reflashing my wt19i to 0.42 and root it and do it all over agn safely ?i knw its the only way nw.. cuz my phone now cant even perform like a smartphone.. no apps and whatsoever
kokzhanjia said:
so you mean i could just proceed with reflashing my wt19i to 0.42 and root it and do it all over agn safely ?i knw its the only way nw.. cuz my phone now cant even perform like a smartphone.. no apps and whatsoever
Click to expand...
Click to collapse
Yes. Some also recommend you back up your sdcard and erase it before flashing new rom.
loCe45 said:
Yes. Some also recommend you back up your sdcard and erase it before flashing new rom.
Click to expand...
Click to collapse
thanks, thanks a lot .. all my worries are gone now
I am running Jokers CM10 right now, if I restore one of my backups when I was rooted and locked and then restore a backup of my CM10 with bootstrap will I be unlocked again ? I hope that makes sense
Nope.
Ok, thanks for the reply :good:
But I could send you zip, that you can flash before cm10 restore and you will be unlocked after reboot. Maybe pulling battery after flashing will be needed.
After restoring stock (you would have to restore stock boot.img and recovery too), you could flash lock zip I can provide, to be locked.
But I am not sure, if you could restore cm10 with bootstrap.
Maybe that unlocking zip would have to flash cwm recovery too. And restore cm10 from that.
peetr_ said:
But I could send you zip, that you can flash before cm10 and you will be unlocked after reboot. Maybe pulling battery after flashing will be needed.
Click to expand...
Click to collapse
Woah, really? Did you make this zip yourself Peetr? I would be interested in that. It could be useful to refer to people.
And nimzp, thanks for the 'thanks'. You just put me at my first 100 :good:
I will post the link here, when I get home. It was tested by one person.
peetr_ said:
I will post the link here, when I get home. It was tested by one person.
Click to expand...
Click to collapse
I would be interested too....
You are welcome Acvice :highfive:
http://d-h.st/aVy - just flash with bootstrap recovery and reboot (maybe power off or battery pull will be needed
http://d-h.st/LWb - this is the locked one from 198_7
One question. If i try to restore my old backup when phone was unlocked i get error while restoring boot image. Is it normal or is there any way to restore a backup (taken using custom recovery) when phone was locked. Now phone is unlocked and using CWM recovery.
Sent from my MB855 using xda app-developers app