[Q] Downgrade from CM9 to ICS or HC? - Acer Iconia Tab A100

Does anyone know of the proper procedure for downgrading to ICS or HC? I really don't feel like bricking my tablet.

PeteSeiler2010 said:
Does anyone know of the proper procedure for downgrading to ICS or HC? I really don't feel like bricking my tablet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1544486 ....guess you didn't feel like searching either lol...hope this helps

cheeb said:
http://forum.xda-developers.com/showthread.php?t=1544486 ....guess you didn't feel like searching either lol...hope this helps
Click to expand...
Click to collapse
this is this guide I followed and now I am bricked...maybe something different about CM9? dunno...just bricked.

Nandroid and install the ICS leak. I did it about 3 times today and I'm running perfectly fine right now.

I do search and I used that very link to downgrade from the ICS leak back to HC. There were reports of people bricking their tablets using that method when trying to go back to ICS or HC from CM9, I did not want to take that risk.
Sent from my A100 using XDA

bmb1983 said:
this is this guide I followed and now I am bricked...maybe something different about CM9? dunno...just bricked.
Click to expand...
Click to collapse
I'm not sure if CM9 has anything to do with it...but without you stating the process that YOU did i'm not sure if we can help you....
If I were to do this...I would've..
**Flashed 009 leak of ICS through CWM..
**Flashed HC 3.2 rom from the thread....hard reset after rom installs....
**Flashed HC 3.2.1 from thread.....hard reset (or reset from tablet..not necessary but its what I do)...
***Finished...
If this is everything that you did then I'm not sure why you would be bricked...maybe you need to go in the CM9 thread and start probing the devs over there...hope your tab comes back to life..
---------- Post added at 09:15 AM ---------- Previous post was at 09:13 AM ----------
PeteSeiler2010 said:
I do search and I used that very link to downgrade from the ICS leak back to HC. There were reports of people bricking their tablets using that method when trying to go back to ICS or HC from CM9, I did not want to take that risk.
Sent from my A100 using XDA
Click to expand...
Click to collapse
OK....didn't know there was an issue (or potential issue) with downgrading from CM9...thankfully I didn't install that as I'm not that fond of those roms in the first place....hope someone can figure out a solution if this is indeed bricking those who are trying to roll back to HC

That is the steps that i tried...but maybe in haste, i did something stupid.
I am trying to get something out of it with NVFLASH but so far nothing...
Oh well, its a nice paper wieght for now!

bmb1983 said:
That is the steps that i tried...but maybe in haste, i did something stupid.
I am trying to get something out of it with NVFLASH but so far nothing...
Oh well, its a nice paper wieght for now!
Click to expand...
Click to collapse
ok ...first..
cm9 didnt cause anything...remember how u got cm9? you had an unlocked bootloader and a custom recovery...
now u flashed a stock image of ics? guess what...now your bootloader is locked again and your recovery is stock. 9 times out of 10 then someone tries to flash a stock hc rom that doesnt have the hc bootloader and this is where theyre stuck.
seriously guys...going from unlocked to stock and back and forth yohr asking for trouble because people are forgetting steps.
once your unlocked and have cwm....stay there..you did this for a reason. ifs almost impossible to brick this thing with an unlocked bootloader. once your back to stock recovery and bootloaders you can seriously eff things up.
Sent from my SGH-I897 using xda premium

Oh I plan to stay with CWM and an Unlocked boot loader. Thanks for the information!
Sent from my A100 using XDA

PeteSeiler2010 said:
Oh I plan to stay with CWM and an Unlocked boot loader. Thanks for the information!
Sent from my A100 using XDA
Click to expand...
Click to collapse
good choice and no problem!
Sent from my SGH-I897 using xda premium

cheeb said:
I'm not sure if CM9 has anything to do with it...but without you stating the process that YOU did i'm not sure if we can help you....
If I were to do this...I would've..
**Flashed 009 leak of ICS through CWM..
**Flashed HC 3.2 rom from the thread....hard reset after rom installs....
**Flashed HC 3.2.1 from thread.....hard reset (or reset from tablet..not necessary but its what I do)...
***Finished...
If this is everything that you did then I'm not sure why you would be bricked...maybe you need to go in the CM9 thread and start probing the devs over there...hope your tab comes back to life..
---------- Post added at 09:15 AM ---------- Previous post was at 09:13 AM ----------
OK....didn't know there was an issue (or potential issue) with downgrading from CM9...thankfully I didn't install that as I'm not that fond of those roms in the first place....hope someone can figure out a solution if this is indeed bricking those who are trying to roll back to HC
Click to expand...
Click to collapse
So will this procedure wont brick?

