Related
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
beast6228 said:
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
Click to expand...
Click to collapse
You are probably going to have use Xboarders ROM then flash the unroot.zip he has in this thread http://forum.xda-developers.com/showthread.php?t=1158513.
See if that works to get you back to 2.3.3 completely stock.
It says that because it checks the baseband to see how recent it was, that's why it thinks you're on v21e.
As of now, there's no way to flash back to the old baseband, since people don't include the baseband in their ROMs, as that can cause a whole host of problems. The solution is to do exactly what tidewaterns said, that just gives you a little extra background info.
I am going to give this a try and see what happens, I will post results.
Well I tried the slimmed down version of Xboarders's rom and it seems to be working well so far. I originally installed his Stock OTA rom and that's when I started having problems. Oh well. thanks guys for all the help.
Crash course about root and roms: Superoneclick roots the rom you have in place. Flashing xboarders rom didn't "give you root" for the other roms you flashed, it is simply one rom out of many that is pre-rooted by the dev who packaged it up. When you flash it you have a rom that is rooted. If you had flashed CM7 (another rom that provides root access to its system files) then you'd have had a different rom that was pre-rooted by its dev.
Are you catching what I'm saying? Flashing xboarders rom didn't "give you root" any more than CM7 "gave you root." Root is built in to those roms.
If you want to restore to an unrooted stock rom browse the threads in the development section. There are a couple of stock nandroid backups posted that you can restore via clockworkmod recovery and then you'll have a stock unrooted rom. You can even do that and still have clockworkmod recovery in case you want to flash a different rom to your phone again.
And PLEASE remember when flashing from one rom to a different rom, WIPE WIPE WIPE data, cache, dalvik cache, then flash rom, then fix permissions, then reboot. This will save you SO MANY headaches.
G2X CM7
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
beast6228 said:
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
Click to expand...
Click to collapse
Sweet! If you're simply updating to a newer version of the same rom you can probably get away with just wiping cache and dalvik cache and then flashing. Its just when you switch to a totally different rom that you need to do a full wipe. Gives you a clean slate to start with.
G2X CM7
I'm curious about one thing though. What would I accomplish by using Nandroid and flashing a bin? I see there is a BIN_LGP999AT-01-V10f-310-260-MAR-27-2011+0.zip file that is available for this phone, although I have no clue on how to install Nandroid. Anyways, wouldn't flashing a BIN be the ultimate way to restore the G2X?
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy
If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?
If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham
Yeah, you can still fix it. No need it to bring to samsung
Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!
Hi there, I have been trying for countless hours to make a custom ROM work on my P920 with no results, always some issues. I've managed to brick my phone in different ways a billion times now, then spent billion hours unbricking it and in the end I'm always back to where I started. I would really love some help please.
My phone is P920.
The android version I'm running is: 2.3.5
Kernel version: 2.6.35.7+
Software version: V21E
Rooting method: megatron
Now I would like a ROM that uses Android 4 and that can still use the 3D features such as 3D camera, the ROM calledthe Darkroom International would be an example I imagine.
While that's one of the ROMs that I would want, I've tried many, and always encountering issues, let me clarify.
First of all my device has to be rooted and since SuperOneClick doesn't work for me as it gets stuck on step 7, I use megatron which works well. I even double check if my phone is rooted with the Root Checker from the Android store. Now according to the guides I've read I need a custom recovery system, so I install Clockworkmod. I then place the ROM on the SD card, in the recovery menu I delete cache, that other cache, format it, format system, data, everything those guides tell me to. Afterwards, I install the ROM by selecting the zip and then I reboot. I've tried like 3 different ROMs, jellybem, cyanogenmod and some other. Yes I know none of them support 3D features - I didn't know at the time. Anyway, the issue was always the same, right after the LG logo there would be a screen with some weird colors showing the display of what happened before the phone crashed. Before it crashed? Yes, the phone would actually boot into the ROM but only for a few minutes, crashing afterwards. The next time I would boot, it would show that weird screen with those fancy colors with what happened just before it crashed. So I followed some steps and I got back to the original 2.3.5 ROM, everything back to normal.
I tried doing some more research and I came across the Darkroom Intentional ROM which had a bit different instructions. It asked me to install TWRP recovery with a bootloader, so I did, successfully, then did all the clean cache etc, installed ROM, bam, wouldn't boot at all. Oh boy have I had issues here, I couldn't even get it back to the default 2.3.5 stock ROM because my phone wasn't even recognized in the device manager. So I did some more research, found a solution, managed to flash back to 2.3.5 stock and I'm back to square one.
Now, could someone please help and explain to me what exactly have I done wrong and how I can make it right? I've spent countless hours now trying to install a custom ROM with no success. Sorry about the long read. If you need me to supply some more information please let me know. Thank you.
First of all if u want to use an ICS ROM then u need to update to ICS FIRST u can't flash it directly from 2.3.5 u can use xbsalls thread to update......
Next if cm based Roms are crashing then u need to flash bootloaders which means u should use os_hacking tool to flash ICS bootladers if u wanna update
Or flash GB bootloaders
So first update if u want
Root
Flash bootloaders
Flash recovery
Flash Roms
Sent from my Nexus 4 using xda app-developers app
Hello all,
Okay, I admit that I am gonna get a lot of "use the search tool first" replies, but please hear me out. I have done my fair share of searching. Its not that I haven't found anything, its just the things I found are useless for this SGS 4G. I really wanted to install Cyanogen Mo on the SGS (its not actually mine, a friend asked me to do it since he saw my old SGS GT-I9000 running CM).
I am gonna try and give a detailed report . The phone was originally from T-Mobile and now unlocked permanently. Its running firmware version 2.3.3 that I installed just recently. I found out that I can't install CWM on the stock kernel or bootloader or whatever and I needed a new of the thing. So I went on searching and searching....found a handful of help but none work. Every method breaks at some point and I go to the "firmware update failed" thing on the phone, which I then install 2.3.3 again using ODIN and try another method. I have tried a lot of things. Hemidall, ODIN, SuperOneClick, and a lot of gibbrish-sounding methods. None work. I am now running 2.3.3. Here are some infos:
ABOUT PHONE:
Model Number: SGH-T959V
Firmware Version: 2.3.3
Baseband Version: T959VUVKF1
Kernel Version: 2.6.35.7-T959VUVKF1-CL270364
Build Number: GINGERBREAD.VUVKF1
The files I used to flash to 2.3.3 using ODIN v1.85:
PIT: Hawk_Sidekick_VibrantPlus_831.pit
PDA: CODE_T959VUVKF1_CL270364_REV00_user_low_noship.tar.md5
PHONE: T959VUVKF1-Phone-CL1020302.tar.md5
CSC: SGH-T959V-CSC-TMB-VIBRANTP.tar.md5
I hope the above infos are enough. So, can anyone help me and point me to the right direction on how to install CWM and then install CM10 or 9 on my friends SGS 4G?
Thanks,
Tamrat
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
For the SGS4G, the kernel, root file system, and recovery file system are all in "boot.img" -- flash one, you flash them all. They can be flashed through Odin (assuming you really like Windows), heimdall (multi-platform), through recovery, or from a root command line (for the adventurous only).
I would say the most robust way to get where you need to be would be to use Lumin's guide to make sure you've got a viable Gingerbread set-up going, then flash something reliable to get you to MTD, like TeamAcid's CM9.
From there, you should know that some of the KK ROMs use slightly different MTD partitioning and aren't a "just flash this ROM and keep your data" kind of thing.
jeffsf said:
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
Click to expand...
Click to collapse
A long day Googling... and then a site turned up. One thing I forgot to mention was, before I installed this firmware, I had to use the "remove battery->plug usb->press the button combos->insert the battery" to enter download mode, but now I juts have to press vol down and power button.
Thanks for the reply,
Failure again
UPDATE:::
I tried to update to 2.3.6 as the guide suggests and I also wanted a clean stock OS in case the old one was not. But once again updating to 2.3.6 has been a pain. Kies Mini recognizes the phone but it doesn't recognize the firmware running on the phone. And also, firmware update is impossible since the button is greyed out.
I googled again and found the official 2.3.6 firmware for the phone (file name: T959VUVKJ6-REV00-home-low-CL694130.tar.md5) and tried flashing it using ODIN; absolutely no luck. It fails at the stage which says Slb.bin. Restarting the phone after that gives a "firmware upgrade failure" display. Only way to wake up the phone is to flash the previous OS back.
I am really confused here.
*********************EDIT***************
Some how, after like 10 retires and fiddling with ODIN, it finally flashed 2.3.6 to the SGS 4G. Still, fingers crossed.
*********************EDIT 2***************
Finally, its all working fine now. Thank you @jeffsf, thank you very much.
F*****************K
forgot an important step and now my IEMI number is gone........
do i throw the phone now, or is there any other way???
Don't throw your phone away! How do you know that you have "no IMEI" on your phone? We'll go from there.
Hopefully, you've backed up your data before starting to play around with ROMS. If so just load your backed up efs folder onto your storage & use Root Explorer to drop it over your existing one , it will overwrite your imei file & you will be good as new.
========================================================================================
I'm also in need of help, I have been running SlimSaber since last weekend, was wanting to try out Beanstalk. First full wipe, install & reboot wipe again, reinstall etc as per Dao's OP, but after the first install, it won't boot past the kernel splash. Tried again with same result. Decided to click it back to stock & start over, using Gremlin Remover (odin). Then saw that others were having similar issue so I tried to load in build from April1st.
But now it only boots back into recovery, won't boot to the OS ( everything indicated install was complete & no errors.)
1 clicked back again & just tried to put SlimSaber back on again, but have the same problem, will only boot into recovery.
I had to first load CM9 to get CWM 6.xx so I could install kk using TWRP
What am I not doing correctly? Thanks for any suggestions.
Flash kernel
Reboot recovery
Wipe all partitions
(Reboot recovery for good measure and wipe again if paranoid)
Install
Boot
If that doesn't do it, it is likely ROM or hardware.
---
Posted from whatever phone booted today
Since this is running GB VUVKG4, could you recommend a kernel that would work & get me to TWRP (or CWM 5.xx+)?
Either the Team Acid CM9 or Hefe Kernel should work.
---
Posted from whatever phone booted today