Related
First, MODS: I apologize if this is posted in the wrong thread, but I can't find anything along the lines of help I need, and since I started here, I was thinking I'd end here... Please move if necessary.
So I have recently learned that not all Android devices are as easily rooted/modded as my EVO (rooted my GF's Optimus S, and ended up on the couch for months, and around the same time, rooted the Sprint SGT she got me for X-Mas, and have only gotten the Optimus S working again, but remain on the couch for bricking my SGT).
I am in dire need of help getting my SGT back to stock (if that's even possible) or at least back to rooted with a stock ROM. I rooted my SGT in preparation for the Honeycomb port (which was apparently a bust(?) and after flashing that port, then Boushh's AOSP ROM, I can boot to download mode (with neither Heimdall or Odin reognizing the device) or I can attempt to boot to recovery and get nothing but the Samsung splash.
I have all drivers installed, and I PROMISE I have learned my lesson, and should have never rooted to begin with, but if ANYONE could please help me get my SGT back, I would TRUELY appreciate it!
I have just recently gotten semi-familiar with ADB again (Optimus S fix) but I'm not really in a place to start pushing commands without guidance.
I'm sorry again if this is the incorrect thread, I didn't know where else to post, but I REALLY need help. We really couldn't afford the SGT to begin with, so I feel horrible that I've bricked it, and can't do anything with it anymore.
Sorry to be a gnat...
IP IHI II IL said:
I'm sorry again if this is the incorrect thread, I didn't know where else to post
Click to expand...
Click to collapse
Read HERE or HERE
IP IHI II IL said:
First, MODS: I apologize if this is posted in the wrong thread, but I can't find anything along the lines of help I need, and since I started here, I was thinking I'd end here... Please move if necessary.
So I have recently learned that not all Android devices are as easily rooted/modded as my EVO (rooted my GF's Optimus S, and ended up on the couch for months, and around the same time, rooted the Sprint SGT she got me for X-Mas, and have only gotten the Optimus S working again, but remain on the couch for bricking my SGT).
I am in dire need of help getting my SGT back to stock (if that's even possible) or at least back to rooted with a stock ROM. I rooted my SGT in preparation for the Honeycomb port (which was apparently a bust(?) and after flashing that port, then Boushh's AOSP ROM, I can boot to download mode (with neither Heimdall or Odin reognizing the device) or I can attempt to boot to recovery and get nothing but the Samsung splash.
I have all drivers installed, and I PROMISE I have learned my lesson, and should have never rooted to begin with, but if ANYONE could please help me get my SGT back, I would TRUELY appreciate it!
I have just recently gotten semi-familiar with ADB again (Optimus S fix) but I'm not really in a place to start pushing commands without guidance.
I'm sorry again if this is the incorrect thread, I didn't know where else to post, but I REALLY need help. We really couldn't afford the SGT to begin with, so I feel horrible that I've bricked it, and can't do anything with it anymore.
Sorry to be a gnat...
Click to expand...
Click to collapse
No worries buddy, I know how it feels, since you posted already here's how your proceed:
1. get Odin 1.7
2. if you want stock, go to samfirmware.com and download the ROM corresponding to your device
3. Bear in mind that most stock ROM are shipped with locked bootloader, if you don't care skip step 4/5
4. download super one click root from shortfuse.org
5. root your device and either get a ROM with removed bootloaders or get the bootloader patch by chainfire, found in this forum somewhere
6. While being in the "yellow" screen flash using odin
Hope this helps.
He has a cdma tab. Sprint right?
Try this: http://forum.xda-developers.com/showthread.php?t=969892&highlight=sprint+stock
As your last resort. If not go back to sprint tell them tab isnt switxhing on.
How about flashing a kernel that installs cwm?
Sent from my GT-P1000 using Tapatalk
As long as you flash the no modem software you are good. That is the key. No modem.
Probably a driver issue if it's not being seen in ODIN.
if its not seen it doesnt matter either, you turn off and turn on again, you'll see a black screen with some kind of logo, then I usually flash a rotohammer release, this is always the life saver
shoman24v said:
As long as you flash the no modem software you are good. That is the key. No modem.
Probably a driver issue if it's not being seen in ODIN.
Click to expand...
Click to collapse
Usually when having both, Odin and Heimdal installed, one of them needs to be removed...
RunTimeWorld said:
Usually when having both, Odin and Heimdal installed, one of them needs to be removed...
Click to expand...
Click to collapse
Yup. ODIN takes a separate driver that conflicts with heimdall and vice versa.
Sent from my SPH-P100 using Tapatalk
Hi I can't even enter download mode after my Odin update failed. It's just a black screen and when I plug it into the computer it's not recognised at all.
Any ideas on how to fix this?
Hi I found a similar article on androidforums.com so I thought id make one here as a lot of people still seem to not know how to flash basebands and go from there. Ill start from the beginning.
For those who don't understand what this is about.
Old Baseband = If you have the Stock Froyo (2.2) Android system on your phone then you have the OLD BASEBAND, and you do not need this unless you updated to past 2.2.2 then continue reading if you wish to root your phone the easy way.
New Baseband = If you updated to the Stock Gingerbread (2.3) Android System on your Optimus One, then you fit this category, Lg have implemented a new baseband in this update which makes any Roms based on the old baseband not function, as well as making it more difficult to root your phone
FLASHING OLD BASEBAND
If you're already on official Gingerbread version you will need to downgrade your version to Froyo 2.2.2 using KDZ Updater. This is because the new Gingerbread contains the new baseband, and the Froyo firmware is the old baseband.
To do this please go onto this link that contains kdz and the stock Froyo 2.2.2 Rom required to flash. The reason you need 2.2.2 is its the easiest and proven version to work with Gingerbreak to root your device.
http://forum.xda-developers.com/showpost.php?p=13396506&postcount=1
Notice: If by some ACCIDENTAL reason, your phone gets stuck in EMERGENCY MODE during flashing, follow the instructions on this link how to use KDZs functions to continue flashing the firmware you downloaded in Emergency mode.
http://forum.xda-developers.com/showthread.php?t=1275523
FLASHING NEW BASEBAND
The Kdz File for new baseband is below, use the same method as above only using the v20G .kdz file instead of the 2.2.2 v10E update.
This will update your phone to the official LG 2.3 firmware, in which the new baseband originated.
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/ANEUBK/V20g_00/V20G_00.kdz
If then stuck on LG Logo OR boot animation, try pulling and putting in your battery, turning on your phone and holding down volume down and home key, this should reset your phone to factory and then you will be able to boot into the stock gingerbread.
ROOTING
The easiest way to get root privileges on Old Baseband (2.2.2) firmware device is by using Gingerbreak apk. Just download it, install it and run it.
forum.xda-developers.com/attachment.php?attachmentid=600902&d=1305802958
To get Root access on the New Baseband (2.3.3) use SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
Or direct link to the latest version
forum.xda-developers.com/attachment.php?attachmentid=778098&d=1320906597
Make sure, after you download the program, you go into your cmd, then go into the ADB folder, drag the ABD exe file into command prompt, delete the .exe part and add devices, so it look like this
OR
Download the ADB.zip attachment on this post, EXTRACT it so cmdXP and cmd7 are located inside the ADB folder in the Superoneclick directory, and run either version, depending on your windows version (This links you directly into ADB app, instead of manually dragging ADB.exe int cmd, really its just for your convinience.)
Then all you have to do is type the following lines.
adb devices
press enter
adb shell
press enter
then type in the following directly after
echo 1 > /data/local/lge_adb.conf
press enter.
Then go into Superoneclick.exe, select auto method and run root, this should then eventually root your device.
***WARNING***
Some Antivirus softwares will detect Superoneclick as a Virus.
IT IS NOT A VIRUS, just the types of exploite code it uses makes some antivirus software think of it as malicious. Just disable your AV for 5 mins before you extract Superoneclick.
RECOVERY
There's two popular custom Recovery versions for O1 - AmonRa and ClockworkMod
The easiest way to flash ClockworkMod Recovery is by downloading ROM Manager app from the Market (free or donate version doesn't matter) and choose to flash the latest recovery version and choose the option to Reboot in Recovery mode.
For Other Recoveries including Amonra there are a few links, but here is the one that has flashable zips
http://forum.xda-developers.com/showthread.php?t=1523050
Just flash the zip files in Clockworkmod recovery menu, after you install that through Rom Manager if you wish to use a different recovery.
Now that you got the right baseband + your device is rooted and loaded with a custom recovery you may install any Rom you wish that is based on the correct baseband such as
Mik_os 6.5.8 Cyanogenmod port (OLD BASEBAND).
http://forum.xda-developers.com/showthread.php?t=946354
[UNOFFICIAL][DEV/GEEKS-ONLY] Cyanogenmod 9 (Android 4.0.3)[BETA][NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1558213
OFFICIAL CYANOGENMOD Rom [NEW BASEBAND]
http://get.cm/?device=p500
Oxygen ROM 2.3.2 (Android 2.3.7)[NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1325386
Next time, search better
Also posted in wrong thread, this is developmentthread...
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
fundoozzz said:
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Guys i did a search and looked into the sticky how to, and the only thing about downgrading baseband is using LGMDP, and kdz is only "mentioned" as a tool for unbricking your phone and flashing old firmware, new users would not know to use kdz.
Also this is a universal guide to root ANY lg optimus one together with having the old baseband, without having to mess around with SDK or LGMDP.
All members have to do now is look at this thread and all their questions are answered hopefully...
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
I hear a lot about the new baseband making ROMs incompatible, but is there any advantage to the new baseband?
its not that they are making roms incompatiable, its that they are not designed for those Roms,
So far there has been no reports of any advantage having a new baseband, Lg engineers obviously decided on it for some reason, but the old baseband is more than fine, and in fact i have read several reports that with the new baseband gsm reception got worse in areas that they used to have fine reception, but thats all speculation.
Your best bet is to try for yourself, but if you want to make use of Roms such as miks cyanogen mod or others you have to use the old baseband.
There are other Roms available on the new baseband, so its upto you.
I suggest what rom you would like to install on your phone first, then pick the baseband it requires, as its only a simple flashing of your firmware.
Also note Gingerbreak.apk doesnt root any stock firmware past the 2.2.2 update.
Personally i pick the functionality and advantage of having a custom rom such as cyanogenmod over an update to the baseband
Does this guide work for Optimus T (LG P509) ? I have got one recently and currently using stock 2.2 on it. I don't know the difference between LG p500 and LG P509. I'm coming from T-Mobile G1 on which I'm using CM 7.1. Thanks for guidance.
Sent from my Dream/Sapphire using xda premium
Hi,
Doing a little search i found this thread
http://forum.xda-developers.com/showthread.php?t=960278
looking at it, i assume you can use this guide for p509, but i can not be 100% sure, try finding the t-mobile 2.2 kdz file, but yes not 100% sure the main difference.
deniso177 said:
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
Click to expand...
Click to collapse
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
As you already quoted it, i said that this method is different from Doks.
As for wiping all data completely, so its all brand new and neat, then try to fiddle around with internals and possibly have a bug result from it.
KDZ is what is used to UNBRICK your phone in the first place, so go do some research before posting unnecessary things.
Lastly how about you show some respect and keep your negative and rude comments to yourself, if you dont like this method dont do it, dont abuse people in the process.
terratrix said:
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Click to expand...
Click to collapse
And yep exactly, i personally prefer completely reinstalling something to make it work properly, then doing things dodgy.
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
ichigo200 said:
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
it means your phone is past the firmware update that gingerbreak works on,
as it says in the first post, use kdz and the file in the link to flash your phone to that firmware, and then gingerbreak will work
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
A warning to anyone tempted to do this. Like the original poster, I also have an LG Optimus T. I am technically savvy (15 years IT experience) and I followed the directions to the letter, but the end result is a bricked, unrecoverable phone. Had I known the risks involved, I would have been perfectly content with Froyo and waited for the official upgrade to arrive.
Here is how mine failed: during the kdz update process, while the phone was on the "Emergency Mode" screen, the kdz updater program threw an exception and crashed. This caused the phone to be permanently locked in emergency mode. The buttons are unresponsive and the only way to turn it off is to remove the battery. With the battery in, it immediately goes to the emergency screen. No combination of button presses (eg, hard reset) does anything. The computer will still see the devices but only if I remove the battery and start the phone up by inserting the USB cable.
I have tried every method for recovery I could find including the following. In each case, I tried it with the modem device listed in device manager both disabled and enabled, as instructed in other recovery threads I found.
Flashing the original .kdz ROM in emergency and cs_emergency modes. When I did, it failed with an exception 4008.
Flashing the original .dz ROM with all of the tools I could find. LGMDP and LGDP2 could see the phone's COM port but beyond that, they could not communicate with the phone in any way. I couldn't even retrieve the IMEI number.
Updating the phone with the LG update software. It actually detects that the phone needs an update and starts to do one but it fails at the point where it tries to communicate with the phone.
Based on other posts I found for the same problem, I believe the phone is completely unrecoverable. I spent over six hours trying to solve the problem and I'm kicking myself for even trying this. I have put in a repair claim with LG and I'm waiting for instructions on how to proceed.
I would not recommend you try this unless you are not worried about destroying your phone. I imagine most installs go without a hitch but if the buggy kdz updater software crashes like it did for me, your phone will likely be bricked permanently.
Click to expand...
Click to collapse
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
In short, don't mess with KDZ unless you really have to.
Click to expand...
Click to collapse
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
I have used KDZ more than 2 dozen times -.- Just used it again this morning. I never ended up with a bricked phone mind you. They favour LGMPD since it's more updated, while KDZ is a little old but still very good.
There is a fairly equal share of bricked phones using LGDMPD, eventhough they got it back by using other people's NV2, they need to hope they are lucky to escape the long arm of the law.
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
Mate your the one who clearly doesnt get it.
And i read your post on androidforums, you even managed to brick your phone installing custom recovery, clearly your phone software is buggy, not kdz, kdz is capable of recovering while in emergency mode as well, but of course there are freak accidents.
EVERYTHING has a WARNING.
Every single Rom, Kernel, Recovery also carry a chance of bricking your phone.
I have used Kdz dozens of times and never had a problem with it, in fact, its what solved my problems in the first place.
And exactly wat terra said, the way LGDMPD works can also cause bricked phoes or taking shortcuts to make things half work.
You have to know what your doing, and follow instructions TO THE WORD, and you should be fine, if your going to skim read then you brick your phone doing the simplest of tasks (such as repeatedly flashing zips without reloading recovery...)
I will always prefer kdz as thats what the firmware comes with originally + i prefer doing clean installs any day.
Please Help...
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
shreyas.kukde said:
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
Click to expand...
Click to collapse
Hey mate, well no gsm is normally caused by the wrong baseband, so flashing back to the old one should fix the problem, try to re-flash the stock froyo given in the link on first post and see if that works, and if still no coverage then its a hardware problem and Lg should replace it for you, just dont forget to flash back to stock again if you rooted it, then they should fix it within the warranty.
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Sounds like the wrong kernel for the Rom was flashed.
What rom/kernel were you trying to flash ?
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
So you are going to need to flash the kernel that goes with the holicakes 2.6.35.14 rom.
Should be on the same site.
You can user CMD to fastboot flash boot boot.img and then the rom will boot.
From what I can tell on the rom page there is a kernel download section.
---------------------------------
Looks like he is instructing you to flash the kernel a different way than I have listed above, but both ways will work.
Riomaru said:
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Click to expand...
Click to collapse
DO NOT TRY, FACTORY RESET WILL DO ABSOLUTELY NOTHING AND MIGHT ACTUALLY MAKE THINGS WORSE.
With that out of the way, don't use the AIO software, use fastboot.exe and flash a boot.img to fix the issue.
Riomaru said:
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
Click to expand...
Click to collapse
No need to worry, you haven't had enough experience to know that it is normal. It is normal for the phone to not boot into the rom when the kernel doesn't match. since you have successfully flashed the kernel, you now need to boot into recovery (which I hope you have it installed at this point, if you have not, read how to do it and flash recovery) once in recovery, proceed to flash the HoliRaider rom and you'll be good to go.
in the same boat
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
newbroman said:
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
Click to expand...
Click to collapse
Did you install a recovery?
Also, it was not a good idea to try and install all different types of things once you thought it was messed up. Anytime you think you may have messed up, stop right then, read about the issue, and if you can't find the solution, ask a question. I think you can get out of this but some people aren't that fortunate.
vivid white screen
Thanks for the advice I will press on and do some more reading,
I can still get to CWM recovery and have tried restoring the backup image I made, with the same result.
During the kernal flashing process:-
- is the HTC dev lock supposed to be on or off? It is off and unlocked at the moment,
- is double flashing the kernal what is meant by the instruction 'if this is the first time you flash a kernal, make sure to reflash it', or as is suggested in esloan's post on this thread your supposed to flash a matching rom instead?
Thanks
You did the right thing by flashing the kernel twice. That is what those directions said. After you flash the kernel twice the next step would have been to flash a rom. I believe it is better to use the fast boot commands for doing this entire process. It sounds like you are still on the holicakes kernel.
What recovery do you have? 5.5.4 or WCX Recovery? You will have better results with WCX Recovery. Also watch this video:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
That is by randog. He did a great video and he shows you how to install everything without a program. Do you have the holiradier rom on your phone?
I was on the CWM recovery.
Thanks for the link to Randog's video, I now have a working phone again.
The major difficulties I had was finding wildchild's webpage with the links shown on the video, mainly because searching for wildchild illuminati took me to a forum with no links to any thing vivid, until you register.
I was also a little worried that I wasn't getting ICS in the ATT_ generic rom, but I needn't have. The key seemed to be locking the phone again and running wildchild's PH39IMG.zip. After that the security warning on the Hboot screen disappeared.
I almost messed the rom flashing part. Randog's vivid does this really quickly, my phone was a good 3 minutes behind and the progress bar was stuck around the 10% way after his phone had finished.
Like Randog says in the video follow the steps and you wont brick and you'll have a working phone.
Thanks megatronisabeast
Glad you got it. Sorry, forgot to give out the link.
Sent from my HTC PH39100 using XDA
Afraid to screw up any further
Htc vivid. 1.2dualcore.ICS.*
unlocked boot loader.
Used all in one vivid *toolkit 2.1
http://forum.xda-developers.com/showthread.php?t=1498003.
There were two choices. After boot loader unlock, which I had already done. Using right reading logic, I went to the "next step". Didn't realize ICS meant ice cream sandwich. Dumbass. I used CWM 5.5.0.4. Then I tried to to update the kernel, to*Holicakes2.6.35.14. For some unknown reason. The result is the white screen of death.
.*
I have access to hboot. As well as the recover menu which has a backup and restore option.
NAND restore clockworkmod backup, is available. I'm not sure how proceed.*
At the bottom of the screen:*
RA Revamped
Build: made for the WCX ILLUMINATE SERIES by GINM
I studied quite a bit. Too dumb to get a clear picture of the necessary steps before I began, I guess. Again, what a Dumbass.
I *need a better understanding of the process.
I didn't know about the super guide until it was too late. Rather, I did not understand I had seen the super guide when I saw it. It was from December, called a Holliday guide, so I didn't read it. There were so many guides, it confused me pretty throughly. Sheesh.
I have the htc white screen, reboots every three minutes or so.
I would really appreciate someone who knows to give me some clarification on these issues.
I understand a lot of these issues have been dealt with in this thread. I'm just really apprehensive.
I hope I posted this in the right place.
Thanks in advance,
Microbot2
Microbot, you have done pretty much what I did. If you follow megatronis a Brady's advice you will have a working phone. In fact I'm using it right now. Use the generic att zip an you will have ICS less the ATT bloatware.
Okay mircobot, I am home and can help you. Here is what you should do:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
Watch that video. Shows you what you will need to do to get everything working again.
The next thing, you need to download all of the files you will need for getting your phone working again. I would recommend going here:
http://www.wcxxperia-nce.com/index.php
You will have to register to see the vivid forums.
Next decide if you want to be able to tether (generic build) or if you want stock based rom (ATT vivid ics).
Download the zip file. Follow the instructions in the video and should get you up and running in no time. That would be the easiest way in my opinion.
If you can't get it figured out or need more help just post here and we will try to assist.
Microbot2--vivid
Hey guys, thanks for the prompt reply's and your general bad-assness.
I just woke and will Start on the instructions.
Megatronisabeast, really appreciate it. Newbroman, thank you.
I already feel considerably less worried about this already. I'll let you know how it works out.
microbot2_no PH39img.zip
Note: I updated to ICS from att before I unlocked the bootloader, which is still locked as now the phone can't be seen by the program.
Megatronisabeast, thanks for the link to the video. I am a little closer to understanding now. Unfortunately, I don't have direct access to the internal storage, like the guy in the video did. and I couldn't discern the website URL and he never tells you directly, except for "goto wildchilds site" which i couldn't locate.
I now know that I have access to wildchildes recovery. Unfortunately, I can only see the internal storage if I use WC recovery, ("windows wants to format it") then goto USB-MS. Otherwise the computers don't see it when its plugged up. It says "device not found when I try to do something in AIO_toolkit 1.2 Don't know if that helps.
I did find the wcxrecovery.img
It appears that you have to have access to internal storage to load an image to it. PH39img.zip, which I don't have. I can't seem to find the wildchild ICS image, either. when I start my phone, it looks for the ph39img.zip, doesn't see it, goes to the white screen.
I don't understand how to get the image back,Rather, how to access the internal storage again. is PH39img is the same thing as the ROM? Do I have to load PH39IMG.zip and the wilchild_vivid_ICS.ROM, which, again, I can't seem to find.
This feels like a comedy of errors. I wish I would have studied longer. I usually do. THEN, I find "newbie_proof" all in one toolkit.
I Just wanted it rooted. All I had to do was click "root" instead of "kernel". Man, what was I thinking?
If only I had taken the Red Pill.
Thanks again,
Look at my post above, the link for wild Childs site is there. You have to register to see the vivid forums. That is also where you will download the files needed to set up the ROM, etc. You won't need the Ph39.img since you already have ics. That is for the bootloader. You can actually send a file to your phone in the recovery. since you already have recovery you would need to download the Android sdk tools, so you will have fastboot. You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery. Sorry these directions aren't better, I will try to assist more when I get home, Swyping right now.
Sent from my HTC PH39100 using XDA
Microbot,
The wildchild files you need are in the first link Megatronisabeast cites
wcxxperia-nce.com/index.php (I'm a newbie and cant post the full web address). You have to sign up to the forum to access the files. The vivid forum will appear once you have registered.
The PH391IMG.zip is not your normal PH39img.zip you have to use the one contained in the WCX_generic_ATT.zip on the WCX vivid forum page. You also need to relock the phone. You are probably better off using the fastboot and the windows command prompt for this.
Can you boot into recovery at all?
Do you have another phone? you could use that to copy the PH39img.zip over. Thats what I did.
Mcrobot2---
Hi guys,*
Here is what I think I know:
HBOOT is a bootloader, *like a BIOS.
PH39img.zip is the boot file. Like PH39IMG.zip which appears to be a modified version for WC.
Kernel *is the memory and CPU manager.
ROM is an operating system package, or file placed onto the erasable/programmable part of the phones memory. NAND, I think.
S-OFF/ON *is a security check.
.Apk: compressed java file.
.Jar: *java application file.
.odex *files: helper files with most relevant information to compile and run the concerned application as fast as possible, a JIT Kind of thing.
----
I was able to relock bootloader, Yea!
Thanks megatronisabeast and newbroman.
--history--I updated to ICS from AT&T.
I thought I could skip reading for another three weeks because of newbie-proof AIO 2.1. * wrong!
I wanted to root my phone. *I had unlocked the bootloader with htcdev.*
Found hasoons all in one vivid 1.2. Used WC's recovery. I then flashed with hollicakes kernel, twice. Wsod.
--
Megatronisabeast:*
You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery.
-I'm not sure the exact boot img,*
- I think the zip file would be the rom?
Getting closer.
Thanks again guys. I'm feeling a little thick lately. Like freshman year of college! Weed out classes.
Hi everyone.
I have an Optimus 2x, and when i updated it to 2.3.4 i could not use superoneclick to root my phone instead i found an answer on how to root it.
I needed to install cwm 5 and after that busybox and so on, and it worked, it was rooted.
Now i have a other problem, i have an update on my phone and when i click on installing it starts to reebot then it comes to cwm screen, there i'm stuck.
I have tryed everything there trying to update it but nothing works.
So now i am wondering if any of you can help me?
Got any idea what i can do to update or what i am doing wrong?
//Szander.
Ok, so now i did a recover so i get back my phone as it was before i installed cwm and tryed to update, it did work fine.
Until the update was done, then it stopped, and nothing i did worked the little android just stand there and looked at me.
So what now, i removed the battery and hoped for the best, now the phone would not bot at all.
After a few tears and a few swear words, i thougt about something, maybe i could use nvflash to get it all back as it was ???
I tryed closed my eyes and after a few minutes i could restart my phone and it loaded as useall, but the update was gone, ofcourse.
So now back to square one again.
Sigh (
Hi Szander,
So just to be completely clear, you're back at a perfectly stock 2.3.4 unrooted ROM and you want to root it, right?
Why not trying to follow cyanogen wiki to root it?
LarsPT said:
Hi Szander,
So just to be completely clear, you're back at a perfectly stock 2.3.4 unrooted ROM and you want to root it, right?
Why not trying to follow cyanogen wiki to root it?
Click to expand...
Click to collapse
No.
I have cwm, and its still rooted.
What i want is to get rid of cwm so i can update to the latest update wich is v20q.
I have tryed this with recover but its only working on froyo, i belive i read it somewhere.
And when i recovered my phone then the problem really started, but thats fine now.
And as an plus is that now when i run LGMobileupdate tool its saying that i have v20q but in the phone it says that i still have v20I.
Weird.
I have read alittle more and (if i got it right) found out that i might just need to use smartflash on the phone via my computer to get rid of cwm and get a perfectly stocked phone again.
So can you help me please, hoping that you understand my problem.
Yup, as far as I know you are correct. To get your phone back to stock you need to flash a stock ROM using either smartflash or nvflash. I haven't done it so I can't guide you through it personally, but search this forum you should find the relevant threads easily enough.
If you have trouble finding it let me know I'll help you searching.
EDIT: By the way, thanks for Meshuggah, one of the best bands ever I should visit Sweden sometime
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.