PeteSeiler2010 said:
So will this procedure wont brick?
Click to expand...
Click to collapse
if your going to flash stock update.zips with cwm...make sure you take out the bootloader.blob and recovery folder and rezip it.
personally though i would wait. im sure acer will also be releasing an update to 4.0.4 and once source is avail the cm9 guys will have much more to play with. especially once the kernel source is avail.
Sent from my SGH-I897 using xda premium

HC bootloader and stock ROM...
ptesmoke said:
cm9 didnt cause anything...remember how u got cm9? you had an unlocked bootloader and a custom recovery...
now u flashed a stock image of ics? guess what...now your bootloader is locked again and your recovery is stock. 9 times out of 10 then someone tries to flash a stock hc rom that doesnt have the hc bootloader and this is where theyre stuck.
Click to expand...
Click to collapse
It looks as though there's no official update from HC to ICS for Canadian users (stuck at Acer_A100_2.013.03_pa_ca). Of course, there are ways around this, but that's not the point of my post here.
Now that I'm running an unlocked ICS bootloader, and custom recovery, alongside CM10... how would I revert to a stock HC (Acer_A100_1.014.08_COM_GEN1) to obtain service? Are the HC bootloaders not normally included in the stock HC ROM zip? I should add that, if able to revert to the aforementioned, I'm almost positive the option to update the device to the original build (Acer_A100_2.013.03_pa_ca) that it shipped with will present itself.
EDIT: Looks as though I may have been reading through some older posts as the tablet did OTA update to stock Acer ICS:
Image Version - Acer_AV041_A100_RV02RC01_PA_CA
Build number - Acer_AV041_A100_1.017.00_PA_CA
Image P/N - FM.S18A0.0AF

mixednuts said:
It looks as though there's no official update from HC to ICS for Canadian users (stuck at Acer_A100_2.013.03_pa_ca). Of course, there are ways around this, but that's not the point of my post here.
Now that I'm running an unlocked ICS bootloader, and custom recovery, alongside CM10... how would I revert to a stock HC (Acer_A100_1.014.08_COM_GEN1) to obtain service? Are the HC bootloaders not normally included in the stock HC ROM zip? I should add that, if able to revert to the aforementioned, I'm almost positive the option to update the device to the original build (Acer_A100_2.013.03_pa_ca) that it shipped with will present itself.
EDIT: Looks as though I may have been reading through some older posts as the tablet did OTA update to stock Acer ICS:
Image Version - Acer_AV041_A100_RV02RC01_PA_CA
Build number - Acer_AV041_A100_1.017.00_PA_CA
Image P/N - FM.S18A0.0AF
Click to expand...
Click to collapse
From your edit, is everything resolved? I know it can be tricky/dangerous to go from unlocked to HC.

Romman0 said:
From your edit, is everything resolved? I know it can be tricky/dangerous to go from unlocked to HC.
Click to expand...
Click to collapse
Actually, I didn't have to go to HC... just making sure that I could for warranty purposes. But, now that I know that there's an official ICS update for Canadian users there's no need to go back to HC... just need to go back to the locked ICS bootloader (again, only for warranty purposes).
Sent from my A100 using xda app-developers app

Related

[Q] Need help restoring non-boooting Nexus

