Related
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
Update: Updated CWM recovery.New version fixes bootloop issue
Rooting:
This technique should work on any stock firmware.
First flash CWM recovery.Instructions are given below
Boot in CWM recovery and connect phone to PC
Download and extract the RootMe.zip package on your PC
Run runme.bat on PC while phone is in recovery mode
Reboot the phone after process is over.
Clockworkmod Recovery:
Download the cwm tar package
Put phone into download mode and connect to the PC
Flash the cwm tar package as PDA and wait for phone to reboot
Recovery download link: cwm-trebon.tar.md5
Note:
[1]The yellow triangle at boot is of no importance.Deal with it
Recovery Mode: volume up+ volume down + home + power
Download Mode: volume down + home + power
Hi i had rooted my phone as mentioned in this thread,i think i have a problem now don't if its related to rooting...
I had a software update notification this morning so i downloaded it but while installing i got an error like update failed...binary mismatch, after the phone booted i tried again now it says no update available...
Is it any way related to ur method of rooting....?
Galaxy ace plus vold.fstab file
HI guys,
I am new to this forum . i have tried swap internal and external SD cards in my galaxy ace plus s7500 . unfortunately i have taken backup to sd card . After modifying /system/etc/vold.fstab phone is unable to mount both sd cards
can any one please upload original vold.fstab of galaxy ace plus plsssss .
Regards,
Appaji .P
Many thanks for the info!
appaji04cn002 said:
HI guys,
I am new to this forum . i have tried swap internal and external SD cards in my galaxy ace plus s7500 . unfortunately i have taken backup to sd card . After modifying /system/etc/vold.fstab phone is unable to mount both sd cards
can any one please upload original vold.fstab of galaxy ace plus plsssss .
Regards,
Appaji .P
Click to expand...
Click to collapse
Here you go....
mb-14 said:
This guide is for rooting the Galaxy Ace Plus GT-S7500
Please follow these instructions carefully:
Download and unzip Odin3.zip package.
Download the ROOT.tar file.
Put the phone into download mode(volume down+home+power on) and connect to the PC.
Open Odin and flash the ROOT.tar file as PDA.Wait for the phone to reboot.
Now root using DooMLoRD's Easy Rooting Toolkit available from here
Enjoy full access to your rooted phone
Click to expand...
Click to collapse
Hey!
What does ROOT.tar includes? Can this be used on other samsung phones?
qzem said:
Hey!
What does ROOT.tar includes? Can this be used on other samsung phones?
Click to expand...
Click to collapse
which model?
i think i know...maybe qzem is trying to get it work on Galaxy S Advance...
logically, it should not work, since the ROOT.tar is built based on Galaxy Ace Plus's own boot.img... however, i am very interested to know how do you manage to modify the boot.img to allow access to DooMLoRD's Easy Rooting Toolkit for rooting purposes... that might help cos i'm actually has started researching rooting methods for Samsung new phones, since i planned to buy Galaxy S Advance as well..
kilsmap said:
i think i know...maybe qzem is trying to get it work on Galaxy S Advance...
logically, it should not work, since the ROOT.tar is built based on Galaxy Ace Plus's own boot.img... however, i am very interested to know how do you manage to modify the boot.img to allow access to DooMLoRD's Easy Rooting Toolkit for rooting purposes... that might help cos i'm actually has started researching rooting methods for Samsung new phones, since i planned to buy Galaxy S Advance as well..
Click to expand...
Click to collapse
You are right, man I am searching and trying every way to root Galaxy S I9070 Advace . Ben even unpacking and repacking system.img.d5, but with no success. Problem is I don't have enaugh knowlage in this, and I don't use linux, everything I did so far was in windows in Cygwin and on the phone it self when the shell was needed. Maybe we could put our heads together and figure this thing out ! You can PM, if you have any good ideas. I was playing with a thought of installing linux vitualy, and make some enviroment for compiling this android stuff. I have some knowlage about computers since I am computer engineer, but i work as system administrator in windows based environment.
Cheers
Well the steps are very easy & it should work on any android phone not just samsung phones.
First unpack the stock boot.img of your device.
Then open the default.prop file and set
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
and save the file.
Now repack the boot image and tar it.
Then you can flash it via Odin
The changes give us root access to adb shell and we can push the su binary and Superuser.apk via adb.
But if you are lazy then run any of the available rooting tools which copy the necessary files via adb(eg Doomlord's toolkit)
whoa...quite simple...thanks bro...but i seemed to read somewhere that everytime our phone reboots, especially for Samsung phones, it will read everything back from the boot.img, so as this exploit is quite simple, will the root stick? sorry for the crudeness of the question...im quite a noob in android development as well..haha...
kilsmap said:
whoa...quite simple...thanks bro...but i seemed to read somewhere that everytime our phone reboots, especially for Samsung phones, it will read everything back from the boot.img, so as this exploit is quite simple, will the root stick? sorry for the crudeness of the question...im quite a noob in android development as well..haha...
Click to expand...
Click to collapse
If using a root browser such as root explorer i make any changes to the files in the boot partition such as init.rc or default.prop then the changes will not persist after a reboot as the phone reads everything back from the original boot.img.
But if we change the the original boot.img(that is what we are doing here) and flash it then the changes will persist.
i see...thanks for the explanation...good job with the root guide for Ace Plus...
To qzem, yeah...im quite as much noob as most of the users here in xda...but maybe we have to do this in a Linux environment, cos i read somewhere for ROM making, its quite difficult to use Windows... now for me, rooting our Galaxy S Advance is quite probable, just that learning how to use Ubuntu just for making these exploits is quite unnerving... there are quite thorough guide for unpacking and repacking those .img files, but you have to be familiar with Linux...
mb-14 said:
Well the steps are very easy & it should work on any android phone not just samsung phones.
First unpack the stock boot.img of your device.
Then open the default.prop file and set
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
and save the file.
Now repack the boot image and tar it.
Then you can flash it via Odin
The changes give us root access to adb shell and we can push the su binary and Superuser.apk via adb.
But if you are lazy then run any of the available rooting tools which copy the necessary files via adb(eg Doomlord's toolkit)
Click to expand...
Click to collapse
How to unpack and repack boot.img? Is there any useful guide here. Can I pull boot.img straight from my phone or can I extract it from firmware (.tar file) on my pc, and how? Or do I need kernel source code, to compile insecure kernel? Thanks for your help!
now i have definitely run into some confusion here...your guide in remaking the boot.img is very clear, but the problem now is that i can't figure out where is boot.img located in Galaxy S Advance firmwares...all i have are system.img, cache.img, hidden.img, kernel.bin and modem.bin... is it in the kernel.bin? if so, how do i extract it?
Im not sure but i think unpacking tools are same as boot.img.There are many guides available online
i see...how do u manage to get CWM working for Ace Plus? do we have to root 1st for flashing CWM, cos i remember that it is not necessary... what are the files we need to port CWM to other devices?
kilsmap said:
i see...how do u manage to get CWM working for Ace Plus? do we have to root 1st for flashing CWM, cos i remember that it is not necessary... what are the files we need to port CWM to other devices?
Click to expand...
Click to collapse
Check this:http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Thanks for the CWM , now all we need is some custom ROMs , hope some developers step in....
Rooting Ace Plus
I am a noob in rooting stuff,i have never used p.c for rooting,despite being with android for 2 years,
My ques is-
will my phone be rooted after flashing root.tar as PDA?
or i have to use doomlord's rooting tool kit also?(i dont know to use)
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
Have tried Bin4ry v18 and another script but they didn't work.
The phone has JB 4.1.1. The Kernel is 3.4.0 dated Dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
Thanks for any help or advice.
Is now rooted, read on..
garyo said:
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
...
Thanks for any help or advice.
Click to expand...
Click to collapse
Me too. I've spent probably 6 hours today messing around with the 1.8 version script, on both windows 7 and Linux. It always fails the same place, with mount permission denied ... are you root?
I have other issues with the G9300 that I'd like to tackle, like WiFi range, but digging in requires root access. Here's hoping somebody smarter than I can find a way to root this thing.
wseverin said:
Me too. I've spent probably 6 hours today messing around with the 1.8 version script, on both windows 7 and Linux. It always fails the same place, with mount permission denied ... are you root?
I have other issues with the G9300 that I'd like to tackle, like WiFi range, but digging in requires root access. Here's hoping somebody smarter than I can find a way to root this thing.
Click to expand...
Click to collapse
Same here. I need root to build a custom CWM recovery.
Anyone has rooted phone that can help rip out the rom?
..
Finally. I've rooted my HDC G9300.
See my post in another thread here:
http://forum.xda-developers.com/showthread.php?t=1886460&page=165
My phone is now nicely rooted with no problems. But it's not an easy process.
wseverin said:
See my post in another thread here:
http://forum.xda-developers.com/showthread.php?t=1886460&page=165
My phone is now nicely rooted with no problems. But it's not an easy process.
The tutorial isn't clear about how to run Android Kitchen. In the Android Kitchen folder is a script called 'menu' that has to be executed by cygwin. Launch cygwin first with the .bat file in its install folder. Then, navigate to the 'menu' script. Hint: '/cygdrive/c/<path to Android Kitchen>/menu'
Nowhere does the tutorial say to copy 'Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip' onto your sd. You will want to do that before beginning the final recovery step.
Click to expand...
Click to collapse
Its great you figured out a root method, and thanks for sharing it :good:
I have just run through it on my phone and all has gone well until I got to where mobileuncle tools flashes the recovery.img. It needs Superuser access to do that and I don't have it. I am thinking it must be something to do with the Menu script you mentioned. How to you run that script? What is the command for it?
Thanks for any help!
Sounds like you're 95% there
garyo said:
I have just run through it on my phone and all has gone well until I got to where mobileuncle tools flashes the recovery.img. It needs Superuser access to do that and I don't have it. I am thinking it must be something to do with the Menu script you mentioned. How to you run that script? What is the command for it?
Thanks for any help!
Click to expand...
Click to collapse
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
wseverin said:
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
Click to expand...
Click to collapse
Finally, you rooted the phone. Do you think you could upload the rom somewhere? Others can just download it and flash without going through the entire process. Good Job!!
wseverin said:
From what you've written I will make a few assumptions. It sounds like you successfully did the rebuild with Android Kitchen, where it created a new recovery.img. And then you used SP Flash Tool to successfully transfer the new image to your phone.
You don't need mobileuncle. It's a great utility to have, but you don't need if for this process. Install it later when this is all done.
If the above assumptions are correct, you already have downloaded the modded recovery to your phone and you're 95% done. It sounds like all you need to do is put the zip install for su, superuser, and busybox onto your sd card, boot into recovery (upvolume+power), navigate to 'install zip from sd card', install the su-superuser-busybox zip, and reboot.
If that doesn't work, I suggest working your way back up the chain – re-downlod the new recovery.img; if that fails, rebuild the new recovery.img; etc.
Click to expand...
Click to collapse
Hi - Yes you are right, I have created the recovery.img and transferred it to the phone.
Thanks for the tip that I don't need to use mobileuncle.. So I have booted up into CWM and have the su-superuser-busybox zip on my sd card. Trouble is CWM doesn't recognise the sd card and says E: unknown volume. That is strange because android sees it fine when the phone starts.
I am still wondering if my problem is from the the android kitchen part. I wasn't able to run android kitchen. I think I better run through the process again. How did you bring up the 'menu' in kitchen? I ran cygwin first and then navigated to kitchens path and used /menu and also ./menu but just got an error message. Even dumped all of kitchens files into cygwins root directory in case I had messed up the navigation path but still got the same error message whenever I tried to run menu. How did you get it to run please?
Thanks for your help :fingers-crossed:
GT35pro said:
Do you think you could upload the rom somewhere? Others can just download it and flash without going through the entire process.
Click to expand...
Click to collapse
I have uploaded the recovery.img that I created here. Remember, because it works on my phone is no guarantee that it won't break yours. You use it solely at your own risk. Also, you will still need to use CWM to install the su+superuser+busybox zip from your sd.
Next problem - no 3G
Having the phone rooted, I've gone on to the next problem that has no ready solution.
That is, no 3G. I use the AT&T network in the USA. AT&T uses WCDMA on 850MHz and 1900MHz for their 3G service. The HDC G9300+ doesn't support WCDMA at 1900MHz, which is the band that AT&T uses most. Where I am (Phoenix AZ) there is only 1900MHz service, which means that I can't get any 3G. Only 2G "Edge".
The problem *might* be remedied through software - or maybe not. If the MTK6577 radio doesn't support 1900MHz in some hardware sense, then the game is over. But I doubt that for two reasons. First, from a marketing standpoint, the AT&T network is too big to just ignore when designing a generic platform like the MTK6577. Second, from a hardware standpoint, the transceiver frequencies are synthesized from one base oscillator through a set of on-chip frequency multipliers and dividers. If the MTK6577 can generate frequencies in the 2100MHz band it can almost surely generate frequencies in the 1900MHz band. What's required is a software driver that properly sets the multipliers and dividers.
My bet is that somewhere out there in the world there is a software driver for the phone's radio that can set the chip to work in the 1900MHz band.
Can somebody find that driver so that we can bundle it into a ROM for this phone? Or a tool to adjust the driver that's bundled with the phone?
Please tell me
garyo said:
has anyone got a root method that works for the hdc galaxy s3 g9300?
Have tried bin4ry v18 and another script but they didn't work.
The phone has jb 4.1.1. The kernel is 3.4.0 dated dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
thanks for any help or advice.
Click to expand...
Click to collapse
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
wseverin said:
I have uploaded the recovery.img that I created here. Remember, because it works on my phone is no guarantee that it won't break yours. You use it solely at your own risk. Also, you will still need to use CWM to install the su+superuser+busybox zip from your sd.
Click to expand...
Click to collapse
Thanks for uploaded your recovery file. I thought I would try that before going through the process of redoing mine. This time it kicked straight into CWM without any sdcard errors, so was able to install the zip file. It is now nicely rooted and has been running for several hours, and as yet I have found no problems.
Great job and thanks for sharing your knowledge :good:
joneswilson02 said:
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
Click to expand...
Click to collapse
http://www.fastcardtech.com/goods.php?u=53399&id=8113
First time I purchased from them, found them very good and had no problems. Took about 15 days to get it. Considering there were xmas & new year holidays at the time it was pretty good.
How to root your HDC Galaxy S3 G9300+
For those wanting to root their HDC Galaxy S3 G9300+ phones follow these steps;
Download wseverin's 'recovery.img' from post #10.
Download my 'MT6577_Android_scatter_emmc.txt', 'su+superuser+busybox.zip', 'SP_Flash_Tool_v3.1224.01.rar' and 'MT657x_USB_Win7_Driver.zip' files that I have attached to this post.
Install the USB drivers to your computer if you don't already have them.
Copy the su+superuser+busybox.zip file to your phones SD Card.
Run Flash Tool (Flash_tool.exe) in administrator mode.
Load my scatter file.
Next, backup your original recovery file (This is very important in case something gets messed up) Do this using the 'Read-Back' function. Select Hex and enter 0x1588000 for Start Address and 0x600000 for Length. Before clicking the Read Back button, shutdown your phone and remove the battery and USB cable. Next click Read Back, plug in the USB cable and replace the battery (But do not switch the phone on) The software will backup the file and come up with an OK window if successful.
Next flash your phone with wseverin's recovery.img. Do this from the Download tab in Flash Tool and tick the Recovery option. Before pushing the Download button you will also need to shutdown the phone, remove the battery and USB cable as above.
Next start the phone holding the volume-up + power buttons. This will boot the phone into CWM. Choose 'Install zip from sdcard', then 'choose zip from sdcard', navigate to the su+superuser+busybox.zip file and select yes to install it.
That's it! So easy!!
If you followed the steps correctly, after you reboot the phone it should have root access.. However, be warned that your phone could be bricked if something goes wrong or your phone is a different model, so do this at your own risk and backup your original first!
PS: thanks to wseverin for the modded recovery file and being the 1st to root this phone.
joneswilson02 said:
brother please tell me
where from you bought this phone "hdc galaxy g9300"???
I also want to buy this phone
Click to expand...
Click to collapse
Do I detect a hint of cynicism?
It seems to be a decently built phone. The display is good; actually better resolution than many competing models. Fit and finish are as good as you'll get anywhere. The capacitive touch screen is just fine. GPS, WiFi, and Bluetooth all work well except that the WiFi range is a bit anemic. Software is pretty much standard Android Jelly Bean. I consider it worth what I paid for it, especially since I am not about to spend 3X that for a cell phone. Oh, and it actually makes and receives phone calls!
help me
Help me please, i've bricked my g9300+.
i need a rom.zip to flash with recovery or complete rom to flash with spflashtool.
help me!!!!
bersarak said:
Help me please, i've bricked my g9300+.
i need a rom.zip to flash with recovery or complete rom to flash with spflashtool.
help me!!!!
Click to expand...
Click to collapse
How do you have brick your phone?
With the garyo's guide?
Thanks
I have a G9300+ and I want to root it
root Star G9300+
garyo said:
Has anyone got a root method that works for the HDC Galaxy S3 G9300?
Have tried Bin4ry v18 and another script but they didn't work.
The phone has JB 4.1.1. The Kernel is 3.4.0 dated Dec 3 2012. The build number is; e1920_v77_zlh_9p017_asx_20121203
Thanks for any help or advice.
Is now rooted, read on..
Click to expand...
Click to collapse
Hello,
First of all, please excuse my english...
I have a Star G9300+ smartphone with the same JB 4.1.1, same kernel (3.4.0 dated Dec 3 2012), same build number (e1920_v77_zlh_9p017_asx_20121203) than yours, but 1Gb RAM memory.
Could I use the same method to root my smartphone? How much RAM have yours?
Thanks!
xnicks said:
Hello,
First of all, please excuse my english...
I have a Star G9300+ smartphone with the same JB 4.1.1, same kernel (3.4.0 dated Dec 3 2012), same build number (e1920_v77_zlh_9p017_asx_20121203) than yours, but 1Gb RAM memory.
Could I use the same method to root my smartphone? How much RAM have yours?
Thanks!
Click to expand...
Click to collapse
Yes mine is also 1Gb RAM. I have read that HDC and Star are the same, however I don't know this for sure. This is where I purchased my phone;
http://www.fastcardtech.com/goods.php?u=53399&id=8113
Does yours look the same??
If yours looks the same you could always try it I suppose, but make sure you backup your phones entire ROM first. That way you can reinstate the original in case it doesn't work.
I bought a chinese phone Telsda/TSD A198 . The firmware reports it as an MT6589 CPU but the computer reports it as a spreadtrum phone. I need to root the phone to get rid of some apps on this to make space. Also without rooting is there anyway to backup the stock rom on my phone before I mess up to root? I have seen a method on XDA but that requires root. Now I am trying to backup to get to rooot !!!! Also I have also researched researchdownload but without a ROM backup and not knowing which CPU model to flash its impossible to it right. I also looked into mtkdroidtools and it tells me "unstructured rom backup not possible" , so I am guessing its a fake MTK CPU that is being reported by tweaking the firmware.
This is the link to the phone
http://www.aliexpress.com/item/New-...3-MTK6589-4-0-INCH-smart-phone/879312434.html
Any help is appreciated.
Thanks
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Villis1251 said:
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Click to expand...
Click to collapse
Ok, first my honest suggestion dont buy this phone it has pathetic performance. For the same price go for a real MTK6577 dual core. ANyways below are the answers to your question
> Real CPU frequence seems to be 1GHZ
>Mali 300 GPU
>no 3G
>no GPS
>256MB RAM and 256 MB ROM
>I am not sure if its real JB and I cant figure it out but it says JB 4.2.1 and the kernel is 2.6.35.7 and hence I guess its a fake JB. The funny part is under baseband version it says "MT6589 1.5GHZ quad cores" !!!! offcourse it means the firmware/build.prop has been tweaked and is reporting false values. Also when I ran Antutu it gives a score of about 3500 which is useless when compared to what is required to run games ..etc. I hope I have helped.
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
custom recovery
Villis1251 said:
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
Click to expand...
Click to collapse
Finally I was able to stitch a ROM, using bits and pieces from different sources and its perfectly working. I only need to build a CWM recovery image based on the recovery image I have attached. Can someone help me do that? so that I can do a nandroid and ump my rom in case someone needs to recover their telsda A198
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
aspirus said:
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
Click to expand...
Click to collapse
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
hel me please!!!
braindia said:
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
Click to expand...
Click to collapse
braindia hello ... I bought the same phone and I have problems with the sims do not have to call or receive coverage ..... could you explain you did and how you did it?
there say that you put android 4.0 not work quite right? ... greetings from chile
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
aspirus said:
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
Click to expand...
Click to collapse
ok looks like lot of people have issues with this phone. Its a junk phone, all fake stuff on it. ANyways I will upload the firmware images and then you guys can use those to flash on your phones. Below is what I have done
1> Patched a 4.0.4 ROM which works perfectly
2>Removed useless preinstalled apps
3>rooted
4>Perfectly working dual sim,GPRS,WIFI,Camera,Camcorder .,..etc etc
4>The issue is with the IMEI, because of the way its stored you guys will need to use your own NV files.
The only thing I havent been able to do is get a working CWM, but you dont need it as you can flash the firmware images using researchdownload.
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
working firmware files
aspirus said:
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
Click to expand...
Click to collapse
Here you go, you flash at your own risk. If there are bricks/issues you are responsible for your own device.(Standard disclaimer) . I have uploaded all the files except system and NV, system image is kind of big and I am trying to figure it out where to upload it.. You dont need to worry about NV unless you completely erased the flash(never erase the complete flash or format it). If you havent done so then you are good to go.
Please google to find researchdownload and use it to flash the attached files. I wont be able to write the tutorial on using researchdownload so google is your friend.
I have also uploaded the gapps zip which will get you up and running with google play store. You need root to copy these files directly into system/apps folder.
I will be able to upload a system file which works, not the patched one with google play store, root ...etc etc . You do that on your own, I will help you do it.
Thanks !
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
aspirus said:
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
Click to expand...
Click to collapse
your phone is probably not detected due to 2 reasons
1> windows disabling non signed driver.. if thats the issue while you start the PC keep hitting F8 you will be shown various options
Select disable windows driver signature enforcement
2> Second reason is you need to add an entry in adb_usb.ini file I think its 0x1782 which is for SPRD enumerator. There are tons of links for this one of which is
http://forum.xda-developers.com/showthread.php?p=37271476
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
aspirus said:
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
Click to expand...
Click to collapse
getting root is simple, flash a CWM I have attached one, please note this does not work but it works enough to get you root. follow the below steps
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
4> perform mount /system and then exit shell
5> push su binary & busybox directly to /system/bin (from the command prompt using adb push)
6>change permissions for su & busybox to make them runnable
7> exit from the shell and reboot
8> do adb install superuser.apk(optional this can be done later)
thats it you have su, and then you can sideload the superuser apk or you can do step 8 as above. Once you have rebooted and verified that you indeed have superuser you can flash the stock recovery back on the phone.
Note note note : The CWM recovery image is only for you to get root and it doesnt work and doesnt show the normal CWM options... you have been warned. You should flash your old recovery/stock recovery after you have achieved root.
Also can you give me the stock recovery image so that I can build a working CWM out of it. I overwrote mine and now stuck with another recovery which works but is not for this phone.
Thanks
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
aspirus said:
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
Click to expand...
Click to collapse
Hmm... I am not sure what is the issue please try attached drivers and pray that they work . use either 64bit or 32bit depending on your OS.
Also you said you have the firmware can you upload it ? I can do something more with the stock/original firmware, so please upload it
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
aspirus said:
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
Click to expand...
Click to collapse
Thanks ... I know this phone is a waste of time and money both. I am just using this phone as an experiment platform knowing fully well that this piece of junk will die anytime.
I tried methods with Send_command.exe on LG H410 Smart Wine (Lilipop 5.1.1) and also receiving #FAIL from Send_Command . But LEAVE command is working fine and restarts the phone. How can I make root?
Firmware v10c:
drive.google.com/file/d/0BzNfkgQOM0SudTREcFNQZTNhdmc/view?usp=sharing
opensource firmware v10a:
drive.google.com/file/d/0B2QhEXa2ySgkX21kZzl0TC1FQlU/view?usp=sharing
if it help
Soft-Man said:
I tried methods with Send_command.exe on LG H410 Smart Wine (Lilipop 5.1.1) and also receiving #FAIL from Send_Command . But LEAVE command is working fine and restarts the phone. How can I make root?
Firmware v10c:
drive.google.com/file/d/0BzNfkgQOM0SudTREcFNQZTNhdmc/view?usp=sharing
opensource firmware v10a:
drive.google.com/file/d/0B2QhEXa2ySgkX21kZzl0TC1FQlU/view?usp=sharing
if it help
Click to expand...
Click to collapse
If not all but most except maybe certain samsung devices are easily rootable without PC by using kingroot v4.5.2 latest version, download and install and sit back watch successfully root your phone
Sent from my SM-N920C using Tapatalk
[email protected] said:
If not all but most except maybe certain samsung devices are easily rootable without PC by using kingroot v4.5.2 latest version, download and install and sit back watch successfully root your phone
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I tried kingroot kingoroot and other similar techniques, none of them does not give the desired result.
Soft-Man said:
I tried kingroot kingoroot and other similar techniques, none of them does not give the desired result.
Click to expand...
Click to collapse
Have you tried latest version of kingoroot?
Also try PC and android version of v/iROOT
Sent from my SM-N920C using Tapatalk
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
There's also rootgenius PC version that have worked #!
Sent from my SM-N920C using Tapatalk
[email protected] said:
Have you tried latest version of kingoroot?
Also try PC and android version of v/iROOT
Sent from my SM-N920C using Tapatalk
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
There's also rootgenius PC version that have worked #!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Yes, tried. Not working. and where is samsung if LG?
http://www.kingoapp.com/root-tutorials/how-to-root-lg.htm
That's what I've used for mosT LG and never failed, you're first to say this ain't working, always try latest version of way ever you're using
Sent from my SM-N920C using Tapatalk
[email protected] said:
that's what I've used for mosT LG and never failed,
Click to expand...
Click to collapse
in this case it does not work
Yes, of course I use the latest versions of software
Soft-Man said:
I tried methods with Send_command.exe on LG H410 Smart Wine (Lilipop 5.1.1) and also receiving #FAIL from Send_Command . But LEAVE command is working fine and restarts the phone. How can I make root?
Firmware v10c:
drive.google.com/file/d/0BzNfkgQOM0SudTREcFNQZTNhdmc/view?usp=sharing
opensource firmware v10a:
drive.google.com/file/d/0B2QhEXa2ySgkX21kZzl0TC1FQlU/view?usp=sharing
if it help
Click to expand...
Click to collapse
Have you found a solution to your problem yet?
BTW, which version of the smartphone are you using? Europe/USA/carrier etc... ?
hey there soft-man !
obviously you found a a solution to install twrp on the h410, i saw it at http://4pda.ru/forum/index.php?showtopic=682101
could you please make a small tutorial in english and post it here ?
.. and reupload the tools we need to install twrp (LG_H410__Flash_Recovery.rar) << dead link
i already installed root and crashed my device by deleting to the wrong system app ... reinstall fw via lg flash tool fails
now twrp is my only hope !
thanks a zillion !!!
If there is a chance to root the LG h410, i totally supportswitcher's request for a english tutorial and new links for the tools needed. Thanks in advance
+1 for translation from Russian forum
once again: does anybody here managed to (re)flash the firmware on the h410 ?
my device is trapped at the android logo ;(
what i did is unsuccessfully tried to flash a *.kdz with flashtool 2014. lg bridge is aborting update and lgup shows device not supported
download modus is available but cant connect device via adb.
any help is greatly appreciated
Ok, after spending a few hours on my LG smart wine (EU version) and with the help of the guys on 4PDA, here is my little how to for rooting our LG H410:
Beware, I'm not responsible if anything goes wrong with the manipulation on your phone and all this was only possible thanks to the people over at 4PDA.ru, thanks to them! I am/was on firmware V10e-EUR-XX official.
1) Use Kinguser apk to get root on your device (don't worry, you can uninstall it later through superSU).
2) Install Flashify and backup your current/original recovery. You'll need to be root to use flashify, that's why we need #1) first. You'll find flashify on the play store.
3) Install TWRP recovery either through flashify or with flash.bat found in LG_H410__Flash_Recovery.rar (this one will be russified, but you can always go through flashify and install the english version afterwards !EDIT!: Since the file was too large to upload, I took the russian recovery.img out of the zif archive. You'll will have to unpack it, copy the recovery_en.img provided after having renamed it to recovery.img, and it should work).
4) Install latest stable or Beta superSU.zip (search google for the official maintainer/version and copy it on your microSD card) from within TWRP.
5) Restart the phone
6) If you open superSU, it will ask you possibly to update the binaries and then to uninstall the other software that might interfere (it's Kinguser). So just say yes and it will take care of everything.
7) (optional) If you're like me needing more storage place on your device, install Link2SD from the play store. If I'm right, you'll need to have a second partition on your SD card (Ext4 file system), after the Fat32 one, to be able to move your apps to the SD card with Link2SD. I even bought the Plus version in order to be able to move the whole app.
You can use MiniTool Partition Wizard Free to set your partitions on th card. Add the new primary partition in Ext4 AFTER the Fat32 one, otherwise windows won't recognise your card.
I forgot to backup my stock recovery before flashing the new one, but all should be fine for you if you do it in the order above.
You have to unpack recovery_en.zip and flash the .img you have in the folder, don't flash the zif through TWRP, it won't work. And don't forget to rename it to recovery.img if you use it within the LG_H410__Flash_Recovery folder.
Once again, thank the people who did the job over at 4PDA, especially Soft-Man for trying out things, they did all the work. I'll try to attach the files needed here.
Hope it will help someone, have fun with your phone!
Sure it is interesting .... just one wuestion ... what about if i stop after step 1? If kinguser gets me root i personally don't have any need to go further ...
Of course you can, if you want to keep the official recovery (probably better if you want to be able to install official OTA updates).
I would still install SuperSU through flashify though (I think you can do so without having a modded recovery installed, but I'm not sure), and get rid of Kinguser the way I described it. Thing is I don't really trust those rooting apk, you never know what they install and what they keep track of on your phone... Not sure what's left of it when you uninstall it either.
Tell us how it worked for you.
:laugh:
Vuche said:
Ok, after spending a few hours on my LG smart wine (EU version) and with the help of the guys on 4PDA, here is my little how to for rooting our LG H410:
Beware, I'm not responsible if anything goes wrong with the manipulation on your phone and all this was only possible thanks to the people over at 4PDA.ru, thanks to them! I am/was on firmware V10e-EUR-XX official.
1) Use Kinguser apk to get root on your device (don't worry, you can uninstall it later through superSU).
2) Install Flashify and backup your current/original recovery. You'll need to be root to use flashify, that's why we need #1) first. You'll find flashify on the play store.
3) Install TWRP recovery either through flashify or with flash.bat found in LG_H410__Flash_Recovery.rar (this one will be russified, but you can always go through flashify and install the english version afterwards !EDIT!: Since the file was too large to upload, I took the russian recovery.img out of the zif archive. You'll will have to unpack it, copy the recovery_en.img provided after having renamed it to recovery.img, and it should work).
4) Install latest stable or Beta superSU.zip (search google for the official maintainer/version and copy it on your microSD card) from within TWRP.
5) Restart the phone
6) If you open superSU, it will ask you possibly to update the binaries and then to uninstall the other software that might interfere (it's Kinguser). So just say yes and it will take care of everything.
7) (optional) If you're like me needing more storage place on your device, install Link2SD from the play store. If I'm right, you'll need to have a second partition on your SD card (Ext4 file system), after the Fat32 one, to be able to move your apps to the SD card with Link2SD. I even bought the Plus version in order to be able to move the whole app.
You can use MiniTool Partition Wizard Free to set your partitions on th card. Add the new primary partition in Ext4 AFTER the Fat32 one, otherwise windows won't recognise your card.
I forgot to backup my stock recovery before flashing the new one, but all should be fine for you if you do it in the order above.
You have to unpack recovery_en.zip and flash the .img you have in the folder, don't flash the zif through TWRP, it won't work. And don't forget to rename it to recovery.img if you use it within the LG_H410__Flash_Recovery folder.
Once again, thank the people who did the job over at 4PDA, especially Soft-Man for trying out things, they did all the work. I'll try to attach the files needed here.
Hope it will help someone, have fun with your phone!
Click to expand...
Click to collapse
Thank you very much.
When I work as the indicated method from you, root has come. (LGS01 of a Japanese local edition of H410).
By the way I can't start bootloader moode in LGS01, can you start it in H410?
When it's done, please tell me the way which can be done.
I'd like to use LGS01 by a DIAG mode.
(I'd like to add a frequency.).
Vuche said:
Of course you can, if you want to keep the official recovery (probably better if you want to be able to install official OTA updates).
I would still install SuperSU through flashify though (I think you can do so without having a modded recovery installed, but I'm not sure),
Click to expand...
Click to collapse
Yeah, i get it. My goal is just to get root and being able to install titanium backup. No need for further modding. I will investigate about installing SuperSU through flashify with stock recovery.
:good:
still looking for a way to flash my bricked h410
..sorry to bother you guys, but where else to ask for help if not at xda ?
After finally reactivating my phone i like to share some bugs in stock firmware.
First of all LED notification: Is there a workaround for the blinking time, i find 15 seconds are much to long, i like to have 2 seconds. Tried some third party apps but the ideal solution would be by modyfing the stock app.
Second the T9: Its horrible ! Is there a way to switch it off ? By deleting the XT9. apk i totally messed it up and only have the numbers left.
Third of all, the keyboard .. Is there a good alternative with bigger (resizable) keys. Currently am using big buttons keyboard but am not really happy with it
I try to root LG H410 (EU version) but after installing Kinguser apk, root was not available so Flashify rapport an error about impossibility to access root.
My version of software is V10c-260-01