Related
I am having some phone problems as a result of a root attempt.
Phone : LG p999
Carrier : Wind (Canada)
Here's what I did:
1. Tried superoneclick root program. It never got to completion and I couldn't figure out why. It always failed at right before finishing, even after reboots.
2. After superoneclick , I decided I would edit the adb shell manually. I did not initialize psneuter because that step was successful with Superoneclick. I loaded the superuser package. After this, I couldn't get the phone to boot, even in recovery mode.
3. Next I used One-Click ClockworkMod Recovery NvFlasher to load clockworkmod (cwm) . At first I loaded it onto internal SD. This worked fine but I couldn't get it to recognize any backups or cm7 nightlies.
4. Then I tried loading on the external SD. This worked, I couldn't see any backups but could load cm7 nightly and gapps.
5. Rebooted phone, everything fine. But within a few hours, my 3g was not working. I typed #*#*4636*#*# and saw the 3g settings were empty. Apn settings are normal though.
So here is where I'm at now. Wifi, SMS, calling all work. Cannot access 3G, sdcard (can’t take pictures).
Also, I didn't make a backup. Yea, that was stupid.
first thing were you on 2.2.2 or 2.3.3 when you first tried superoneclick? It sounds like you did the update and were on 2.3.3. The superoneclick methode does not work for rooting anymore. You have to nvflash CWM first. Then flash xboarders stock ota rooted or any Rom that is pre rooted I think will work.
So what I would do at this point is try using nvflash and flash back to stock and start over. You will probally have to reinstall CWM then I would just use the xboarders stock rooted ROM just to gain root then install CM7. You probally dont have to flash xboarders first but that is the way I know will definitly work so that is what I recomend. Also I dont know if the NVflash returns the phone to stock 2.2.2 or 2.3.3 I have never done it. maybe someone else who knows more could chime in.
Charlie
Are you already on Cyanogen Mod 7 as your title indicates? CM7 is rooted OOTB. There is no reason to try and root it again.
Yes it is running CM7 now, but with some serious problems:
1. Can't use one click to flash stock ROM -- each time I try the phone gets stuck in a rebooting loop and just eventually freezes.
2. 3G/sdcard problems with CM7
- not sure if this is just an issue with the CM7 build or whether my phone is causing this.
I have flashed CM7, but the weird thing is that the 3G works fine for about a day and then it cuts out. Its not an APN thing --> I checked the settings. Any ideas what is going on there?
Gonna try loading xboarders when I have a free evening.
Thanks
Hi guys, I need your help!
Yesterday I updated my phone from Froyo 2.2 to Gingerbread 2.3.5 with Kies, then I rooted it trough Odin and flashed the recovery with ClockWorkMod recovery (i followed the guide, and made everything it asked to do). I completed the task succesfully. But here comes the problems:
I turned the phone on and I wanted to use Wi-Fi connection but I couldn't! It was just saying "error" and in settings the MAC address was unavaiable. I found something on the web, like trying to dial *#*#526#*#* but it didn't work too ("Driving loading unsuccessful").
So I wanted to bring the phone back to the previous state, So i unrooted it (succesfully) but now I'm stuck with this ClockWorkMod recovery and I can't find a way to restore the original Samsung i9003 recovery because i can't find it anywhere and I don't even know if I can use another Samsung's one.
I tought that maybe reinstalling Gingerbread from zero could fix this problem, but I'm not even sure of that, neither on how to reinstall it. Damn, I'm truly an Android n00b
Thanks to everyone that will spend some time helping me!
If it can help, here some infos about my phone
I9003XXPN
Kernel Version: 2.6.35.7-CL482273 [email protected]#1
Version build: GINGERBREAD.XIKP2
Click to expand...
Click to collapse
marvin_kk said:
Hi guys, I need your help!
Yesterday I updated my phone from Froyo 2.2 to Gingerbread 2.3.5 with Kies, then I rooted it trough Odin and flashed the recovery with ClockWorkMod recovery (i followed the guide, and made everything it asked to do). I completed the task succesfully. But here comes the problems:
I turned the phone on and I wanted to use Wi-Fi connection but I couldn't! It was just saying "error" and in settings the MAC address was unavaiable. I found something on the web, like trying to dial *#*#526#*#* but it didn't work too ("Driving loading unsuccessful").
So I wanted to bring the phone back to the previous state, So i unrooted it (succesfully) but now I'm stuck with this ClockWorkMod recovery and I can't find a way to restore the original Samsung i9003 recovery because i can't find it anywhere and I don't even know if I can use another Samsung's one.
I tought that maybe reinstalling Gingerbread from zero could fix this problem, but I'm not even sure of that, neither on how to reinstall it. Damn, I'm truly an Android n00b
Thanks to everyone that will spend some time helping me!
If it can help, here some infos about my phone
Click to expand...
Click to collapse
Now, Do you want a guide on how to re-flash back to Gingerbread using ODIN? If so,It is here. And, I would like to tell you that on re-flashing the FW, you are going to void your warranty and you will be able to get rid of the CWM
Hope it helped you!
hi OP
I'm facing the same problem as you, right now waiting for dxkp9 download and reflash with Odin.
But if you somehow manage to solve this issue please share.
Hi!
I tried and I tried and I solved it! I flashed back the stock rom of I9003 with Gingerbread trough Odin. This removed ClockWorkMod and restored the phone as it was in the beginning. Problem solved, original recovery mode and wi-fi finally works!
marvin_kk said:
Hi!
I tried and I tried and I solved it! I flashed back the stock rom of I9003 with Gingerbread trough Odin. This removed ClockWorkMod and restored the phone as it was in the beginning. Problem solved, original recovery mode and wi-fi finally works!
Click to expand...
Click to collapse
+1 [Reflash, and CF-root without 'extras' and restore]
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
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!
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