Can someone link to a guide dealing with restoring a Nexus? It's stuck at the Google logo. I can get into bootloader mode with power+volume down, but it's not reacting when trying to navigate with the volume buttons after that.
I got a little bit tired of waiting for official firmware on my Galaxy S2 (even if CM was fun) so I got a Nexus yesterday - great price these days. It was the 4.0.1 yakju version as I'm in Western Europe.Unlocked and rooted with Root Toolkit v1.4 after which I wanted to install 4.0.4 using this guide. Got as far as flashing system.img and then the above happened.
All I want is to get back to working stock so that I can flash 4.1. Have no data on the device so a factory reset is no problem.
Much appreciated.
Nitsson said:
Can someone link to a guide dealing with restoring a Nexus? It's stuck at the Google logo. I can get into bootloader mode with power+volume down, but it's not reacting when trying to navigate with the volume buttons after that.
I got a little bit tired of waiting for official firmware on my Galaxy S2 (even if CM was fun) so I got a Nexus yesterday - great price these days. It was the 4.0.1 yakju version as I'm in Western Europe.Unlocked and rooted with Root Toolkit v1.4 after which I wanted to install 4.0.4 using this guide. Got as far as flashing system.img and then the above happened.
All I want is to get back to working stock so that I can flash 4.1. Have no data on the device so a factory reset is no problem.
Much appreciated.
Click to expand...
Click to collapse
Just fastboot flash Nexus Factory Images if you have no problem with wiping your data. That's odd that your bootloader won't respond to volume buttons... I might say try reflashing the bootloader and recovery, but since your bootloader is acting up right now, I'd go to flashing the factory images first, and if that doesn't work, try reflashing just bootloader and a custom recovery.
Nitsson said:
Can someone link to a guide dealing with restoring a Nexus? It's stuck at the Google logo. I can get into bootloader mode with power+volume down, but it's not reacting when trying to navigate with the volume buttons after that.
I got a little bit tired of waiting for official firmware on my Galaxy S2 (even if CM was fun) so I got a Nexus yesterday - great price these days. It was the 4.0.1 yakju version as I'm in Western Europe.Unlocked and rooted with Root Toolkit v1.4 after which I wanted to install 4.0.4 using this guide. Got as far as flashing system.img and then the above happened.
All I want is to get back to working stock so that I can flash 4.1. Have no data on the device so a factory reset is no problem.
Much appreciated.
Click to expand...
Click to collapse
Have a look at posts 1 and 2 in the "flash" link in my sig.
BTW, volume down and power is not the bootloader. You need to press volume up and volume down and power.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Have a look at posts 1 and 2 in the "flash" link in my sig.
BTW, volume down and power is not the bootloader. You need to press volume up and volume down and power.
Click to expand...
Click to collapse
Perfect, that guide worked. Installed 4.0.4 and then 4.1. The root guide does not work on 4.1 however, but I'll find another one. Many thanks.
Do you know if the current 4.1 image is gold by the way?
Nitsson said:
The root guide does not work on 4.1 however, but I'll find another one. Many thanks.
Click to expand...
Click to collapse
The file in post #2 of that thread should work for 4.1
Nitsson said:
Do you know if the current 4.1 image is gold by the way?
Click to expand...
Click to collapse
Should be. If not, it should get an OTA update as well.
efrant said:
The file in post #2 of that thread should work for 4.1
Click to expand...
Click to collapse
Nope, I follow it to the letter; CWM installs fine, as does Superuser, but I don't have root access after reboot. Any ideas are appreciated.
efrant said:
Should be. If not, it should get an OTA update as well.
Click to expand...
Click to collapse
Perfect. Assuming the next Nexus is a nice step forward I hope to stay on this platform for a while.
Nitsson said:
Nope, I follow it to the letter; CWM installs fine, as does Superuser, but I don't have root access after reboot. Any ideas are appreciated.
Perfect. Assuming the next Nexus is a nice step forward I hope to stay on this platform for a while.
Click to expand...
Click to collapse
just flash any custom rom via your recovery. youll boot up with root access.
simms22 said:
just flash any custom rom via your recovery. youll boot up with root access.
Click to expand...
Click to collapse
Thanks, but the whole reason I got the Nexus was to get the pure Google experience, the latest updates, and to stop playing around with custom ROMs
Nitsson said:
Thanks, but the whole reason I got the Nexus was to get the pure Google experience, the latest updates, and to stop playing around with custom ROMs
Click to expand...
Click to collapse
stock, rooted, jellybean should be good for you then. bigxies jellybean rom in the development section should work out good for you. or you can try this flasable updated su https://www.box.com/shared/acb928d8edd41b91a6c9
Nitsson said:
Nope, I follow it to the letter; CWM installs fine, as does Superuser, but I don't have root access after reboot. Any ideas are appreciated.
Click to expand...
Click to collapse
That is because you didn't read what I posted above. You need to flash the file in post #2, not the one linked in post #1.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
stock, rooted, jellybean should be good for you then. bigxies jellybean rom in the development section should work out good for you. or you can try this flasable updated su https://www.box.com/shared/acb928d8edd41b91a6c9
Click to expand...
Click to collapse
But bigxie's ROM is NOT stock...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
But bigxie's ROM is NOT stock...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ok, technically it not, since JB isnt out yet. im using his original version 1, so its close to where stock would/should be. but, that is just a guess on my part since, again, there is no official stock jellybean. theres only the google i/o preview version
simms22 said:
ok, technically it not, since JB isnt out yet. im using his original version 1, so its close to where stock would/should be. but, that is just a guess on my part since, again, there is no official stock jellybean. theres only the google i/o preview version
Click to expand...
Click to collapse
That's not really what I was trying to say: it is stock, but it's deodexed, which makes it not stock, and it won't be able to apply any future OTA updates.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
That's not really what I was trying to say: it is stock, but it's deodexed, which makes it not stock, and it won't be able to apply any future OTA updates.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
truth
efrant said:
That is because you didn't read what I posted above. You need to flash the file in post #2, not the one linked in post #1.
Click to expand...
Click to collapse
Flashed with CWM-SuperSU-v0.92-mod which worked like a charm. I now have both Superuser and SuperSU installed, with the latter taking precedence, but I guess that doesn't matter.
Nitsson said:
Flashed with CWM-SuperSU-v0.92-mod which worked like a charm. I now have both Superuser and SuperSU installed, with the latter taking precedence, but I guess that doesn't matter.
Click to expand...
Click to collapse
sweet, i thought it would. use root explorer to go to /system/app/ and delete the superuser app
simms22 said:
sweet, i thought it would. use root explorer to go to /system/app/ and delete the superuser app
Click to expand...
Click to collapse
Funny, but the superuser app is nowhere to be found in the list at /system/app/.

