Related
so i have the i777 and i rooted using a guide on the android central forum
basically i downloaded kies, odin, cwm, and superoneclick
i put the cwm.tar file through odin, and than ran superoneclick, and i was rooted pretty easily
i than downloaded rom manager and through there i flashed CWM. I tried to make a back up using rom manager but that failed, no biggie i hear other people have the same problem. I boot up into CWM using rom manager and it says stuff like "failed to verify whole file signature"
im not sure if this means i rooted incorrectly?
i made a back up just fine using CWM. However i found out this stuff about flash increments and how i flashed a custom CWM kernal or something (sorry my definitions in this subject are still noob)
i decided i want to get rid of the yellow triangle + i9100 message every boot, no biggie but i am here to learn and i figure might as well if i can. I read a couple threads here and im not sure if this is my answer but i think it is please advise
my plan is to go back completely as if i never rooted and than root by using a stock rom/kernal so i dont get the error triangle message as well as the incorrect international i9100 display
i think this is my solution
"2b.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from the command line using Heimdall (Linux and Mac OS)
* Tested on Linux, should work on Mac OS
* Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
* Download Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from here. Extract the PDA.tar file from this package to a directory on your hard disk drive, then extract the two component files from the tar - zImage and factoryfs.img.
* Place zImage and factoryfs.img both in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
* Reboot the phone. Success. You're Rooted.
"
i am under the impression that if i flash the .tar file that is 200+mb (why so big) that i will be RE ROOTED and COMPLETELY stock, therefore no error message and no international thing popping up
also, no more flash counter increments ? << this one is also important as this is one major reason i want to re root
im not really sure but i think that by flashing this new .tar it will over ride my custom.tar file that i do not want any more, i dont know how to get rid of it so this is the only thing i can think of
im worried because i dont know if i have to UNROOT before i install entropys thing or if it will just over ride
thanks so much to any one who can give me advice
Really the best instructions are in creepncrawly's write up on how to return to stock. It covers any question you could have:
http://forum.xda-developers.com/showthread.php?t=1313659
And for doing it right:
http://forum.xda-developers.com/showthread.php?t=1311081
Plus new tools:
http://forum.xda-developers.com/showthread.php?t=1367319
The write ups he does are top notch and should be mandatory reading for first time visitors.
The file is so big because it contains the entire android os.
The issues you're having in cwm sound like clockworkmod needs to be reflashed.
The triangle will be removed simply by the stock kernel being replaced. The flash counter as of now can only be reset by a usb jig ~ less than $10.
Though a few have reported returning the phone for warranty issues and they did not check the flash counter.
The only way the flash counter is tripped is by using pc Odin to flash a non stock kernel.
Sent from my páhhōniē
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
There's a stock plus root package. One of the best ways to root in my opinion.
Root means installing SuperUser.apk, su, and busybox. That's it. The stock + root package has those already included, but also gives you the bone stock kernel.
You install a custom kernel to, among other things, get ClockworkMod Recovery.
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
in reality, 'rooting' your phone is nothing more than placing 2 files on the /system (only one is really needed, since you can download Superuser from the market)
what happens is this:
android version release (say 2.3.5)
extremely smart people find way to exploit a memory hole in the OS, and create a 'rooting' method. what this method does is exploit that hole, which allows for a 'temp root' while it injects the needed files for root
needed files for root:
/system/bin/su <- this is the binary that allows you to retain root access
/system/app/Superuser.apk
without root access, /system is a read-only partition. utilizing the exploit, it will create temp root, then remount the /system partition as read/write, allowing your rooting tool to inject the required files into /system
rooting actually has nothing to do with the device at a true hardware level. it is all within the OS itself. anything outside the OS (recovery, boot, bootloaders, etc) dont get 'rooted' because root is only access to the /system within the OS
samsungs have this awesome ability to be easily rooted via CWM. its extremely easy with ODIN or heimdall to flash recovery/new kernel with recovery built in, and use a cwm zip file to inject the needed files into /system rather than relying on an exploit to do it for you.
its a common misconception that i hate to see when people associate rooting with access to anything outside the OS itself.
'i am having problems flashing this rom/kernel/mod in cwm'
'are you sure you are rooted? try re-rooting'
asinine logic...to say the least
^^
That needs to be stickied in every android forum on xda.
Sent from my páhhōniē
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
DroidBehavior said:
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
Click to expand...
Click to collapse
Sounds like you still have reading to do. And kudos to you for taking what they said as constructive criticism.
The flash counter can only be reset by a usb jig. Mobile Tech videos make some very good quality ones.
The delay from the home button is due to the vlingo app shortcut being tied to the home button (double tap home button) so it's waiting to see if you hit it twice before it takes you to the home screen. Cusom roms remove the vlingo app from being there which helps cut down on the delay.
But you may notice it more since what you did. And you should. By adding cwm you likely flashed Entropy512's kernel. Which is an awesome kernel. One of the ways that kernel helps battery life is by setting the cpu govener to conservative. It slows the cpu from jumping too high too quick. That explains why you may have not noticed the delay before you did anything. As well as the delay from unlocking the phone.
For me the extra battery life is worth it. If you don't like the delay one of the easier ways to set it back to ondemand (stock) is to use the app SetCpu:
https://market.android.com/details?id=com.mhuang.overclocking&hl=en
Hope that explains everything.
Sent from my páhhōniē
yeah that makes perfect sense thanks for the explanation
right now i installed miui and i ****ing love it! the interface is so smooth and sexy its like iphone spliced with android
minimalistic ftw
the interface was so much smoother i ran quadrant but the score was the same heh, but still its impressively smooth
i unlocked bootloader with teh asus unlock tool. I then rooted using the debugfsroot method found in the stickies. everything went well Or so i thought. After all rebooting was done i went into app folder and the superuser app was in there so i thought that i was rooted. Went to install twrp through goo manager and it said it couldn't get root permissions adn that i wasn't rooted. So i downloaded titanium backup to backup my apps and when i opened it it too said i wasn't rooted or that busybox wasn't downloaded. I downloaded busy box from the market and tried to install it and same thing....any one know what's up?
try rooting again with the same method and post what the cmd says after you are done with it~
lil-devil said:
try rooting again with the same method and post what the cmd says after you are done with it~
Click to expand...
Click to collapse
ok doing that now
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
vballrkc said:
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
Click to expand...
Click to collapse
UPDATE: After the second root now everything i described above is requesting superuser permissions so it appears all is well. If i have problems i will repost. Thank you for your response though i guess it just didn't stick the first time.
i'm glad that it works now
Hello,
i have a litle problem with the method above everything went ok .. i have root acces i think :'(
but the problem is that almost all applications started to crash, force close ro stoped running at all.
everything that was working before the root is broken somehow
any way to fix this ,???
i would suggest you to try unrooting with the root keeper app
if that doesn't work try reseting your tab via the pin hole under the SD card
if that still doesn't solve the problem default the tf201~
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
bk201doesntexist said:
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
Click to expand...
Click to collapse
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
vballrkc said:
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
Click to expand...
Click to collapse
I actually had good intentions, but now I don't freaking care what you think: Don't use sarcasm on me boy. BTW, no sarcasm here: You'll never learn anything if you keep using toolkits.
I have a Nabi 2 tablet that I've rooted, installed TWRP, and flash the gapps and a few other tweaks to. It's about to go in for an RMA since the USB and charging ports are both broken. The problem in the USB port is that one of the pins got bent - I don't know how, it looks like the conductor somehow got peeled back off of the plastic. The point is, I have no USB access to the device.
In order to pass the inspection for the RMA, I need to have it stock I can flash the stock ROM by putting it on the SDCard in my laptop then transferring that to the device and flashing it through TWRP. The question I have, though, is whether I can flash the stock recovery with ADB access to it. Every thread I've been able to uncover so far about flashing a recovery requires ADB access to issue the "adb fastboot flash" command. Is there another way to do this?
If the ROM your going to return it with (stock) has the flash image binary then you can use a terminal emulator but I doubt this will work as most often stock ROMs don't. But maybe worth a shot
Otherwise depending on how the tablet and recovery are set up possibly flash the stock recovery through twrp
Would need to know a lot more about your tablet to say for sure how to do it
Sent from my Nexus 4 using Tapatalk 2
Yes. Sometimes I have seen recovery-from-boot.p and install-recovery.sh restore it on first boot after you have restored stock ROM.
If not...
Copy a stock recovery.img to your external SDcard
After restoring your Nabi ROM.
Use TWRP "mount" tab and make sure external_sdcard is checked
Use TWRP "Terminal Command"
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
I forget when TWRP add terminal command, if you have an older version you'll have to update it first.(same idea as flashing stock, just get the 2.6.0.0 TWRP image and put on external SD) There are some other methods but I think this is easiest without a functioning USB
aicjofs, thanks!
It could just be my current sleep-deprived state, but this line confused me:
aicjofs said:
Yes. Sometimes I have seen recovery-from-boot.p and install-recovery.sh restore it on first boot after you have restored stock ROM.
Click to expand...
Click to collapse
The way my brain interpreted it says that once the stock ROM is restored, it will automatically restore the recovery on first boot.
I have some part of my brain screaming "NO!" though, so I'm not sure what you were trying to say there. Care to enlighten me?
oh, and I've got TWRP 2.2.2.1, and it does have a terminal emulator, but it's clunky at best.
Dan in SA said:
aicjofs, thanks!
It could just be my current sleep-deprived state, but this line confused me:
The way my brain interpreted it says that once the stock ROM is restored, it will automatically restore the recovery on first boot.
I have some part of my brain screaming "NO!" though, so I'm not sure what you were trying to say there. Care to enlighten me?
Click to expand...
Click to collapse
Yes some have claimed it returned them to stock recovery. That file is only like 300kb though so it can't be the full image as the kernel alone is 4MB+. Maybe it's just the ramdisk, but its too large for that. I can't imagine it works but that's what people have claimed, probably shouldn't have said I have seen because I haven't personally seen it, just heard. I would do the method I talked about and dd the image from TWRP.
All can be recovered without USB port as long as you can boot either Android or TWRP just don't lose both at same time
Ok, thanks I'll try and get it charged tonight, and flash the stock ROM tomorrow and see what happens.
One more quick question - I don't have a recovery.img file. I have recovery.emmc.win and mmcblk0p1.img - they're both 8,192kb. I'm assuming I would either rename the first to recovery.img, or use the second and dd it into /dev/block/platform/sdhci-tegra.3/mmcblk0p1
Am I on the right track?
Dan in SA said:
Ok, thanks I'll try and get it charged tonight, and flash the stock ROM tomorrow and see what happens.
One more quick question - I don't have a recovery.img file. I have recovery.emmc.win and mmcblk0p1.img - they're both 8,192kb. I'm assuming I would either rename the first to recovery.img, or use the second and dd it into /dev/block/platform/sdhci-tegra.3/mmcblk0p1
Am I on the right track?
Click to expand...
Click to collapse
Yes on the first but No on second. The way you have it won't work but you are close. for dd the "if" = input file, and the "of" = output file. Both are your input file. recovery.emmc.win = mmcblk0p1.img and an image of recovery partition basically a different name for the same thing.(the same as boot.emmc.win = mmcblk0p2.img an image of boot partition) In this case the input is either of those 2 files, and the output is the recovery partition.
So you could use any of the following it's just changing the name of the input
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS (if you renamed one of the two files to recovery.img)
dd if=/external_sdcard/recovery.emmc.win of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
dd if=/external_sdcard/mmcblk0p1.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Just use the above...but to confuse you more you could be using mmcblk naming convention in the output file as you stated. Tegra renames the mmcblk block format, think of it as a symlink so you can call a single location 2 different names.
so /dev/block/platform/sdhci-tegra.3/by-name/SOS is the same as /dev/block/mmcblk0p1 and is the recovery partition itself
another example /dev/block/platform/sdhci-tegra.3/by-name/LNX is the same as /dev/block/mmcblk0p2 and is the boot partition
knowing that you could take the first example from above
dd if=/external_sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
and write it as
dd if=/external_sdcard/recovery.img of=/dev/block/mmcblk0p1
and accomplish the same thing, so you were close just no "/platform/sdhci-tegra.3" Hopefully I didn't come across as offensive as I imagine you already know some of the above
I knew that (DUH! :cyclops: ) I told ya I was sleep deprived.
I'm going to flash it this afternoon and see what falls out.
Thanks bunches!
Ok, first step finally done.
Got the JmzNabi2Stock_OLD.zip loaded. Got the dreaded "turning wifi on" error, but skipped that step to move on. Currently waiting for "Please wait while your nabi device is being initialized. This might take a few minutes."
It has been at least 5 minutes, but to be honest this is going faster than the FC17 to FC19 upgrade I have going on on the system next to it. It's had a blank screen with the disk spinning since I started this about 30 minutes ago.
WooHoo! as I was typing that last para, the setup screen showed up. I'll go through som rudimentary things just to check and make sure this image isn't rooted, then I'll try to reload the stock recovery.
edit: crap, this wasn't the "stock" image. Now I need to head off and try to find that......
Whelp, that didn't work. One of the ROM flashes broke the recovery and lost root. Without ADB, I can't do anything more
Dan in SA said:
Whelp, that didn't work. One of the ROM flashes broke the recovery and lost root. Without ADB, I can't do anything more
Click to expand...
Click to collapse
If the recovery doesn't boot I doubt they will even look deeper then that and think you messed it up.
If you still want to attempt it you have to use an exploit to gain root again(Android still boots right?) Unfortunately most exploits are using ADB as a means to that end. ADB restore bug, elevating ADB shell to root via local.prop edit, for example. I would think the Android master key exploit would work on this device but the only good tool I have seen for it is Cydia Impactor. GUI that's compiled so its not easy to short cut and do locally without following the write up and manually doing everything(In short no one click that will work without USB). I think memdroid or something like that only worked up until 4.0.2 or something so I think Nabi is patched against it. It can be done I just don't know if you want to go to the effort. Should have used the Nabilab full stock ROM and stock recovery to restore as they are matched set.
aicjofs said:
Should have used the Nabilab full stock ROM and stock recovery to restore as they are matched set.
Click to expand...
Click to collapse
I did, but when I booted that up after I loaded the ROM, SuperSU was installed implying that the image was rooted already.
Too late now, it's in the box going back to Nabi tomorrow.
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Ophidian_DarkCore said:
if your savvy with the shell, aroma fm has a built in terminal.
flash this in recovery http://forum.xda-developers.com/showthread.php?t=1646108
then cd to the directory.
rm settings.db
mv settings_old.db settings.db
Click to expand...
Click to collapse
Thanks you for you reply. I have one question though, I have no idea if my bootloader or my kernal or any of that is 'unlocked' I only rooted my phone. If I try to flash aroma fm and they are locked or something would that actually really brick my phone?
ALSO: I don't have an SDCARD... I don't think it's possible to flash anything then? Because flashing from the Internal Storage might brick the device. right?
ALSO: I don't think the LG Optimus F60 has ARM Neon support... & the "Recovery mode" doesn't have any flashing support. It's all STOCK.
LG Optimus F60 Specifications
Any Ideas?
Ophidian_DarkCore said:
well damn, if you have a custom recovery usb-otg you can make a flashable zip that runs some shell commands.
flashing wont brick a device. putting unsigned boot/recovery imgs usually bricks locked devices.
as with all lg devices, there is download mode to load stock firmware/updates. [LOL apparently I can't post outside links yet even, if their a quote...]
Click to expand...
Click to collapse
That's RIGHT! But, sorry for the noob question: What is a custom recovery usb-otg and how do I make a flashable zip that runs some commands? (For example: maybe one that just runs the commands but doesn't actually change the recovery software or the boot just one that can rename the files?)
Also, I don't think it would work but, would flashing the recovery to stock not delete any data, and have the phone be able to boot?
If it's too much to explain that's okay just show me some related posts that can show me how.
Thanks again for your time.
Ophidian_DarkCore said:
maybe try this http://forum.xda-developers.com/showpost.php?p=59637778&postcount=62
EDIT: Disregard below
you need a custom recovery before anything. and apparently your device supports fastboot.... so give this a go http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
and later you might get android L
Click to expand...
Click to collapse
I'm not sure, because the phone already has the factory boot and I haven't flashed anything into the Boot Partition. It's probably an error that happens when it tries to validate the settings.db or the permissions it has [chmod or that its mounted read write]. [To my understanding] what TWRP boot loop fix does is install fastboot then the custom recovery and the stock boot again. Which should do about the same thing because the phone is already stock. Right?
Would installing a custom recovery then allow me to access adb or the filesystem? (If so any recommendations?) Or how would I run a script from download mode?
Thanks for your time.
Ophidian_DarkCore said:
you only need to flash the recovery. not the boot img.
installing a custom recovery will either give you adb, or an on device shell.
Click to expand...
Click to collapse
That's right, Thank you. I'm going to try flashing one right now. Do you know of any that give you access to adb? (and maybe have low risk of bricking LG phones?)
Ophidian_DarkCore said:
the one in that thread should work.
fyi, recoveries, roms, and kernels are specialised software usually only compatible with one model. so no mixxy matchy
i guess using those instructions you could try the img from here http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
Click to expand...
Click to collapse
How would I install the img? I would need to install fastboot, right? Then run fastboot ****.img?
Is fatboot run from adb or from SendCommand.exe?
Thanks again for all your help.
Ophidian_DarkCore said:
yea, just grab a fastboot binary, the lg driver, go into whatever mode in that thread and
Code:
fastboot flash *.img
edit: fastboot is it's own binary. so it's run in a command shell on your pc like adb is.
Click to expand...
Click to collapse
One last question (Need to make sure...): I have fastboot.exe from the SDK tools, so all I need to do is:
1. Connect the USB
2. Boot into Download Mode
3. Run fastboot flash *.img
4. When finished unplug the USB and take the battery out.
5. Then boot back into Download mode or Recovery Mode to get TWRP?
6. Then try to see if I can get ADB to work?
Also, sorry for all the questions: But If I ever needed to, will a factory reset delete TWRP or will I need to flash it again with the Stock recovery?
Thanks for your time. You are awesome.
Hi, thank you for using XDA Assist. Unfortunately there is no device specific forum for your device. I'm going to ask a moderator to move your thread here, http://forum.xda-developers.com/android/help
Solved it.
I used an exploit to access the filesystem and fix the corrupt db.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
I did the same thing, you installed the wrong model FW. just install the base rom and start over.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it.
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen seems also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
how do i restore my us metropcs lg f60 phone back to stock?
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
Help Help
Help anyone, i have LG f60 (390n) running with 5.0.1 lollipop. I wanted to instal custom recovery and install custom rom CM. But i have two problems:
1. If i want to boot to download mode - i have error "SECURE BOOT ERROR" (but it boots up normally, and work normally)
2.If i want to boot to recovery mode - i have error "LOADING KETSTORE FAILED STATUS 5"
Please help.
I am not able to flash it trough LG Flash tool, and i am not able to boot into custom recovery.
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.