Related
Hi there everyone, i am in need of assistance.
I have follwed the guide on here for downgrading my phone usin the ADB commands and all is good up until the actual downgrading stage. After a few attempts i had managed a temp root (i think) using command line.
" adb shell " brought back the # so i know i did that right, but when it comes to pushing the rom file to my sd card it comes back adb not found in which case i cannot reboot the bootloader if that doesnt work.
Is there something i am doing wrong or is the file im uusing just not compatible, "PC10IMG.zip"
If there is another way to downgrade after temp root with maybe a different rom file i would be very grateful if someone could help me.
Any questions you have to help me, just let me know
Thanks
Sent from my HTC Vision using XDA App
Im still very new at this but i'll thrown in my two cents here.
After you've gotten temporary root status '#' and you've set your version to 1.00.000.0 following the guide, your next step is it push the stock ROM used to downgrade into your sd card.
At this point make SURE you are not in the adb shell, (aka you dont see the #)
so make sure you exit first.
Another thing is to make sure the ROM you want to push, the "...._PC10IMG.zip" file is in the correct directory, same directory as your CMD.
Lastly the push process takes time so dont be impatient, unlike the other files you pushed before which were more or less instant, this one will take at least a minute and the CMD may look idle so really just have to wait.
when the results show, you can then proceed with reboot bootloader command.
hope it helps.
i got stuck after this point, i keep getting a cid error, which is a totally differnt issue from your above question.
Cut to the chase, I can no longer get into recovery. I am trying to use adb in command prompt, but am running into a roadblock where $ comes up, and no commands will work. I quite literally have no idea what to do. I just want to go back to normal. I know it's my fault for trying new things, but if the phone still boots up, there must be a way out of this hell. Please can anyone have mercy on me and help? What information must I provide? VM670 is the phone. I think it's on stock ROM cause the UI is all virgin mobile looking.
Edit: I tried to restore some BCDS backup or something in Rom manager. Now my screen is just black, but I can hear it boot up. Is my phone toast?
mcnic05 said:
Cut to the chase, I can no longer get into recovery. I am trying to use adb in command prompt, but am running into a roadblock where $ comes up, and no commands will work. I quite literally have no idea what to do. I just want to go back to normal. I know it's my fault for trying new things, but if the phone still boots up, there must be a way out of this hell. Please can anyone have mercy on me and help? What information must I provide? VM670 is the phone. I think it's on stock ROM cause the UI is all virgin mobile looking.
Edit: I tried to restore some BCDS backup or something in Rom manager. Now my screen is just black, but I can hear it boot up. Is my phone toast?
Click to expand...
Click to collapse
I am not sure if I remember correctly, but when $ pops up, don't you have to type "su" (without the quotations) to allow superuser actions or something? What I mean is, before you type any other command, you must first type "su", press enter (when you do the $ should turn into a # or something), then proceed with the rest of the commands.
when I type su, it waits a second, then tells me permission denied I believe.
Can you post the set of instructions that you are following?
I was just able to get into recovery for some reason! It was the one I remember with orange text this time. (older version?) I wiped everything.... but had no ROM to flash. -_- trying something now.
After 2 days of trying to fix my phone, I give in, make an account and ask for help here. No more than 5 minutes later my phone is back to just how I want it for no reason at all. I am so utterly baffled right now. Thanks sweetnsour for being there . love this place
Simply get root (GingerBreak or Super One Click) , then install recovery with Rom Manager.
Sent from my LG-P500 using Tapatalk
mcnic05 said:
when I type su, it waits a second, then tells me permission denied I believe.
Click to expand...
Click to collapse
Are you root your phone? Use, depending your stockROM, z4root (2.2 and some 2.2.1), Gingerbread (2.2.1, 2.2.2) or SuperOneClick + Gingerbread exploit + some ADB commands (2.3.3)
When you rooted, you can flash customrecovery using commands or, in case of CWM, Clockworkmod apk.
mcnic05 said:
when I type su, it waits a second, then tells me permission denied I believe.
Click to expand...
Click to collapse
Because when you typed su , your phone will appear the super user permission , it only give you 9 seconds to allow the su...... But you just see the black screen
Need 10 posts to comment in developers forum. So I'll just thank everyone for their help! And say how much faster bobzhomes build is than others I've used. Love it.
I rooted using viperMOD PrimeTime v4.5 today without any problems. Then I installed Rootkeeper via the market, unlocked the bootloader, and installed CWM using viperMOD PrimeTime v4.5. Everything worked flawlessly.
So then I noticed an Asus firmware update was available. I wanted to install it and then give rootkeeper a try to make sure I kept root.
During the Asus firmware update, the android symbol on the screen fell over on his back and had I think an X on him.
Apparently, something went wrong with the firmware update. Everything froze, so I pushed the power button.
Now, when the device turns on, it goes straight into CWM.
Since everything went haywire before I backed up the ROM, I have nothing to restore.
Also, now my device is not recognized by Windows.
I downloaded the [ROM][S Series] Virtuous Prime Beta 1 .zip file with the intent to install this custom ROM, but since I cannot get my Prime recognized by Windows, I cannot move the .zip file over to my Prime to install the ROM.
If anyone could help me through what to do next to possibly reinstall the stock ROM, get my device recognized by Windows, etc. It would be appreciated. I am totally lost now.
How can you have done this when development section clearly says don't try to apply OTA updates after unlocking prime? Its a guaranteed brick just waiting to happen. That's why you have to always read thoroughly everything involved. Obvious you didn't because you tried to apply update. SMH
You should be able to flash stock back with this info:
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
It has worked for others who soft bricked prime. It should work n allow you to flash back stock rom.
Lesson to be learned here: Do not unlock device if you haven't researched it thoroughly. And never, ever ever ever try to apply an OTA update from Asus after unlocking device. It won't work and will brick your device almost 100% of the time. Once you unlocked device, say goodbye to OTA updates. They no longer will work. If you concerned with OTA updates then you have no business unlocking device. I hope you know you completely voided your warranty also by unlocking. Asus has proof as your serial number and device info was sent to Asus while you unlocked. Be glad xda is here and has solutions.
I have the same problem which i dont know how to fix
shinichikey said:
@demandaring: what exactly should I do? download the file, rename it, then put to removable sdcard, then boot using power+ volume down?
I don't think I cant do it because it's will lead into CWM...
Here are my case also: if you can help
I don't know what I did but after install the CWM successfully using PrimeTime 4.5, I couldn't get back into the system, but instead it keep boot back into Recovery mode after every single reboot. I have tried everything within my knowledge include: install the original zip file extracted from US_epaduser9_4_2_14UpdateLauncher.zip using recovery mod, and it stated successfully, but yeah still in a recovery loop; then I tried to install the Virtuous Prime Beta 1 through the CWM, it was also successfully but, guess what, still in the loop again, so I hope if anyone out there has this problem or know the solution, please help me, I am really appreciated... (I can get in to use adb in recovery mode also)...
Click to expand...
Click to collapse
" flashed today the file from this post (US Full OTA .14): http://forum.xda-developers.com/show...&postcount=387
Use this Method: EP201_SDUPDATE.ZIP (Rename extracted ZIP-File)
CONFIRM: Works ONLY with MicroSD CARD (REMOVABLE - ROOT).
Inernal Memory FAILURE - Search only for REMOVABLE RECOVERY
HOW TO:
-Shutdown Device
-HOLD LOWER VOL. + POWER
-CONFIRM within 5 Seconds with HIGHER VOL. "
when i hold the power+ lower volume, It went straight to CWM, what I am suppose to do in there?
Apparently, I screwed up. I saw the link that you mentioned.
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
I downloaded the zip file, but since my prime is not recognized by Windows, how I can I get this zip file over to my Prime to install this zip file?
I renamed the zip file as instructed to below.
I have my prime plugged in. I power off using CWM. Then I hold lower volume and power, it turns on. Then I hold volume up. It goes back into CWM. So I don't know what to do next.
I'm not sure how to proceed from here or exactly if there's some kind of method to "confirm" that I am unaware of.
Yes, I'm aware that I voided my warranty. I'm hoping that someone at XDA can walk me through fixing this.
Thanks for anyone who is willing to help.
@all
flashed today the file from this post (US Full OTA .14):
http://forum.xda-developers.com/show...&postcount=387
Use this Method:
EP201_SDUPDATE.ZIP (Rename extracted ZIP-File)
CONFIRM:
Works ONLY with MicroSD CARD (REMOVABLE - ROOT).
Inernal Memory FAILURE - Search only for REMOVABLE RECOVERY
HOW TO:
Shutdown Device
HOLD LOWER VOL. + POWER
CONFIRM within 5 Seconds with HIGHER VOL.
Works perfect...think with this method you can flash every FULL OTA - FW from EVERY SKU (without ROOT ???)
shinichikey said:
when i hold the power+ lower volume, It went straight to CWM, what I am suppose to do in there?
Click to expand...
Click to collapse
Try pointing it to the location where you put the stock rom file at. Then flash it. I added some stuff in your thread if you can't get it to work.
you supposed to put the zip file into the removable microsd card, so you just need to use an adapter or somehow put the file into the microsd card, but yeah, i tried it, but it did nothing...
---------- Post added at 01:06 AM ---------- Previous post was at 01:03 AM ----------
I did try to locate and install the zip file using CWM, it stated successfully but after reboot, it went straight into CWM again
I stuck a microsd card in the slot, but my Prime is not recognized by Windows. So I can't copy and paste the zip file onto the microsd card to install the zip. Any ideas how to apply this fix given my situation. Thanks again to anyone who is willing to help.
Both of you post your issue in this thread http://forum.xda-developers.com/showthread.php?t=1510983
They can help you in there. We had someone earlier who had same problem and was walked through what to do.. you can also pm Doltaplex(misspelled) or Diamondback. They can help.
use an adapter so you can connect your microsd card without the tablet, or you can use adb to push the file into the memory card, that's how i did, but even if you can get the file into the tablet, you cant still fix the problem, that's my case...
richteratmosphere said:
I stuck a microsd card in the slot, but my Prime is not recognized by Windows. So I can't copy and paste the zip file onto the microsd card to install the zip. Any ideas how to apply this fix given my situation. Thanks again to anyone who is willing to help.
Click to expand...
Click to collapse
He means use your computer to put the file on root of microsd card. Then put card inside of prime. Then do those previous steps. Prime doesn't need to be hooked up to PC for this. Microsd card need to go inside prime with the stock rom file on root of it.
---------- Post added at 01:19 AM ---------- Previous post was at 01:11 AM ----------
I posted in that new thread I linked you to. They should know you on the way. State your issues in thatthread. Someone there will get your primes back running again.
I think I found this solution that doktaphex posted in this thread:
http://forum.xda-developers.com/showthread.php?t=1511839&page=5
"kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius"
Unfortunately, I don't know how to implement this. If someone could help, it would be appreciated.
I have less than 10 posts, so I can't post in the ClockworkMod Recovery 5.5.0.4 for TFP developer thread.
richteratmosphere said:
I have less than 10 posts, so I can't post in the ClockworkMod Recovery 5.5.0.4 for TFP developer thread.
Click to expand...
Click to collapse
Guy in other similar thread in this section fixed his prime n got out of CWM loop. Check that other thread. I told him you probably need his help.
My Transformer crashes also during the .14 update and I have not unlocked the bootloader, there are some other users on swedroid also having these problem. Does anyone have a clue about what could be wrong?
Sent from my Transformer Prime TF201 using Tapatalk
Uppenberg said:
My Transformer crashes also during the .14 update and I have not unlocked the bootloader, there are some other users on swedroid also having these problem. Does anyone have a clue about what could be wrong?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
There's a new update coming that should fix your issue. There's a thread on it in general section. People are testing out a beta fix now. Everything goes well n they will release it asap.
richteratmosphere said:
I think I found this solution that doktaphex posted in this thread:
http://forum.xda-developers.com/showthread.php?t=1511839&page=5
"kmdm: it'll clear the headers for the blob update from the staging partition
kmdm: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
kmdm: remove the boot-recovery command
kmdm: right so, I'd reboot now
doktaphex: You sir are a f#cking genius"
Unfortunately, I don't know how to implement this. If someone could help, it would be appreciated.
Click to expand...
Click to collapse
I ran into the same problem - here is what I did (on Linux mind you) to use this info to fix.
1. Download and extract the Android SDK from Google. You will need the file "adb" which is located in the platform-tools folder when you extract the sdk
2. Boot into CWM Recovery
3. Connect your prime to your PC via the USB cord that came with it (make sure no other android devices are plugged in)
4. Open Terminal on your PC and go to the platform-tools folder that you extracted with the SDK.
5. Enter the command
Code:
sudo ./adb start-server
- you'll get a message telling you its connected or whatever
6. Next, enter the command
Code:
adb devices
- you should see the prime listed as "recovery" or somethign along those lines
7. Enter the command
Code:
adb shell
- this will put you into command line for your prime
8. Now you can start entering in the commands from the post.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
then press enter.
9. Next,
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
then press enter again.
10. Now you can unplug the prime and reboot your prime through "Reboot Now" in CWM
See if that helps. It worked for me.
If you have no idea what unlocking the bootloader and rooting your tablet does, you probably shouldn't do it. I mean, that's why HTC gives a big legal warning because there are too many people that just click on **** and wonder why things break.
If you still want OTA update, you can do that with just root. If you unlock the bootloader, there is no more OTA for you. You have to learn to flash custom roms and what caches to clean. There is a plethora of information on XDA on how to do this stuff.
Not trying to sound like an ass, but before I ever rooted / unlocked my phone, I talked to a friend who knew what they were doing and did a lot of reading up on it.
teknomar7 said:
If you have no idea what unlocking the bootloader and rooting your tablet does, you probably shouldn't do it. I mean, that's why HTC gives a big legal warning because there are too many people that just click on **** and wonder why things break.
If you still want OTA update, you can do that with just root. If you unlock the bootloader, there is no more OTA for you. You have to learn to flash custom roms and what caches to clean. There is a plethora of information on XDA on how to do this stuff.
Not trying to sound like an ass, but before I ever rooted / unlocked my phone, I talked to a friend who knew what they were doing and did a lot of reading up on it.
Click to expand...
Click to collapse
I agree. I will say, however, that I never attempted to do OTA after unlocking my bootloader so I'm not sure what happened. Freaked me out a bit, but glad the solution was the same for me as for those who attempted OTA after unlocking.
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.