Jb 4.1

To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Jpcsilva said:
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Click to expand...
Click to collapse
Flash your phone back to stock... then do the ota update... profit...
Sent from my Galaxy Nexus using xda app-developers app
Everything must must be bone stock to install an ota.
Jellin' like a felon
The issue at hand here is that you have a custom recovery. I can't say that if you remove CWM that you'll be able to OTA update, but that's at least what was the problem there. Now, if you want to keep all your apps and update to the OTA jelly bean instead of the Google I/O preview build, you can flash this here: http://forum.xda-developers.com/showthread.php?t=1737849
Follow the instructions on that post to update. This is what I did and it worked perfectly.
Camera not working after JB update!
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
nishantbhatia84 said:
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
Click to expand...
Click to collapse
What Rom? Custom or stock
What kernel? Custom or stock
Sent from my Galaxy Nexus using Tapatalk 2
And how do i do that? I really dont know how to flash it
Sent from my Galaxy Nexus using xda app-developers app
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
nishantbhatia84 said:
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
first try factory reset, otherwise yes go back to stock ics and check.
Jp182
atifsh said:
first try factory reset, otherwise yes go back to stock ics and check.
Click to expand...
Click to collapse
But going to factory reset will not remove the cwm recovery... right? If i go to factory data reset on my phone ( remember i am using a 4.1 rom) will it go back to ics and delete all roms / root? Cause this sounds like the best way to do it, but you were the first one that said that. Bought my phone from Amazon unlocked ( do you guys think it is gonna update?)
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
I don't get it. What did you do? Factory reset? Installed the stock?
Sent from my Galaxy Nexus using xda app-developers app
HELPPPPPP
nishantbhatia84 said:
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PLZ, tell me!! If I do the factory reset is it gonna remove CWM, and all stuff i have installed?
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ok
phazerorg said:
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Sorry man, I know i am not giving a lot of information, but that's cause i really don't know. I did a random "how to update your galaxy nexus to 4.1" tutorial, and i don't even remember where...... I just know the links i download were from here.
So what i am going to do:
1: Factory data reset
2: I think it's going back to ICS
3: Just do the normal system update that should just pop up.
My only fear is if the phone does not ask for update.
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Factory reset factory reset
phazerorg said:
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Click to expand...
Click to collapse
I want to restore it VIA FACTORY RESET. Cant i?
Jpcsilva said:
I want to restore it VIA FACTORY RESET. Cant i?
Click to expand...
Click to collapse
No, that will just wipe data. You'll have a clean phone, but with the same ROM you currently have. The phone doesn't keep a copy of the stock firmware hidden away or anything like that. Efrant's guide is the proper way to restore everything back to stock.

