Hello i have made an official update to android 1.6 from Rogers rom V10Q .
Everything runs smoothly but my problem is that i cant set root permissions or flash it to an other rom.
Because there is no Fastboot mode in this version and also at the hiden menu there is no "Enable Root Permission" option, so i cant flash it in any used methods.
I tryied becoming root with Z4Root and AndRoot but no success.
Does anyone know how to root and/or flash this version?
Thank you.
You need to downgrade to an older firmware - one that still has Fastboot enabled. Once you've done that, I'd suggest using the OpenEtna firmware instead of the official firmware. OpenEtna is based on Cyanogen's Android 2.2, so it is much better than the official firmware.
Check the official OpenEtna site and forums for more info/help.
http://code.google.com/p/openetna/
http://forum.openetna.com/index.php
Thanks for your reply.
My problem was that i could not downgrade it to any previous version.
The Lg utils was crashing always and i think that it was because i was not root according to this thread lg-phones.org/how-to-flash-lg-eve-etna-gw620.html[/url] which steps i was following each previous time i had flashed from an official cab file with success.
I had also tryied some automated flashing utilities but none of them worked.
I have finally made it with the above way,but i had to shut down the phone and start the flashing procedure while it was still booting.
I dont know why but only this method worked.
I have the same problem, I couldn't make a nandroid backup before udate to V10Q, which is the official release from LG. The "root enable" in the hidden menu by dialing 3845#*620#. It's not there.
I have used link to make a nandroid but with no root there is no nandroid .
I tried to find V10F which is the original 1.5 rom, I suppose this rom has fastboot, but I don't know.
Regards,
Mauricio
I have succesfuly rooted V10Q with this tool http://forum.xda-developers.com/showthread.php?t=803682 but you have to replace the "su" file located in the downloaded folder with the one included in this link from system/bin folder http://forum.xda-developers.com/showpost.php?p=6499147&postcount=1 (the "cd" version).
Just click root and averything works perfectly!
sport_billy said:
i have succesfuly rooted v10q with this tool http://forum.xda-developers.com/showthread.php?t=803682 but you have to replace the "su" file located in the downloaded folder with the one included in this link from system/bin folder http://forum.xda-developers.com/showpost.php?p=6499147&postcount=1 (the "cd" version).
Just click root and averything works perfectly!
Click to expand...
Click to collapse
yaaaa
its work also for me bu same method
thanx man
how do you get past the read only files system?
sport_billy said:
I have succesfuly rooted V10Q with this tool http://forum.xda-developers.com/showthread.php?t=803682 but you have to replace the "su" file located in the downloaded folder with the one included in this link from system/bin folder http://forum.xda-developers.com/showpost.php?p=6499147&postcount=1 (the "cd" version).
Just click root and averything works perfectly!
Click to expand...
Click to collapse
ya right i dont believe you guys cause ive been trying the exact same thing and it does nothing!!!!!!!!!!!!!!!
I just successfully rooted after doing the LG upgrade to 1.6.
You need to use the superoneclickv1.5.5 not the most recent version.
Then take the superuser.apk and su files as per the instructions from the previous poster making sure you get the donut.cupcake version and put them into the directory where you installed s1c replacing the files that were previously installed.
There is no need to go into the hidden menus and enable root access as it is default in the 1.6 firmware. (and no longer an option)
Related
Hi
Anyone struggling to root using "SuperOneClickv2.1.1-ShortFuse" can still use the same app with new exploit "zergRush" (see in http://shortfuse.org/)
Using SuperOneClickv2.1.1 I could not root with the existing exploits "GingerBreak" or "psneuter" whereas the new exploit works.
Unzip the attached file and copy in to the "Exploits" folder under the folder "SuperOneClickv2.1.1-ShortFuse".
Now open the app and select "zergRush" instead leaving it to "Auto" under exploits (you can see this on the top right of "SuperOneClickv2.1.1" app.
Hope it helps.
Or download SuperOneClick 2.2
http://shortfuse.org/?page_id=2
adixtra said:
Or download SuperOneClick 2.2
http://shortfuse.org/?page_id=2
Click to expand...
Click to collapse
best choice
smohanv said:
Hi
Anyone struggling to root using "SuperOneClickv2.1.1-ShortFuse" can still use the same app with new exploit "zergRush" (see in http://shortfuse.org/)
Using SuperOneClickv2.1.1 I could not root with the existing exploits "GingerBreak" or "psneuter" whereas the new exploit works.
Unzip the attached file and copy in to the "Exploits" folder under the folder "SuperOneClickv2.1.1-ShortFuse".
Now open the app and select "zergRush" instead leaving it to "Auto" under exploits (you can see this on the top right of "SuperOneClickv2.1.1" app.
Hope it helps.
Click to expand...
Click to collapse
Somehow I tried 2.2 but it doesn't work (on windows 7 x64), so thank you for providing us this exploit file to run with 2.1.1.
SuperOneClick 2.2 uses ZergRush to exploit GB on LG Optimus 3D (see image attached)
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
sounds like you're totally lost. I don't know what a recovery.img is, well I guess most android phones have a recovery partition and a boot partition and you would flash a recovery.img to those but the galaxy s series doesn't work anything like that.
lets start with you sharing some information. open settings>about phone and tell me the baseband and android version. because if I have to guess you are trying to use a froyo proceedure that was only needed before custom kernels existed and you're trying it on stock gingerbread firmware, either a Rogers phone or a phone that has been flashed with a gingerbread leak.
also do you mean miui??? auto correct is a *****. and if you flash miui then why an old build? wouldn't you want 2.3.7???
singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
huh .....
oh and this should be in the [email protected]
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
singhtjay said:
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
Click to expand...
Click to collapse
well first off its not a .img its a binary file with no extension a .img is something you get when you dump a partition or drive on a low level so all the Metadata and everything is copied exactly and it would be used for reproducing a drive as a backup or on another device, well it could be any extension really but .img is common.
other androids have a different partition layout and may have a recovery partition.
now what is going.g on is you are trying to do a proceedure for froyo on a gingerbread rom. Samsung changed the boot scripts making it impossible to use cwm without a custom kernel. the boot scripts are in the initramfs which Samsung uses in place of the boot partition which means cwm and init.d support can't be added without replacing the whole kernel.
good news is Samsung has a flash tool called Odin. and there is an open source substitute called heimdall and if you are rooted there is a phone based program called sgs kernel flasher that will flash the kernel. look into the Rogers infuse root thread. the root kernel will also give you cwm. you could also use the hellraiser kernel, entropy's dd kernel, or the infusion gb kernel.
sorry for posting new thread but I don't know where to ask...can anybody please tell me tge new update 4.5.269 and someting3..is it the new version of gingerbread,is it safe to update..please tell me...
The new update is 4.5.629. It goes from Gingerbread 2.3.3 to Gingerbread 2.3.4, so a slight update. There are a few bug fixes, but it has a number of undesirable things.
1) 4.5.629 is currently not rootable
2) You cannot simply return to an earlier version via SBF.
You can overcome the first by using Voodoo Rootkeeper or similar to root on your current version, back up root with Rootkeeper and then update.
Recently, a method was found for this release to unbrick phones damaged by attempts to SBF or from bad ROMs: http://rootzwiki.com/topic/23207-how-to-sbf-unbricking-root-d2g-629 This also allows users who did upgrade to 4.5.629 to return to the previous version, root there and then upgrade again.
So it is sort of safe, but not ideal. The changelog is here, decide if the bug fixes are important enough for the added inconvenience
http://support.verizonwireless.com/pdf/system_update/droid_2_global.pdf
ok...thank u very much +1..I prefer not to update for now,and by mistake ,i select yes button in the update prompt,and its in the pull down bar,stucked and is ready to start downloading as soon as I connect to wi-fi,how will I cancel the download
You can block the update by renaming these files (e.g., append ".bak" to each filename):
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
Since these are in /system, renaming them requires root privileges and a root-enabled file manager (such as Root Browser Lite, available in the Google Play store).
ok..thanks,will do that,but after doing that,will I be able ro manually update it,or all the updates have been blocked???
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
jabberwockish said:
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
Click to expand...
Click to collapse
okok..thanks man +1
edit : i got this 'failed to rename file' error ..what should I do??
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
jabberwockish said:
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
Click to expand...
Click to collapse
the app that u suggested me,root browser lite and my phone was rooted and also have been granted superuser's permissions..
You didn't remount /system in Read/Write mode.
Gasai Yuno said:
You didn't remount /system in Read/Write mode.
Click to expand...
Click to collapse
please tell me how to do that
Root Explorer has a button for that.
“adb remount” when connected to a PC with USB debugging enabled will do that as well.
It's also possible to do from the terminal emulator, however I don't remember the exact command.
i can't find that button,by long pressing the file/folder or what?
It looks like this app defaults to RW once it gets superuser permission (GY was referring to Root Explorer, a different app). How about copying a system file, does that work?
Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.
TheJokah said:
Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.
Click to expand...
Click to collapse
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.
ajent said:
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.
Click to expand...
Click to collapse
I'm having the same issue with upgrading 10G. maybe there is a way in the ota Package
EDIT:
I found this link http://forum.xda-developers.com/showthread.php?t=2699123 to force an update using the dlpkgfile from ota. I wonder if it could work for G4 also??
@TheJokah @ajent. Don't need to be rooted. Root Browser will be able to view the directory without root permissions. (I use it all the time to browse system partitions and files on unrooted devices). You can do a lot with Root Browser without root. You just can't make changes.
When the fota is available you will find it in /cache/fota
I have captured several OTAs for various devices this way...
EDIT: Make sure to copy the file after it downloads and before restart, otherwise the file will be deleted before you get it.
That is good info, thanks.
I'm pretty convinced flashfire installing the xposed zip does something that isn't reverted when flashing the unrooted system image. I used my limited knowledge to look at that xposed zip and it seems like only modifications are made to /system so it should be removed when flashing back unrooted image. I really don't know, but hope somebody can figure it out lol.
This is my first time rooting my phone (tried rooting an o+ phone but couldn't unlock the bootloader) and I want to know how to my get phone's firmware. I tried using the Samsung Firmware Downloader but it won't accept my model and region.
I've tried using SuperSu to root but Root Checker says root access wasn't properly installed. What do I do now? Can I download a different firmware from a different site and is it safe? Does showing my pda code safe?
Edit: Forgot to mention I've already flashed TWRP.
Excuse me but what is your region and model number
tech-mаn said:
Excuse me but what is your region and model number
Click to expand...
Click to collapse
Never mind, I manage to download the firmware and root my phone thanks to Samsung Downloader. I wasn't able to download it at first because I keep using XXU (the one I saw in *#1234#, samsung firmware) as my region but it was actually XTC (I checked Software information in the About Phone).
Ok
if twrp is installed
root the phone with magisk
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
Maybe it'll work
MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
first root your device
then use mt manager to access build.prop file
i tested this in my sm-t585 with lineage os custom rom
alireza9082 said:
then use mt manager to access build.prop file
Click to expand...
Click to collapse
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
MasterKwonKaichi said:
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
Click to expand...
Click to collapse
as i said
use mt manager to save changes in build.prop
Since our system is F2FS you can't modify system it stays RO you can make a magisk module yourself to modify build prop also don't use supersu rooting is very easy just flash twrp then flash magisk. I'm making a custom rom which I'm hoping to release soon that's ext4 but I'm limited by time and the recent events from where I live so I can't give a ETA