Related
Okay, so I read and read, searched and searched. So far I'm pretty stuck.
I did a ton of research before taking my LG P500h, and flashing the ROM because I wasn't a fan of the Froyo android setup. Did everything properly, ran an nandroid backup, everything that I was told to do.
Rooted using Gingerbreak APK, custom backup using Amon_RA custom recovery. All done using the latest USB drivers LG updated me with.
I am currently with Koodo Mobile here in Canada. Pretty much an offspring of Telus Mobile. Currently I am running Cyanogen Mod 7 the 6.5.7 beta build, and the phone is not bricked, or giving me any errors or hassle.
The problem is that I cannot use the 3G network or use the Koodo network. It only defaults to Telus towers. No android market showing up anywhere either. From what I've found on here, there doesn't seem to be a bugfix solution to this, and no settings I've been able to change on the phone has helped my situation. Maybe I missed something.
So, I decided to take it back to where I began, back to Froyo 2.2.1 . This is where it all went wrong. Tried going through the Nandroid backup and restoring that, I was given an " Error : run 'nandroid-mobile.sh restore' via adb! " . Okay, I'm not exactly a Java programmer so I'm a little intimidated. I do however have Android SDK going on my laptop.
Some more searching revealed the KDZ_FW_UPD.exe flashing method. I got the right KDZ file for my Koodo phone, V10V_00.kdz and began the process. Everything checks out, good to go, started update. Wait, phone not found? WTF! My laptop recognizes it, says my phone is connected and working. No problems here, just can't find it? UGH.
So, I need someone to either give me info on getting it to flash the kdz, or get Cyanogen Mod 7 working properly on my device.
Please help, I'll fully admit I'm a noob to this, and not an expert programmer either. But, I know computers and I fully understand what I have done so far to my phone. Just not enough to fix it.
Okay, I have gotten some things working on my phone. I think I am settling into Cyanogen Mod nicely. I missed the Google apps flash zip so I have my market and stuff. Its a shame the data does not work though. Oh well I will keep updating as it gets developed.
Sent from my LG-P500 using XDA App
GOT IT! finally...
Finally got my phone recovered to OEM specs. I had to restore my computer back to before I installed all my drivers and reinstalled all my USB drivers from there. Phone connected to USB properly, ran the KDZ updater, and it sucessfully installed the V10V kdz. All is well.
finally good luck.. enjoy androiding..
When you flashed the cyanogen mod rom what program did you use to flash the phone? And how did you make a rom backup? When you reflashed the stock rom did it still have all the original bloatware?
LG Optimus P500h TELUS became dead during Upgrading
Hi everybody!
I have LG Optimus P500h Telus. I purchased from Kijiji. I don't have any papers or documents for that so i cannot claim its warranty.
I was trying to upgrade its version during upgrading my device was stuck so I disconnected and plugged out its battery and inserted again. When i tried to turn it on. It never turned on again. It never ever appeared emergency mode again. I tried for several times by pushing home, power, and volume up and down buttons, and escape buttons. Now its just like dead. It never showed any sign of life. If anybody have any idea what happened with it and how I can recover or where I should take this one for repairs. I am in toronto, canada.
Your help and suggestions will be appreciated.
HELP!
http://forums.androidcentral.com/t-lg-phoenix-thrive/127858-jobans-kernel-2-08-overclock-cm7-2-3-7-etc-gyro-fixed-60.html
My problem starts from post #600
Please.
Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!
Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk
If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk
So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?
Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.
I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.
What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.
At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App
To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!
Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App
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.
First off, I know I just signed up. I've been creeping for the past month or so.
So here is the situation:
Summary: I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.
Hboot:
Unlocked
S-On
1.26.0000
Software Info:
version: 2.3.4
htc sense: 3.0
software number: DesignerEvo-0.5
Longer Version:
I bump into a tech-head tweak everything buddy of mine and he says i just have to "flash the new ics" to my phone.
15 hours of banging the head against the wall later i realize im trying to unlock/root/su/flash as though i have the evo 4g not the evo DESIGN 4g which i actually have. (and which i shortly discovered has nothing customized for it) After that I was off and away-ish...
so here is what i have done (don't mock me for saying it wrong):
- Unlocked the phone via htc dev site (it won't let me post links yet)
- Flashed/Installed Custom Recovery Clockwork mod 5.0.2.7
- Flashed su-2.3.6.3
- Flashed Designer Evo 0.5 found at sdx-developers (wont let me link)
- then for kicks flashed a a vaelek rom that said it was compatible-ish for the evo design from http://forum.xda-developers.com/showthread.php?t=1399351 it didnt see usb and other issues, so...
- then came back to Designer Evo
- installed setcpu to try to improve battery life...
Everything was fine for a couple of weeks (other than no ics and crappy battery life!)...
All of a sudden at random the phone powers off with battery reading charged. It will reboot, and within minutes power off again.
It does this in stock rom and custom.
If i keep it on charge it stays on.
If i remove it after charging, it holds power for a little while, but still powers off.
I thought conflict may have been between setcpu and a power savings app i had running and had forgotten to remove. removed, seemed to be okay then same.
I decided to come back on here figure out how to flash back to factory and unroot, and plugged it into computer (windows 7) via usb. "unknown device". reinstalled drivers. same problem. opened as ubuntu 11.x, still nothing. installed drivers nothing.
I dloaded a stock PH44img.zip w/ phone and put it on root and it would load at hboot, but do nothing after. may require s-off?
This is weird, I did a factory reset from recovery and on reboot it defaulted to the vaelek custom rom, so i went back to my oldest backup.
so... as i said, I think I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.
Hang in there Vince...somebody is bound to point you in the right direction
I guessing people were off partying this weekend and have yet to respond?
ok this is crazy.... My design 4g is nowing doing the same thing.... Google brought me to this thread... anyone know anything?
Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app
shrekdaklown said:
Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app
Click to expand...
Click to collapse
Tried several roms . No luck..
tried to ruu via boot loader... It won't take. I may need to relock the boot loader.
No longer own this phone, and no longer have a copy of the rom so this is no longer being developed.
Thanks to @shifattk and @FitAmp for the overclock
Thanks to @Restl3ss, who is working on a rooted and overclocked, otherwise bone stock ROM
Thanks to @atmu5fear, who made the first flashable rom for the S730M, I based my Rom off your original release.
changes I made from the stock 4.04 image
Rooted
BusyBox
Overclocked to 1000mhz
Nova Launcher
Default Ringtone: Crank
Disabled power on and power off boot sounds
Bloat Removed
Theme Changes
Zipaligned
Replaced Samsung keyboard with the google keyboard (much better IMHO)
Stable
Working and tested. Tested on a S730M as well as a S730G
Flashing instructions:
1. Use CWM 6.0.3.1 Get it here https://docs.google.com/file/d/0B1BxFtN0QItNUExLMHBWT1loQjg/edit?usp=sharing, flash with Odin)
2. Make a backup, if things go wrong for you, you cause use the backup to restore your phone's original firmware.
3. WIPE DATA/CACHE
4. Flash
5. Wipe Dalvik.
6. Reboot
NOTE: I can not and will not be responsible for any damage this rom could potentially cause on your phone, http://en.wikipedia.org/wiki/Caveat_emptor
Download Version 1.0 here
Good to see someone still working on this device
Sent from my HTC One using Tapatalk
FitAmp said:
Good to see someone still working on this device
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It's a nifty little phone. I personally think it's better than a Nexus S but just suffers from the typical Samsung pump and dump routine where they sold all their inventory to the carriers then stopped supporting it with any updates.
Good job! I have 3 versions of the stock ROM available for this device as well, may have been more appropriate for a base, there's stock, stock + root + Busybox, stock + root + Busybox + overclock. Find them here
http://forum.xda-developers.com/showthread.php?t=2677332
Sent from my SGH-T989D using XDA Premium 4 mobile app
r740c
Will these ROMS work with the Cricket version?
kadeleblanc said:
Will these ROMS work with the Cricket version?
Click to expand...
Click to collapse
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.
CDMA
doctor_evil said:
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.
Click to expand...
Click to collapse
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.
kadeleblanc said:
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.
Click to expand...
Click to collapse
You may be able to use the same CWM recovery on that model,
you should be able to probably use the same kernel to overclock your model too, and you can probably use the kitchen app we used to cook these different version roms for the 730M and 730G models to do your own custom rom, just remember before you start working, to do a full nandroid backup of the current rom so you can restore it back to the original (mostly stock except for the cwm recovery) firmware if you need to later on.
By any chance this will unlock it or do you know a way for me to get the unlock using hex?
Thanks to doctor evil for this ROM I was able to flash my phone but not before removing more apps (bell apps and oothers ).
I was wondering if anyone was successful in unlocking the tethering? Tried a few things out there and the best I could get was Bluetooth tethering with foxfi.
And it works!
@doctor_evil: I flashed your set after having played with @atmu5fear's version (http://forum.xda-developers.com/showthread.php?t=2673097). I like them both very much and am still looking which one I will keep. I have not wiped data/cache (i.e. Factory Reset) before overlaying your version over @atmu5fear's one, and it did not hurt. I noticed the following:
Flashing your ROM did not again trip the ROM counter after applying the triangleaway script after @atmu5fear's ROM load (it did go off then).
When having a SIM in the S730M and after putting in the phone unlock password, the keyboard stays on top (this does not happen when no SIM is present)
My Battery-drain problem when having the phone powered fully off with a SIM installed is still there. Probably need to await a cooked custom ROM for this to be solved
The triangleaway script for the S730M can be found at http://forum.xda-developers.com/showthread.php?t=2420184
The Battery-Drain S730M issue has been noticed by quite a few people (TELUS and BELL, both in Canada), and is unexplainable. When the phone is on (with SIM installed), power usage is normal, but when you power off the phone (with SIM still installed) the power-drain goes up dramatically (draining the battery completely within a few hours). When the SIM is removed, or when the battery is removed there is no abnormal drain perceived. The other thing is, that, when the device, with SIM and battery installed, is powered off, both the battery area and the SIM area get warm (not really hot), indicating SIM activity WHILE THE DEVICE IS OFF... Very odd. I am hoping that a new KK custom ROM would fix this issue as both 'custom' 4.0.4 ROMS I have tried now show the same issue, indicating it is either a hardware or a 4.0.4 implementation issue...
I am sorry I never responded back to you. I had my Cygwin install with my kitchen build environment running on a SSD hard drive with my OS and the drive crapped out on me and had to be sent in for a RMA. I had a easus todo workstation backup of my drive I was able to restore, but the backup wasn't current so I lost my kitchen environment. I never tried to set it up again as I had hoped that someone would have ported Cyanogenmod to the phone.
I may give it a try again as I just setup a vmware ESX host server here at home and I can allocate multiple cores and plenty of ram to the linux Virtual Machine I created on it once I figure out the best build environment and how to actually go about building CM successfully. Anyone know of a porting cyanogenmod for dummies guide I can use? LOL