Locked Bootloader Situation in LG's ICS

As many have come to discover, with ICS, LG has gone over to the dark side and locked their bootloader.
So what does this mean for us P93X users? This means that if we upgrade to ICS via the official LG tool or by using an LG ICS .kdz, our bootloader is now locked. This has caused problems for newer users who have managed to gain root access, only to subsequently soft-brick their phone when they attempt to remove default apps or install CWM via Rom Manager.
So what's the good news? It is possible to downgrade to Gingerbread using the Unbricking Guide stickied in this forum. Once on Gingerbread, if a user so desires, our very own HO!NO! has created a CWM-flashable version of official AT&T ICS that will not overwrite the device with the locked ICS bootloader.
The purpose I would like this thread to serve is a place to discuss the nature of the bootloader on the P93X and to answer questions about how it works (in addition to the warning above that I hope new users see). Here are some questions I have:
Which partition is it on our device?
Is it possible to simply overwrite a phone on ICS with a Gingerbread firmware without having to unbrick?
Can we get a collection started of various bootloader images for all the devices (i.e. P930 AT&T/Bell, P935, P936, SU640)?
If my suspicion is correct, anybody who has gone through the Unbricking Guide is currently using the SU640 Gingerbread bootloader, including myself. It's possible there are no differences in the various devices' Gingerbread bootloaders, but from available evidence, I do not believe that is the case. We already know, for example, that anybody who has never unbricked their phone is not able to successfully flash and use the CWM-flashable ICS and ICS leak that HO!NO! has released.
Thoughts?
is there a plan to, or can the boot loader be overwritten in leaked ics?
I rooted my lg nitro and then bricked it within an hour. I flashed the leaked ics and rooted. Like we know cwm and cwm touch don't work with ics. I went back to ginger bread so I could backup my rom and flash custom rooms. I like this flexibility; however, I hate how fast my battery drains. I have tried all roms out here. All suck the juice within hours. ics leaked version With locked boot loader rooted lasts all day. Even listening to music with head phones.
Tried jellybam
Nitrogen with ho!no!
Hono
Cm10
Cm9
And quite a few others I can't remember right now.
Is there a way to get battery life like I get from leaked ics on any of these roms.?
Sent from log nitro rooted nitrogen with gapps
He he dont worry it is normal.....why?
Because its ICS!!!!
The spectrum users at androidforums figured out a way to replace the locked boot loader with the unlocked one. Nobody has done this for the nitro yet but I am sure it is possible. All we need is a dev to make it happen. Unfortunately I am not willing to install a locked boot loader on my phone so I cannot do it. Perhaps another dev can do this?
does spectrum share same partition layout as nitro hd?
I think the unlock process should be as easy as some dd script if we can locate the right partition(s).
arda99 said:
does spectrum share same partition layout as nitro hd?
I think the unlock process should be as easy as some dd script if we can locate the right partition(s).
Click to expand...
Click to collapse
It is not the same but very close.
It is a bit more complicated than a dd script, you also need a unlocked kernel (such as the cm9 kernel).
Contact Neph81 and death2all110 at AF, they are the devs who did this.
Ho!no! did it.
tdmcode said:
It is not the same but very close.
It is a bit more complicated than a dd script, you also need a unlocked kernel (such as the cm9 kernel).
Contact Neph81 and death2all110 at AF, they are the devs who did this.
Click to expand...
Click to collapse
Ho!no! did it. I flashed this modified leaked version. MY battery last for ever now. Thank you HO!NO!
CWM touch works well with this release. The only thing I did not like about the leaked release was the locked boot loader.
NO MORE locked bootloader thanks to HO!NO!. There is also a V20 that was released. Have not tried that one.
I appologize because the answer was already on XDA.
Though my status say junior, I have used this site for my own education for years, but nevr needed to ask any questions until recently. lol
http://forum.xda-developers.com/showthread.php?t=1684032
tdmcode said:
It is not the same but very close.
It is a bit more complicated than a dd script, you also need a unlocked kernel (such as the cm9 kernel).
Contact Neph81 and death2all110 at AF, they are the devs who did this.
Click to expand...
Click to collapse
I searched and found this thread
http://androidforums.com/spectrum-a...oot-cwm-lg-spectrum-4g-ics-linux-install.html
its rooting with qemu + dd some images. But I don't understand why need so many images(and the exact purpose for each of them).
and I don't get the "unlocked" kernel part since we can use stock kernel+GB bootloader on P930.
Anyway, its as easy as some dd script but it might be too risky to figure out the whole thing.
I don't understand why you would want to spend the time and effort on this project when the unbricking method in my signature allows you to restore the P930 gingerbread bootloader, which you can then install CWM on top of and flash your roms all you want.
Just curious, can someone outline why this would be worth the time investment?
hereric said:
I don't understand why you would want to spend the time and effort on this project when the unbricking method in my signature allows you to restore the P930 gingerbread bootloader, which you can then install CWM on top of and flash your roms all you want.
Just curious, can someone outline why this would be worth the time investment?
Click to expand...
Click to collapse
because its more easier than yours.
can be done in one simple shell/batch script.
skoobbarnes said:
Ho!no! did it. I flashed this modified leaked version. MY battery last for ever now. Thank you HO!NO!
CWM touch works well with this release. The only thing I did not like about the leaked release was the locked boot loader.
NO MORE locked bootloader thanks to HO!NO!. There is also a V20 that was released. Have not tried that one.
I appologize because the answer was already on XDA.
Though my status say junior, I have used this site for my own education for years, but nevr needed to ask any questions until recently. lol
http://forum.xda-developers.com/showthread.php?t=1684032
Click to expand...
Click to collapse
sorry but its unrelated. cwm roms don't touch the bootloader part and to have cwm working, you need an unlocked bootloader to begin with.
here we're talking about how to replace a locked bootloader with an unlocked one, so one can install cwm and continue, including installing the rom you mentioned.
arda99 said:
because its more easier than yours.
can be done in one simple shell/batch script.
Click to expand...
Click to collapse
How is it easier ? You still have to install CWM to flash the zip so I do not see the advantage of this either.
Nz
notzippy said:
How is it easier ? You still have to install CWM to flash the zip so I do not see the advantage of this either.
Nz
Click to expand...
Click to collapse
one is like 10-20 steps, another is as easy as 1 click...
and they're the same because cwm is installed regardless???
root then uninstall systemapp
wujianheisheng said:
root then uninstall systemapp
Click to expand...
Click to collapse
This gets rid of the bootloader lock?
And nothing else of importance?
dukkitdalaw said:
This gets rid of the bootloader lock?
And nothing else of importance?
Click to expand...
Click to collapse
That just bricks you...
Sent from my LG-P930 using XDA Premium HD app
arda99 said:
because its more easier than yours.
can be done in one simple shell/batch script.
sorry but its unrelated. cwm roms don't touch the bootloader part and to have cwm working, you need an unlocked bootloader to begin with.
here we're talking about how to replace a locked bootloader with an unlocked one, so one can install cwm and continue, including installing the rom you mentioned.
Click to expand...
Click to collapse
I seem to have missed it. But where is this shell/script located?
Other than the unbricking method.
hereric said:
That just bricks you...
Sent from my LG-P930 using XDA Premium HD app
Click to expand...
Click to collapse
Yes. I was being sarcastic.
That guy is going to ruin someones day with advice like that.
dukkitdalaw said:
I seem to have missed it. But where is this shell/script located?
Other than the unbricking method.
Click to expand...
Click to collapse
It doesn't exist... yet. At least, not for the P93x/whatever else is covered in the Nitro Forum.
Nvm Arda99
I see the link
Hello, I was just reading this post because of my Lg optimus G.
I know that they are two different devices but my question is about LG locking bootloader for our devices.
Does the bootloader relock it self if I flash stock KDZ file?
I was wondering how to get it back to stock so I can get the warranty support from LG.
Thank you
jnhsd0319 said:
Hello, I was just reading this post because of my Lg optimus G.
I know that they are two different devices but my question is about LG locking bootloader for our devices.
Does the bootloader relock it self if I flash stock KDZ file?
I was wondering how to get it back to stock so I can get the warranty support from LG.
Thank you
Click to expand...
Click to collapse
Flashing kdz will replace all partitions, and return your phone to 100% stock.
Sent from my LG-LU6200 using xda app-developers app

