Hey everyone, I'm new to the xda scene, but I've been following most updates closely.
Until last month, I had a rooted version of v10a (using Gingerbreak), but then I upgraded to v10b without checking if it was rootable first. My bad.
Now I have an unrooted LG P970 with v10b, and my only other tool apart from the phone is my iMac...
How do I get from an unrooted v10b to a rooted v20n using only my SD card and an iMac? (I just realized that this might be a fun riddle for some of you)
ISSUES OF HAVING A MAC:
Can't use SuperOneClick or any other .exe, unless there's a Mac version.
I've been struggling with this in my head for a long time now, I hope that there's someone who can actually discover a way for me.
I don`t know any tool for mac but now REALLY is that hard to find a windows PC to make your job ? lets forget about MAC and Windows users conflicts.
Install windows, at least as a virtual pc and it all will work
Download Gingerbreak 1.20 on yout phone (google-it) and try root with it.
Worked for my V10B - Romanian version
Well, I tried various options and finally managed to win vs this evil cell phone!
The reason I can only use Mac is because there aren't any PC's in my company, we all use Mac.
1 - I installed VMware Fusion to boot Windows in a Virtual Machine on my iMac;
2 - Used KDZ Updater to revert my phone back to v10a;
3 - Booted Gingerbreak v1.2 to root it;
4 - Used CWM Recovery to upgrade to a rooted v20n version.
Et voilá! If I can help with any of these steps, just let me know and I'll go into details!
Related
Hi all,
I am unable to get Kies to recognise my galaxy s (when in Kies mode) or windows for that matter. I've tried installing the samsung usb drivers etc using the latest version of kies, still doesn't work.
What options do I have now in terms of firmware flashing? (I'm not installing 32bit xp just to flash my phone)
Cheers
if you search the forums you will find your answer, which will be along the line sof using Odin, very easy to use, so good luck and enjoy.
win7-64bit and kies connection semi-working method
I've tried almost all methods mentioned on different forums...but since i'm unwilling to mess to much around i've opted for this way:
using latest kies 1.5.3. 80something... on win7 64 bit..
remove the lockpattern from the phone if yo uhave it enabled
install kies...remove the kies autostart option and the kies trayagent
do the repair drivers and reboot
ones the bios screen is done..have the phone unlocked and connect to pc/laptop
wait and wait some more after login to windows..
one most occasions windows will finally tell you it have a new device ready for you...then open kies and life is good.. at least until like in my case the laptop goes into powersave mode and the connections are broken and I have to do the reboot step again
the firmware update from jf__ something to jm__ something was a hassle...but after a few attempts to run it the darn thing finally worked..
hope this helps
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
ardll said:
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
Click to expand...
Click to collapse
i am with win7 x64, fine here
using odin to flash rom is dam easy job.
Kies updated to _82 today.
the _82 update fixed closing the firmware updater for me that was in the last 2 builds on win7 x64 , it promptly closes having not used up more than 33mb ram when I click cancel or close after checking for new firmware, previously it billowed up to over 1300mb use and really flawed my system until it, kies and the connection manager were terminated fully.
http://www.samsung.de/de/support/detail.aspx?aguid=47e29085-4dff-4b5c-b8ab-dd9b9c8b70f8&dl=software
try the new PC Studio software for SGS
download link and detailed info on SGS wiki, click my link
ok..i bricked my black and i have a big problem. i was on CM7 latest nightly build and i manually tried to change the font using root explorer. and the cell went into bootloop after i rebooted.
now, i tried to use the unbricking using the R&DTT, but i have the following erroor. the attached image is what i get.
i, infact have the b2c client installed .
please helpppp, please, please...ANY help is appreciated!!!!
achyut said:
ok..i bricked my black and i have a big problem. i was on CM7 latest nightly build and i manually tried to change the font using root explorer. and the cell went into bootloop after i rebooted.
now, i tried to use the unbricking using the R&DTT, but i have the following erroor. the attached image is what i get.
i, infact have the b2c client installed .
please helpppp, please, please...ANY help is appreciated!!!!
Click to expand...
Click to collapse
Servers are down anyway so you can't use R&D with B2C. Do you have adb installed? Also, try entering recovery by pressing volume down then power button, you might get lucky.
gabwerkz said:
Servers are down anyway so you can't use R&D with B2C. Do you have adb installed? Also, try entering recovery by pressing volume down then power button, you might get lucky.
Click to expand...
Click to collapse
1. servers are down: AWESOME!!!
2. ADB installed: NO!!!
3. vol down+power: NO LUCK
NUTSHELL: AM *&&^%^&*
Hey, tomorrow is a Monday. Im figuring you are within your warranty. Instead of waiting for the servers, which are up, btw, all you need to do is step into the LG service center. They'll replace the handset in 2 days. I got mine replaced a week ago.
shreyas99 said:
Hey, tomorrow is a Monday. Im figuring you are within your warranty. Instead of waiting for the servers, which are up, btw, all you need to do is step into the LG service center. They'll replace the handset in 2 days. I got mine replaced a week ago.
Click to expand...
Click to collapse
i thot of that, but since the phone is bootlooping CM7 bootscreen, i feel they are going to void my warranty!!!....were u rooted and yet got your handset replaced???....reply man!!!....am so tensed!!!
Try this :
1. R&D Tool must be Run As Administrator
2. B2CC notiagent must run (on taskbar)
3. Change Phone Mode to DIAG
see also THIS GUIDE
can anyone post the EXACT STEP BY STEP 2 unbrick the phone??
even running LGUpdate -> recovery phone didn't help.
it downloaded the update, updated the phone, but the cell won't boot!!!...only thing that changed is that the bootanimation loop has changed from CM7 to stock LG one. dats about it!!!....please help me guys!!!!...am so so so so worried!!!!...feel liek i was better off with the x10
I did down-grade CM7 to Stock ROM V10D use R&D Tools without problem. I saw your R&D tool pic, I suggest to you :
1. Use R&D tool again (because R&D tool is full flash).
2. Re-download kdz file stock ROM HERE (maybe your kdz file is broken)
3. All of that Windows Software must be run as administrator.
4. Change PhoneMode : CS_Emergency to be DIAG (see image of R&D that you uploaded)
ps. : Sorry for my bad english
here is the problem with me.
1. I HAVE THE DRIVERS, MSXML 4.0 AND THE B2C TOOL INSTALLED
2. I DID EVERYTHING MENTIONED IN THE GUIDE ABOUT THE WINDOWS ENABLER AND EVERYTHING.
3. THEN WHEN I START THE R&D TT or he UpTestEX_mod2_marwin.exe, it runs. i select the downloaded .kdz file, (mode is set as CS_Emergency) and then when i hit run CSE WEB UPGRADE TEST, it shows me the 2nd window where i should hit "UPGRADE START" and it runs the updater, however, when i run it, it says
"please install B2C CSMG CLIENT TOOL
SELECT TOOL -> B2C Client Setup Menu
but when select it from tools it says "B2C Tool Setup Complete"!!!!!.....what 2 do.....PLESASEE HELP...HELPPPPP!!!!
@achyut What window$ version do you have?
redy2006 said:
@achyut What window$ version do you have?
Click to expand...
Click to collapse
i have Windows 7 Ultimate_x64 on my laptop...however,i have the WIN 7 (_x86) on my desktop.
SOLVEDdon't know if it was specific to my laptop,but when i tried it on my desktop, it worked!!!! btw, i don't have the PC Suite installed on my desktop,if it makes any difference.
I use x86 version, and don't have problem. Perhaps it is related with x64 system, I don't know for sure.. But, I'm glad you've solved it...
Now listen to this one...
OK, so after a lot of reading and surfing, I finally decided to root my Galaxy Note N7000, using the method described here http://www.youtube.com/watch?v=uv2oGo1_yTQ and I did prepare all and myself mentally for all the variants of the failure.... except for one...
ok. so I download all the software needed on both my English/British Windows 7 64-bit Home Premium laptop and on a XP Home 32-bit laptop, just in case there are some incompatibilities, I'll have it all covered right??? WRRRRROOOONNNNNGGGG!!!
I put the phone in download mode connect it to pc and want to start Odin (1.85 version), but I get "Odin3.ini 000 000" (except the zeroes were square...) small pop-up screen with "ok" in the middle... So, I think "oh, ok, again asking for permission... GRANTED" and I press it and the screen/window of Odin flashes in the third of a second and disappears... I try again.... Same story... on both laptops.... with kies on and off... installed and uninstalled... SGN N7000 connected and disconnected.... same with the downloaded Odin from zedomax's link and from any other link I could find...
What is the problem???!!! Seriously, have you heard of that????
I don't even get to brick my phone, that is how the Android gods hate me!!!
I can't even start Odin programme... (yes, I did Run as Admin)
what is it?
I tried turning off antivirus and firewall... nothing...
Any ideas?
Try these methods :
Download a fresh Odin, maybe yours is corruptEd.
After the download extract the entire rar directly into a folder and then run Odin from that folder.
I got a similar error on Odin once when I placed the Odin icon on the desktop.it was a long time ago so I don't remember the error but I couldn't run Odin either.
And for Godssake don't use a 64 bit machine, we've already got enough trouble as it is on regular 32s.
i run 64BIT...and ODIN3 v1.85...it works flawlessly...just remember to run it AS ADMINSITRATOR....
I read somewhere that the odin folder should be placed on the root of c: drive. Works flawlessly on my 64bit win7 machine. I've also set it to run as administrator.
please hit thanks if i helped
SpyderTracks said:
I read somewhere that the odin folder should be placed on the root of c: drive. Works flawlessly on my 64bit win7 machine. I've also set it to run as administrator.
please hit thanks if i helped
Click to expand...
Click to collapse
i dont agree...i have placed it in F:.....
I bow to you, Masters of Android (or at least Samsdroid)
Hey, guys, you're a golden bunch really!
Turns out the problem wasn't any of the above mentioned meanies, but the fact that I extracted Odin to an Odin folder in My Documents and then copies that file/exe to desktop (I like my start buttons on the "main command frame", which is desktop for me ), and after posting this OP of this thread I went for a cold shower, and an early morning run and thought I'd try the whole thing one more time... This time I didn't put the Odin exe on the desktop, because I expected it to fail again... But, as it turns out, my lack of faith in Odin MADE IT WORK!!!
And, yes, the Note is rooted, and straight away (while luck is still on my side! ) I went for the Galaxy_s unlock and BusyBox apps to sim unlock my phone from the evil claws of UK Vodafone... And it worked as in 1.2.3.-DONE!
Guys, thanks for your effort and time invested in trying to help... I really appreciate it... It is great to know that if one gets stuck there will always be someone who has a solution, or at least will to find it through co-operation...
Now, find some good, useful apps, nice launcher (maybe tweak Touchwiz, if possible), good battery app, and research which ICS custom ROM based on a stable kernel is "da best"...
Glad it worked in the end. Check out paranoid android for a great and safe ics experience (based on cm9)
please hit thanks if i helped
I have been trying to root my LG Optimus 2x for maybe 10 hours now. Nothing works.
I bought it already used, with stock rom Froyo 2.2.2
I am running winxp sp3 and ofcorse i have already installed LG drivers and have "debug usb mode" (adb) checked.
List of thinks i have tried without success:
SuperOneClick - No ADB connection
NVFLASH - no connection
Smartflash - no connection
ADB over wifi - apparently i need root for this, so no success
^After theese tries, i came to the conclusion that my usb connection is not working for some reason (i cant even get mass storage working, well, never buying used phones again)
z4Root - App freezes and can not be started again without reboot.
Root via Terminal Emulator (Rage against the cage) - I cant seem to run/copy this .bin anywhere, "Operation not permitted"
I even tried gingerbreak.
I am not a linux noob, nor an Android noob. I have successfully rooted multiple devices, Desire (pvt-4 alpharev s-off) and some tier 1 android phones.
Anyone have any clue what is going on here?
U can try Unlock Root. It worked perfectly on my o2x!
Very easy to root, basicly with one click, very fast.
LINK: http://www.unlockroot.com/download.html
DualCoreEST said:
U can try Unlock Root. It worked perfectly on my o2x!
Very easy to root, basicly with one click, very fast.
Click to expand...
Click to collapse
Already tried that, too But as my ADB debug bridge is not working properly this will not work
Hi there, honored experts!
Today I got my precious Optimus Speed bricked, after I successfully restored a recent nandroid backup.
I've been happily running paranoid android for the last months, and often updated the phone with the help of goo.im manager. Today I did a full factory-reset after the CWM upgrade-process, to get rid of the old "disappearing keyboard"-bug. I backed up all my apps and data with superbackup and titanium-backup, and even created an online nandroid-backup (freshly updated nandroid-scripts and patch for my device).
After the reset I had issues to restore everything, since ti-backup often got stuck in batch-restore-processes. Because I couldn't stop the stuck process, it required me to soft-reboot the device a few times. And in the end, it failed to boot.
So I went into CWM, and restored my nandroid-backup. This went fine, and no errors were reported. But after soft-rebooting it, it only showed the LG-Logo-Screen, and nothing else happened. So I tried to get back into CWM - with no luck .
I've tried every possible key-combination I could find, and the only mode I can bring my device into is "S/W Upgrade". In this mode it is recognized by my laptop (running Linux), but rustys recovery fails, because nvflash reports:
Code:
sh ./flash-recovery-ext.sh
Nvflash started
USB device not found
even though lsusb shows:
Code:
# lsusb
Bus 001 Device 017: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000
I'm fresh out of ideas - maybe one of you can help me out? Otherwise the only thing I could try now is to turn it back in where I bought it.
I'm no expert at these matters,but I can tell you from my experience because I bricked mine P990 two times and was able to bring it back to life.
In both instances I used Smartflash, found V30a ICS ROM for it and flashed it over it, and it came back to life.
But when you do this,you will have ICS bootloader and you won't be able to install PA or CM since they work on the old bootloader.
Or you can flash it to the stock Gingerbread ROM https://hotfile.com/dl/168874678/8ea13eb/NVFlash_LGP990_V20Q_EuroOpen.7z.html
And I would recommend reinstalling nv flash drivers before,just in case the error is on your computer. http://www.mediafire.com/?cdgwwgkdozht8pw
Also, try All in one kit, http://forum.xda-developers.com/showthread.php?t=2020737 maybe it will help you. I repaired my bricked phone with it a lot of times. Its very easy to use as everything is explained there.
Jasper_bin
this device is 99% unbrickable
just go ahead with the AIOT by SPYROSK (this guy is a silent killer with amazing skills)....link in my signature
it works like a magic....real magic if you read the opening post and do it properly
Thanks
Hi Obersoldat,
I'm currently on the new BL - PA has a spin for the old, and one for the new BL. Is smartflash a windows-binary? Since I currently have no access to a windows-machine :-/.
Hi Make1 and Sreeprajay,
thanks for your recommendation. I'll also hit that thanks button if it helps me solve this, but first I've got two questions:
1st: As said above, I currently have no access to a windows-machine. Therefore I wanted to try working this out with nvflash on Linux. AFAIK this should be possible, even though there would be no nice menu-system. The question is if there's a difference due to the special drivers on windows which are mentioned everywhere? I ask that, because I've successfully rooted my buddies TP-Tablet on Linux with adb, and without any special drivers (which were said to be mandatory on windows).
2nd: What am I aiming for in Spyrosks AIOT? Instantly I'd think option 2B (Change Recovery with NVFlash) might help me. As in ProgMaqs Full-Brick-Repair. Then I'd look into the batch-Scripts, and simply manually execute the needed Steps.
Ok, so I dug up my old windows-tower from the attic, soldered a power-cord that I was missing, and fired it up. Took me more than 2 hours - thats what I meant with "no access to a windows-machine".
I ran Spyrosks AIOT, but no luck . The only possible ways to save this phone, are IMHO the nvflash based methods. But nvflash on windows reports the same error: "USB device not found".
Yes - I installed the driver out of the AOIT - but it seems that it cannot be activated for my phone. I think it's not in the right state to be recognized as a device that would need that driver, so windows won't activate it.
Attached is a screenshot of how the phone appears in my Device-Manager when connected in "S/W Upgrade"-mode.
Do you still think this phone can be saved somehow? I had high hopes as I read that this phone is nearly unbrickable
Come on, please someone help me. I'm not trying to be lazy here, or have someone else do the searching/thinking for me. I just can't figure out how to solve this - propably due to a lack of experience.
I don't think this is a simple problem - but there must be a reason why that phone is said to be 99% unbrickable. I hope I'm not the other 1% in this case.
Anyone?
I would have known what to do if the pc recognized your phone when you've installed drivers because almost exact problem happened to me few days ago.
Okay, now I will suggest random things well, I'm just trying to help :/
I suppose cwm isn't working?
Then about S/W Upgrade mode, have you installed APX drivers? Because when you connect phone in S/W upgrade mode with APX drivers installed then Device manager shows no errors.
You also mentioned that you restored a backup so it means you have latest backup of your system which you wanted to use. Tell me if I'm not correct. Then full wipe of your phone will fix everything, you will just flash a new rom, do the rooting stuff again and then you can restore your backup again.
maybe its because you are on linus, try restoring a STOCK GB KDZ if you are on the old layout, if you are in the new layout use a official LG smartflash, try that on windows and use AIO Toolkit !
Hey, thanks a lot! Actually the last Tip did the Trick!
After I downloaded and installed the full LG phone suite, I was able to restore the phone with the official LG support-tool. During the installation of the PC-Suite one or two new drivers were installed, which then lead to the phone beeing correctly recognized by the Windows 7 on the PC.
So to sum that up, and clarify the questions I brought up earlier:
Can the windows Drivers do more than what the native ones on Linux?
Absolutely yes! Only the drivers which came with the PC-Suite made my PC recognize the P990, which it didn't do before. Propably even the special drivers which come with Spyrosks AIOT depend on them (correct me if thats not true).
Can I restore my bricked phone with only Spyrosks AIOT?
In my case that did not work. Even after installing the PC-Suite and its drivers (including the support-tool drivers) the nvflash based methods in spyrosks AIOT did not find my device, which was connected over USB. But LGs support-tool did, and revived the device .
Hope that helps other people in my situation. The legendary unbrickability of this thing is proven once again
Thanks to all of you (Yesyesyes - I'll hit that button right away!)