Related
ummm.. My phone said it needed to update, I said, ok, it installed restarted and now there is a little green guy with a triangle and an explanation mark in the middle of the triangle..
I just rooted my phone about a week ago, Sprint said it needed to update.. Am I to never update my phone? Its a stock rooted phone.. But now I think its bricked..
Should I take the battery out and try to reboot?
ok... I just took the battery out and restarted the phone.. Came back up.. after sitting idle for about 10 seconds, the message came up again and asked if I wanted to update to 3.xxxxxx.xxx.xxxx.x or whatever it is.. Do I want to try to install this update? Whats the deal with stock rooted phones? can we upgrade or no?
Thanks guys!
Are you rooted?
If Yes: Do you want to stay rooted?
If you're stock, unrooted, I would update. 3.29 is quite a bit better from a variety of perspectives. You can always root again in the future.
drivendaily said:
Are you rooted?
If Yes: Do you want to stay rooted?
If you're stock, unrooted, I would update. 3.29 is quite a bit better from a variety of perspectives. You can always root again in the future.
Click to expand...
Click to collapse
I just rooted my brand new phone 3 days ago, I bought it 4 days ago..
1.Are you saying I cannot upgrade it because of this?
2.Should I unroot the phone and get the upgrade? what is it exactly?
3.I did the 1 click root option and it worked fine, how would I reverse this?
If you update OTA you will lose root. If you wish to keep your root then you need to flash a rooted ROM.
As far of "Stock rooted roms" there are basically two kinds
DeOdex roms let you flash themes, other customizations
DeOdex 3.29
Odex roms are basically as close to the stock rom as possible (just rooted)
Odex 3.29
Or you can flash Fresh, Baked Snack or any number of roms in the Development section...
I dont get it.. Isn't everyone in my position?? This update just came out today right?
I know so many people that just have a rooted phone, no kitchens or roms or anything else.. Just a stock rooted phone..
So now this update comes out and I am forced to get some premade rom?
Is there a way I can just unroot my phone.. Get the update and reroot the same way I just did?
Thanks
Your not forced to install it. If your stock you can update and re root or you can find the update zip and flash through recovery.
fastfed said:
I dont get it.. Isn't everyone in my position?? This update just came out today right?
I know so many people that just have a rooted phone, no kitchens or roms or anything else.. Just a stock rooted phone..
So now this update comes out and I am forced to get some premade rom?
Is there a way I can just unroot my phone.. Get the update and reroot the same way I just did?
Thanks
Click to expand...
Click to collapse
Sent from my Evo CM6
bizdady said:
Your not forced to install it. If your stock you can update and re root or you can find the update zip and flash through recovery.
Sent from my Evo CM6
Click to expand...
Click to collapse
I am such a newbie with Android, everything you just said is jibirish to me..
Here is what I am thinking, maybe it might help, lol
I am not forced to update, but don't I want to? Most updates fix things or improve things..
I am stock other then I rooted the phone 3 days ago.
What in the world is an update zip? and what is flashing through recovery?
I have no recovery programs installed on either the phone or the computer..
Im so lostl... LOL
So you haven't installed? If you do install your just going to have to root again I believe. How did you root the first time?
Sent from my Evo CM6
no, you are not even close to bricked, and yes, it can be fixed
wow guys cant you give a newb some help..... i'm here for you man. the froyo update was released two days after i rooted. i was pissed. but know, i am newb no longer, and i share my knowledge with you. ok, so baisically, you have two options:
option 1 is to unroot, do the update, and reroot the updated version. this is the long way that pretty much puts you back at square 1 and will delete all your data. i would not reccomend this.
option 2 is your first lesson in using root: FLASHING ROMS!!!hahahaha this will be fun..
so baisically, you need to make the phone think it is being manually updated using a built-in tool called recovery mode. the stock recovery mode (red !) has protection and signature verification that makes it so you can only update actuall htc stuff. the thing is, there is no protection stopping us from changing the recovery mode... now do you see where i am going? the little bit of recovery protection there was you removed by rooting. so first, download the rom of your choise from the dev section. most newer ones are 3.29.xxx.xx.xx. watever, so you are good. you can always just download the stock one from the dev section. make sure you back up everything with titanium backup. then, there are two ways to flash this rom:
easy: run unrevoked (www.unrevoked.com) to install a custom recvoery and remove factory system partition security (nand protection). then, boot into recovery by powering off phone and then holding power and volume down at the same time. finally, wipe data/cache/dalvic and then flash your rom.
hard: download the three attached files. install the android sdk and adb drivers. then, push flash_image to data/local/ and both amonra.img and mtd-eng.img to /sdcard/. then do..
adb shell
su
chmod 755 /data/local/flash_image
cd /data/local/
./flash_image misc /sdcard/mtd-eng.img
./flash_image recovery /sdcard/amonra.img
then, put rom of your choise on sdcard, and boot into recovery using either the way above or the command
adb reboot recovery
wipe all three things and flash rom.
if ANYTHING here is over your head. please pm me. don't just reply to my post because then i will not help you. i hope you do this successfully. seriously, ANYTHING, just beam me a pm.
dk
Hi all
My USB connector does not work, I would send him assistance, but unfortunately my device has the bootloader unlocked, with root and rom Mincov6.
I tried to use Mobile Odin, I downloaded directly from the phone the factory image of 4.2.2 and tried to open the file .tgz, however, tells me: "Partition could not be found in file."
What can I do? I'm desperate, I await your response
Thanks in advance.
Sorry for english, but i'm italian :crying:
http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128
bodh said:
http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128
Click to expand...
Click to collapse
My device is GSM, not Verizon
It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.
bodh said:
It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.
Click to expand...
Click to collapse
From what I understand, who used the Verizon tar in GSM, brock the device.
Now, I can not find anywhere the. Tar for GSM..
This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..
bodh said:
This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..
Click to expand...
Click to collapse
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?
Try this
ciccionicosia said:
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?
Click to expand...
Click to collapse
You should've replaced the stock recovery before locking the bootloader. You can try finding a flashable .zip of the stock recovery, but it'd probably have to be made. Has the device ever gotten an OTA update? I'm thinking you could use the following OTA script and patch to reflash the stock recovery in a very minimal sort of way.
First, you'll have to re-root by installing supersu.zip from sdcard download via custom recovery(which youll need to remove later).
Install Root Browser Lite by jrummy, and say no to installing the additional features (you may have to remove some binaries from your sdcard later after unrooting).
Unzip the attachment.
Place the install-recovery.sh in /system/etc/ with r-xr--r-- permissions and root root ownership and group ownership (via long pressing the file once it is in place, first permissions, then ownership).
Place the recovery-from-boot.p in /system/ with rw------- permissions and root root ownership and group ownership (same way as above).
Now power down.
Boot into recovery from fastboot (vol up+down+power, scroll with volume keys until the top says recovery, then press power).
Does it say android recovery on top, or is it still your custom?
If it's stock, let it sit until it boots on its own.
Remove the supersu.apk and su binary via root browser.
Remove rootbrowser and its binaries on the sd.
You should now be in business.
P.S. You could also look for an odin flashable .tar for your device, and flash it to return, but i think that'd be more complicated for you. Those files I provided are put in place during every ota update, and I believe this should work for you.
Hey there,
today my N7100 surprised me by anouncing that there is a firmware update available. Must be that 4.2(.2). [edit: no, unfortunately it's just a security update] In all my years with my i9000 I never OTA updated because I was always on custom ROMs and like lightyears ahead of the official update cycle, but now I'm uncertain.
Of cause I want to keep root / reroot at least for AFWall and especially the 240dpi is very important to me... will OTA override those settings, going along with those as well the Xposed settings? Any experiences yet?
And if, will rooting and Triangle away work like before on the new version as well? I am as the title says on the stock 4.12 with root and counter reset according to this manual: http://forum.xda-developers.com/showthread.php?t=1896696
On my SGS I'd just give it a shot, but the Note is just like a month old (so me still a bit nooby) and at the moment I don't need&want to mess around with it too much - Especially because all this counter stuff is bugging me ^^
Any advices? I know that's probably not really helpful, but probably someone has the same concerns too and just wants to share his thoughts too
Guess unrooting before OTA updating would be the safest way anyway.. wouldn't it be? ... Kinda have a lack of motivation here ^^
I think that is just a security update. There is still no word on 4.2.2 yet
Sent from my GT-N7100 using xda app-developers app
hendog4385 said:
I think that is just a security update. There is still no word on 4.2.2 yet
Click to expand...
Click to collapse
Good point, found this: http://www.sammobile.com/2013/06/18...ty-update-galaxy-note-ii-still-android-4-1-2/
Questions still persist though..
Adjusted the thread title and initial post to reduce confusion.
Yeah previous 4.1.2 rooting method will work latest too.
OR simply flash prerooted ROM, no need to reset counter/Root.
Read Prerooted ROM in my signature, i have just posted latest XXDMF2
dr.ketan said:
Yeah previous 4.1.2 rooting method will work latest too.
OR simply flash prerooted ROM, no need to reset counter/Root.
Read Prerooted ROM in my signature, i have just posted latest XXDMF2
Click to expand...
Click to collapse
Awesome! Thanks! (will give it a shot as soon as I have a bit mroe time and want to reboot into WIndows. A shame that there's no proper - as easy to use as ODIN - alternative for Ubuntu)
Is this usual, that flashing stock with some extra apks like the su stuff doesn't increase the counter? Or is it that just flashing PDA doesn't affect it? Am curious..
Samsung bootloader only check custom recovery /kernel for flash counter setting. So it can't detect these applications. On prerooted rom everything remains as it is except pushing su +super user +busybox.
Sent from my GT-N7100 using xda premium
XXDMF2 is probably the same as XXDME2 except they could only be bothered to work on/release that geographic variation last?
dr.ketan said:
Samsung bootloader only check custom recovery /kernel for flash counter setting. So it can't detect these applications. On prerooted rom everything remains as it is except pushing su +super user +busybox.
Click to expand...
Click to collapse
That's great thanks. So basically I could as well push some more apps with my installation by following your, how I find very clear and nice to follow, Tutorial in your Pre-Rooted-Thread and varying the step where the superuser.apk is being added from:
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
to
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
cp myFavoriteApp.apk temp/app/myFavoriteApp.apk
chmod 0644 temp/app/myFavoriteApp.apk
Right? So this way I could have a Stock ROM that comes with my usual App Setups by default when flashing and still leaves my Counter untouched..That's just wonderful, spares a lot of time after wiping..since in this case there is no wipe that's not needed here I know, but having a clean phone without having to install everything manually again would be nice anyway.
Wondering what weird things would happen if I tried to install apk's that are already installed.. will they be skipped..guess so, I mean, superSU is installed as well here already.. ?
Thanks for teaching me A pleasure to learn
When you push applications to rom that install to system rom of your device and that is limited space, so no good idea to push multiple applications.
Sent from my GT-N7100 using xda premium
dr.ketan said:
When you push applications to rom that install to system rom of your device and that is limited space, so no good idea to push multiple applications.
Click to expand...
Click to collapse
Ah I see, sounds reasonable... thanks for clearing that up!
Hey guys, im on the same state like the op.
i have stock rom, but rooted with odin and on TWRP recovery, busybox, superuser and triangleaway.
can i easily run this update without issues or should i completely go back to stock?
thanks, greetz, hope for a fast answer :|
Done! Without problems. but iam lose root, busybox and su
I updated yesterday, rooted stock 4.1.2 with xposed. Flashed new non-rooted (original) ROM from SAM mobile.
upon flashing, I had to
1) root agiain
2) install SU again from apk,
3) run SU and it updated binary
4) run Triangle away and reset counter
5) run Xposed framework and press "install", reboot
6) run busybox and let it auto-install
Then I was able to manualy change sounds for keypress/press and bootanimation.
All well.
D,
Just flashing stock prerooted ROM, you can skip first 4 steps
NOTE! This guide is extremely old and likely isnt up to date. I cannot maintain it any more. If anyone is willing to take it over and fix any issues, let me know!
TOOK THE OTA AND GOT STUCK IN RECOVERY LOOP? DERP, DONT TAKE OTAS, DUH. ANYWAYS, IF YOU CANT GET INTO DOWNLOAD MODE AFTER OTA, DO THIS
GUIDE:
Thanks to Bliss who worked the exploit into Loki, Dees_Troy built TWRP for us, djkinetic, Huskehn, and myself tested.
So good news folks! TWRP is now working on LG G2 thanks to an updated loki patch from bliss. Note that Loki patch is not necessarily an unlocked bootloader, but for the end user there is basically no difference. We can flash kernels (when they exist) roms (when they exist) recoveries etc etc. A full bootloader unlock could come someday, but this is all you will need until then.
First off, if you have issues with ADB not connecting, try THESE DRIVERS
The install is super simple, and you have two or 3 options.
Download the img for your device:
AT&T IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Verizon IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
TMobile IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Korean Telecom IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
d802 IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
For other models, click HERE and scroll down to find the files beginning with d2, and see if any of the folders sound like your model.
NOTE FOR THESE DOWNLOADS! READ ME! UPDATE! Ok, so if you look in the download page for your device and you are getting a zip file, this is a flashable zip, but it cannot be treated the same as an IMG file in this guide. You need to flash an older one that is a .img file, and then use that to flash the newer zip.
YOU MUST ALREADY BE ROOTED! follow This guide to do so if you arent. BE AWARE THAT THIS ROOTING METHOD ONLY WORKS BEFORE TAKING THE OTA. IF YOU ARE UPDATED AND UNABLE TO ROOT, FOR NOW THE ONLY WAY IS TO FLASH BACK TO STOCK AND ROOT BEFORE THE OTA, THEN TAKE THE OTA, THEN INSTALL TWRP
NOTE THAT ALL GUIDES BELOW ARE REFERENCING THE VZW img file. Be sure to replace it with whatever version you downloaded!
ABSOLUTELY DO NOT FLASH ANYTHING NOT MADE FOR YOU PHONE SPECIFICALLY!
OPTION 1 RECOMMENDED The way I tested it in #lg-g2 Possibly safer as loki runs some safety checks first. Download loki from github here Click download zip on the right. and go into the bin folder of the zip. push loki flash and the img like so:
Code:
adb push loki_flash /data/local/tmp/loki_flash
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
exit
adb reboot recovery
-------------------------------------------------------------------------------------
OPTION 2 via dd. Push just the recovery img like this:
Code:
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
dd if=/data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
--------------------------------------------
OPTION 3 easy, untested (as of time of writing) install it from goomanager on the phone! This aparantly does work bu you have to manually browse to the file or something... anyone who's tried care to clarify?
I tried and cant figure out where you find the recovery. I recommend Option 1 or 2
----------------------------------------------
Troubleshooting:
If you get "Failed to open aboot for reading." when following method 1, Be sure you have the # prompt, not $. If you rooted properly you should alutomatically have # in shell, but if not just type su to get it. then run the flashing command.
If you had confusion based on the pushing steps because the two img names listed in the command were different, my bad. the filenames changed while I was writing from test version to final, I missed replacing the first name in the commands. Look at the post again as it is fixed now.
If adb reboot doesnt work, make sure that "exit" command fully exited you out of the adb shell prompt. you should be at standard command prompt for that. type exit again if you arent, or heck just open a new command prompt
-------------------------------------------------------------------------
Be happy with what you have, so soon. Be sure to thank all the devs and donate to them![/SIZE][/U]
Got stuck trying to send the recovery to my ATT G2, replacing verizon files, renamed all the files including recovery file to RECOVERY and got it running. TWRP up and running. WOOOHOOO, let the roms begin lol
What? You mean no one cares whether or not I get this device only what @scrosler gets?
I kid, I kid.
Nice work on getting TWRP on the device. Now it is time for something truly awesome to happen, now that this first step has been taken.
Thread Cleaned
can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?
Walter21026 said:
can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?
Click to expand...
Click to collapse
I'd like to know this as well, please
This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?
If this works as the loki for the S4 did, then we will have access to flash everything. Kernel, modem, and ROM. There are no boundaries.
Sent from my LG-D800 using Tapatalk 4
JustusIV said:
This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?
Click to expand...
Click to collapse
Currently this is a work around. Bootloader is still locked up tight
Goo says no recovery found for this device.
Sent from my LG-D800 using XDA Premium 4 mobile app
Basically the bootloader no longer matters except for the purity of beating them at their own game. I am sure there are other benefits, but crackflashers will have our fix
Sent from my LG-D800 using Tapatalk 4
i tried thru goomanager i went in to the install open script and it says no recoveries are available
HUGH Thanks to everyone that made this possible! :victory: You guys are the reason I stick with android and never worry about buying the latest devices.
Patience paid off. :highfive:
Now Bring on the ROMS!!!!!:laugh:
Doesn't work for me. I get a "cannot stat 'g2vzw.img': No such file or directory"
Do I need to root before this
Nvm I'm dumb
Sent from my VS980 4G using XDA Premium 4 mobile app
Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....
Han Solo 1 said:
Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....
Click to expand...
Click to collapse
i was about to try, then saw this when reading through it. i don't get it.
So in theory an OTA will patch this just like the S4 so be careful with updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.
jayochs said:
i was about to try, then saw this when reading through it. i don't get it.
Click to expand...
Click to collapse
Hopefully the OP will chime in here soon.
JustusIV said:
So in theory an OTA will patch this just like the S4 so be careful updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.
Click to expand...
Click to collapse
Stop by the store or CS they will push it up for you no problem. They did for me just ask nicely
Sent from my LG-D800 using XDA Premium 4 mobile app
Han Solo 1 said:
Hopefully the OP will chime in here soon.
Click to expand...
Click to collapse
i'm also frekaing out because this is the first i heard about this chinese root method possibly having spyware..that's the method i used, and despite the fact i deleted their superuser app immediately, i'm wondering if i should go back to stock and do all that bs just to root again with the new method..
Would anyone know where to find the original stock rom and flashing method?
Why would you need it if there is no alternative right now? Stock is all you can have so do a factory reset if required.
Sent from my SGH-I337 using xda app-developers app
For example you need a stock rom to unroot your device. Factory reset doesn't work for unrooting. So the questions from @ekolb123 is very good. I agree to the question.
You can unroot from within the supersu app under settings.
Sent from my LG-V500 using Tapatalk 4
LG has posted the source for the G Pad: https://www.lg.com/global/support/opensource/opensourceList?types=NAME&search=LGV500
However until now there isn't any way to unlock/hack the bootloader, and so you cant flash it.
Most of us rooted with Kingoroot. Can't you just unroot with that and then factory reset in the stock recovery?
I'm currently working on a stock, rooted ROM but as I'm very new at this, I'm having quite a bit of difficulty.
Once I'm able to actually get it to build, then I can work on figuring out our new LOKI support and get CWM up and running.
what buttons do i press upon booting up to get to recovery to factory reset my device. i already unrooted. thanks.
edit: nevermind, figured it out. it's in system settings, and you can also press and hold Volulme Down + Power and then when you see LG let go of Power and press and hold it again.
mustbepbs said:
I'm currently working on a stock, rooted ROM but as I'm very new at this, I'm having quite a bit of difficulty.
Once I'm able to actually get it to build, then I can work on figuring out our new LOKI support and get CWM up and running.
Click to expand...
Click to collapse
Good news.
I tried to get CWM working and although it built i only achieved to brick my tablet.
The good news is that now i've found tutorials to unbrick it (in fact any recent LG smartphone or tablet).
To download the rom: http://forum.xda-developers.com/showthread.php?t=1073827
model is v500
Go to download mode by pressing volume+ and keeping it pressed connect your usb cable to your pc (the tablet must be off)
To flash the rom : http://forum.frandroid.com/topic/167696-tuto-flasher-une-rom-officielle-en-kdz/ (translated by google: http://translate.google.fr/translate?sl=fr&tl=en&js=n&prev=_t&hl=fr&ie=UTF-8&u=http%3A%2F%2Fforum.frandroid.com%2Ftopic%2F167696-tuto-flasher-une-rom-officielle-en-kdz%2F&act=url)
This method saved my tablet.
Also check this:
http://lg-phone-firmware.com/index.php?id_mod=39
obiwan86300 said:
Good news.
I tried to get CWM working and although it built i only achieved to brick my tablet.
The good news is that now i've found tutorials to unbrick it (in fact any recent LG smartphone or tablet).
To download the rom: http://forum.xda-developers.com/showthread.php?t=1073827
model is v500
Go to download mode by pressing volume+ and keeping it pressed connect your usb cable to your pc (the tablet must be off)
To flash the rom : http://forum.frandroid.com/topic/167696-tuto-flasher-une-rom-officielle-en-kdz/ (translated by google: http://translate.google.fr/translat...to-flasher-une-rom-officielle-en-kdz/&act=url)
This method saved my tablet.
Click to expand...
Click to collapse
Good to know. How did you flash the recovery? Did you work LOKI into it?
mustbepbs said:
Good to know. How did you flash the recovery? Did you work LOKI into it?
Click to expand...
Click to collapse
adb push loki_flash /data/local/tmp/loki_flash
adb push loki_patch /data/local/tmp/loki_patch
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
cd /data/local/tmp
chmod 755 loki_patch
chmod 755 loki_flash
./loki_patch recovery aboot.img recovery.img recovery.lok
./loki_flash recovery recovery.lok
I can't say for sure this method works as i still havent managed to compile a working CWM but at least it flashes without error.
obiwan86300 said:
adb push loki_flash /data/local/tmp/loki_flash
adb push loki_patch /data/local/tmp/loki_patch
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
cd /data/local/tmp
chmod 755 loki_patch
chmod 755 loki_flash
./loki_patch recovery aboot.img recovery.img recovery.lok
./loki_flash recovery recovery.lok
I can't say for sure this method works as i still havent managed to compile a working CWM but at least it flashes without error.
Click to expand...
Click to collapse
Excellent. So since that works without an error, once we get a working CWM we should be set.
mustbepbs said:
Excellent. So since that works without an error, once we get a working CWM we should be set.
Click to expand...
Click to collapse
Hello guys, wednesday I will have in my hands the G Pad..
I practiced a lot of modding on my N7000, but I've never created anything personal on my smartphone.
I wanted to know what is missing, until now, in order to start modding our G Pad.
LG has released the firmware or am I wrong? What is missing to create custom rom starting from the stock firmware?
thanks :victory:
Palux said:
Hello guys, wednesday I will have in my hands the G Pad..
I practiced a lot of modding on my N7000, but I've never created anything personal on my smartphone.
I wanted to know what is missing, until now, in order to start modding our G Pad.
LG has released the firmware or am I wrong? What is missing to create custom rom starting from the stock firmware?
thanks :victory:
Click to expand...
Click to collapse
We're missing recovery. We've got a bootloader workaround with LOKI and we've got the stock source. We just need a working recovery.
thank you for the reply,
so, for example, if coming out a version of CWM you could do it all, in total security (because now you can do the root but do not go back, right?) ?
Palux said:
thank you for the reply,
so, for example, if coming out a version of CWM you could do it all, in total security (because now you can do the root but do not go back, right?) ?
Click to expand...
Click to collapse
.. Not quite sure what you mean.
We've already got a way to restore stock even if we manage a soft brick.
mustbepbs said:
We've already got a way to restore stock even if we manage a soft brick.
Click to expand...
Click to collapse
ok, I'd missed this step.
so just missing a good recovery worthy of note. hopefully good
thanks