[ROM] HO!NO! P930 Bell Official V20e CWM-Flashable!

This is the Official ICS V20e from Bell
ClockWorkMod flashable
I did not remove or add anything this is really stock.
Enjoy!
signed_HO!NO!_P930_V20e-CWM-Flashable.zip
It's rooted, though, right?
Thanks! Hoping to give it a try either tomorrow or Saturday.
Do you have to unbrick your phone in order for it to work? Like the other official ICS releases?
@RealyPssd,
If you have ever done the unbricking guide in the past, you're good to go, just flash via CWM.
Malnilion said:
It's rooted, though, right?
Click to expand...
Click to collapse
yes for sure it is root
I haven't ever unbricked before.
Then yes, you will likely end up with a non-booting phone (but a still working CWM) if you flash this rom. I'm currently trying to figure out which partition the bootloader is on the Nitro HD so that we might just be able to give users like yourself a bootloader that will allow you to boot these ICS roms with CWM. Right now it appears the SU640 Gingerbread bootloader, which is flashed when you do the unbricking guide, is the best bet for this. It'd be nice if we could also get one of you guys to donate your stock Bell/AT&T bootloaders once we figure out which partition it's on.
Malnilion said:
Then yes, you will likely end up with a non-booting phone (but a still working CWM) if you flash this rom. I'm currently trying to figure out which partition the bootloader is on the Nitro HD so that we might just be able to give users like yourself a bootloader that will allow you to boot these ICS roms with CWM. Right now it appears the SU640 Gingerbread bootloader, which is flashed when you do the unbricking guide, is the best bet for this. It'd be nice if we could also get one of you guys to donate your stock Bell/AT&T bootloaders once we figure out which partition it's on.
Click to expand...
Click to collapse
The only issue with this is I'm not sure if it's safe to overwrite the bootloader using a method other than LG's tools. Or even if the phone will let you overwrite it using any other method.
That's very true, it's somewhat risky.
Flashing this on my phone right now = after selecting reboot in CWM the LG logo pops up briefly then I'm brought back to CWM automatically.
So if i flash with the LG tool it'll work fine? I'll just have to unbrick if i want to switch ROMS?
And if i unbrick now, this should work fine with CWM staying installed?
Just follow the 40 steps of the unbrick guide and all should be fine?
Which guide should I use?
http://forum.xda-developers.com/showthread.php?t=1784709
or
http://forum.xda-developers.com/showthread.php?t=1412367&page=1
Any possibility to get the battery life on ICS similar to HO!NO! CM9?
lilbluemirage said:
Any possibility to get the battery life on ICS similar to HO!NO! CM9?
Click to expand...
Click to collapse
4% during night with 3G enabled on v20e. Is that bad?
RealyPssd said:
Flashing this on my phone right now = after selecting reboot in CWM the LG logo pops up briefly then I'm brought back to CWM automatically.
So if i flash with the LG tool it'll work fine? I'll just have to unbrick if i want to switch ROMS?
And if i unbrick now, this should work fine with CWM staying installed?
Just follow the 40 steps of the unbrick guide and all should be fine?
Which guide should I use?
http://forum.xda-developers.com/showthread.php?t=1784709
or
http://forum.xda-developers.com/showthread.php?t=1412367&page=1
Click to expand...
Click to collapse
Follow Malnilion's advice, unbrick first. I was in the same situation (logo-CWM sequence) until I unbricked.
Both guides work fine, only problem I had was rooting using ROOT.bat. Didn't work and
I don't know why. So i rooted using SuperOneClick 2.3.2 from Machzalet's guide.
After unbrick no problem flashing this ROM in CWM, everything wen smootly
glc011 said:
Follow Malnilion's advice, unbrick first. I was in the same situation (logo-CWM sequence) until I unbricked.
Both guides work fine, only problem I had was rooting using ROOT.bat. Didn't work and
I don't know why. So i rooted using SuperOneClick 2.3.2 from Machzalet's guide.
After unbrick no problem flashing this ROM in CWM, everything wen smootly
Click to expand...
Click to collapse
Once you flash this rom, do you lose CWM?
veryluckyguy said:
Once you flash this rom, do you lose CWM?
Click to expand...
Click to collapse
No, you don't.
Well I unbricked and such don't think I'll be sticking with this ROM.
Is there any way to disable the search bar at the top using the stock launcher?
Thanks for the CWM version though HONO.
Going to give CM10 nightyls a shot.
RealyPssd said:
Well I unbricked and such don't think I'll be sticking with this ROM.
Is there any way to disable the search bar at the top using the stock launcher?
Thanks for the CWM version though HONO.
Going to give CM10 nightyls a shot.
Click to expand...
Click to collapse
You won't be disappointed with CM10. I'm not.
Sent from my LG-P930 using xda premium
I'm visiting Israel for a month and neither stock nor CM9 nor CM9 Full Throttle work here. The Nitro's frequencies are exactly the same as my GS2, but the GS2 works perfectly. There are several carrier networks here, each using a slightly different combination of frequencies, but the GS2 works with all of them and the Nitro with none of them. It works perfectly on AT&T in the US. It is SIM unlocked, of course.
Is this likely a problem with the modem? Will the ROM in this thread likely fix my issue because it's meant for Bell (presumably a non-American carrier)? Any other suggestions of what I can do to get the phone to work on a foreign (but frequency-compatible) carrier?
good job!!
Sent from my LG-SU640 using xda premium
Everything is smooth, but the phone gets stuck for a few seconds and then goes into some sort of deep sleep. I need to do a battery pull every 2 hours.

[Q] Tmobile update on stock rooted rom

Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
When it is rooted even if you try to use the OTA update it won't let you, while rooted, you could alternatively flash the update via ODIN w/ root support. Or try some of the sweet ROMs available , the reason I switched to a custom ROM because I was going to have to erase my phone anyway if I wanted to update, so I thought why not just try a custom ROM?
I use LiquidSmoothRC7, but if you want a more stock feel with touchwiz you can try Wicked, Wicked stays true to the "official stock ROMs" and just adds roots and tweaks the ROM to make it as stable as possible
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
OR you could listen to this dude
cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2
zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA
cobraboy85 said:
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA
Click to expand...
Click to collapse
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app
Towle said:
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Some of those 10 partitions that are getting rewritten are... for one, your recovery... so that makes 9 actually...
My point is, and I'm not trying to be argumentative in any way, merely objective, is that unless it is reformatting the ext4 partition to new file structure (for example) there should be no need to do this. I suppose I would ask somebody to define in depth "rewritten" and how exactly this is being done and why. Every single update we have had since the release of this device I have not once updated my own device with odin merely to put it back to stock. And I have run into zero issues. Seems like a waste of time to me unless there is something highly critical being restructured entirely. In the end, its all the same disk, and disk size for any given partition.
---------- Post added at 05:51 AM ---------- Previous post was at 05:47 AM ----------
neim81094 said:
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
If you are on LH2, with that same baseband, I would go ahead and update your baseband via docs packaged update in his thread, and just reboot, then move on to the jelly bean updates. Do a factory reset through recovery before you flash the JB ROM tho since you are coming from a completely different version of android.
zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.
Just stating my experience, I was rooted stock ics and ran the ota update. I was able to update, keep root and ran stock jelly bean without any problems at all.
Now I am running frosty jelly and still no problems at all. I am not saying for you to do it (dont want anyone blaming me) just stating that it can be done. Do whats most comfortable for you.
Sent from my SGH-T999 using xda app-developers app
jcbofkc said:
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.
Click to expand...
Click to collapse
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice
cobraboy85 said:
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice
Click to expand...
Click to collapse
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.
jcbofkc said:
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.
Click to expand...
Click to collapse
Totally dig it. And yeah, just want to know what exactly is being done differently in odin
cobraboy85 said:
Totally dig it. And yeah, just want to know what exactly is being done differently in odin
Click to expand...
Click to collapse
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999
neim81094 said:
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999
Click to expand...
Click to collapse
Sorry, I will clarify, I am curious to know why Odin is such a critical issue. I know how it works as far as it being a flashing tool
I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999
neim81094 said:
I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999
Click to expand...
Click to collapse
The file used to flash with Odin is much larger because it is a complete rom. The OTA is a patch that attempts to patch and modify existing files.
I basically said that on the last post not the one you quoted
Sent from my SGH-T999
Finally got the time to Odin Route66 Jelly bean.
Sent from my SGH-T999 using Tapatalk 2
Everything good?

Categories

Resources