Related
Hi All,
I have Dell streak with EVT1 hardware. I flash all possible recovery images, but it isn't work. Black screen every time when I launch recovery mode. May be somebody know how to update this hardware?
Phone is working on 1.6 (performance is very poor)
P.S. Sorry for bad English.
Please help!!!
What is the currently installed rom exactly?
NikolayTLM said:
Hi All,
I have Dell streak with EVT1 hardware. I flash all possible recovery images, but it isn't work. Black screen every time when I launch recovery mode. May be somebody know how to update this hardware?
Phone is working on 1.6 (performance is very poor)
P.S. Sorry for bad English.
Click to expand...
Click to collapse
If you have a black screen at recovery with no Dell logo, you probably are going to need to restore your device using the QDLTool3rd.
Typically, this happens when flashing an "update" file mismatched with your recovery. I did this myself recently, and the only way I was able to get back was to use the QDL tool then re-flash my stock ROM.
It literally saved my phone.
EVT=evaluation/testing?
Without knowing the differences in hardware and possibly software you can't assume that solutions that work on production Streaks will work on his phone.
marvin02 said:
EVT=evaluation/testing?
Without knowing the differences in hardware and possibly software you can't assume that solutions that work on production Streaks will work on his phone.
Click to expand...
Click to collapse
EVT=evaluation/testing - Yes
i think that difference between EVT3 (product hardware) and EVT1 - smallest RAM size (145Mb is available)
in on board EVT1:
- QSD8X50 Processor (as per "Android System Info") with 998.4Mhz max frequency.
- Total RAM: 145Mb
I tried flash device via QDLTool3rd - unsuccessful. Maybe i used newest recovery images instead old? Black screen every time when i try to boot it in recovery mode. What additional info about EVT1 is needed and which application can provide this information?
BR. Nikolay.
TheManii said:
What is the currently installed rom exactly?
Click to expand...
Click to collapse
Sorry, but i don't know the currently installed rom.
Info in 'About device' menu:
- Firmware version: 1.6
- Baseband version: GAUSB1A1008151
- Kernel version: 2.6.29-perf
- OEM version: RerforceVerify_1012
- Build number: 1012
You definitely have an enginnering beta streak, from what've seen from attempting to get people to dump their roms off it, trying to update it will prob brick it.
It's only valuable if you can get the rom off it, but otherwise you likely wont be able to use it as a normal streak
TheManii said:
You definitely have an enginnering beta streak, from what've seen from attempting to get people to dump their roms off it, trying to update it will prob brick it.
It's only valuable if you can get the rom off it, but otherwise you likely wont be able to use it as a normal streak
Click to expand...
Click to collapse
Thanks, i think about that. I am use it as normal cell phone right now. But it is not easy, because it will reboot at any time as they wish. I like this phone and it isn't trouble to update RAM (on this device to appropriate size). I just want to know - device is 'upgradeable' to 2.2 or not?
I'l talking with people, which know about this device. And they said me - that this device can be ungraded, but build should be compiled in appropriate kitchen! Maybe somebody have appropriate build rom for this HW type/ or maybe somebody upgrade EVT1 HW?
how much did that specific streak cost you exactly?
You're much better off getting a normal retail streak unless you dont mind the hassle of making everything work on that submodel.
Clearly stock kernels and roms have trouble with that submodel, are you willing to investigate why? and are you willing to be forced to resort to making custom versions of roms just for your specific streak?
I am interested in getting the rom off that, but besides that unless you got it for free/next to nothing it's prob not worth the hassle compared to a retail streak, there's far too few owners of working prototype streaks left for premade roms to work on them
TheManii said:
how much did that specific streak cost you exactly?
You're much better off getting a normal retail streak unless you dont mind the hassle of making everything work on that submodel.
Clearly stock kernels and roms have trouble with that submodel, are you willing to investigate why? and are you willing to be forced to resort to making custom versions of roms just for your specific streak?
I am interested in getting the rom off that, but besides that unless you got it for free/next to nothing it's prob not worth the hassle compared to a retail streak, there's far too few owners of working prototype streaks left for premade roms to work on them
Click to expand...
Click to collapse
Yes, I got them for free. But this is a not major point for me. I would like to understand 'How it works'.... And I request help on this forum. I'm from Russia, Dell Streak mini 5 isn't selling in my country, So I would like to do 'candy' from it (not for sale, for me only). I thinking about purchasing Dell streak mini 5 with broken LCD, to change mainboard between my and broken device. But I'm not sure about compatibility this hardware (and I not have money to buy it........)
P.S. Sorry for bad English again.
I would assume the lcds would be compatable, but this is just an educated guess,
It sounds like a good idea to switch the motherboards if you want a real working streak
as you're not going to be using the original motherboard, could i ask you to make a dump of the system and boot partitions?
we should continue on #dellstreak on irc.freenode if you dont mind, prototype roms and devices are extremely rare and working ones with pre-release roms are even rarer. There's only a handful still in existance now
TheManii said:
I would assume the lcds would be compatable, but this is just an educated guess,
It sounds like a good idea to switch the motherboards if you want a real working streak
as you're not going to be using the original motherboard, could i ask you to make a dump of the system and boot partitions?
we should continue on #dellstreak on irc.freenode if you dont mind, prototype roms and devices are extremely rare and working ones with pre-release roms are even rarer. There's only a handful still in existance now
Click to expand...
Click to collapse
Please write instructions / 'how to' make a dump of the system and boot partitions
Do you know how to use ADB?
you will need to root your phone also before beginning
TheManii said:
Do you know how to use ADB?
you will need to root your phone also before beginning
Click to expand...
Click to collapse
My dell is rooted. I used ADB shell in my practice but a long time ago. So it would be perfect if you provide ADB commands...
Do you still have the original recovery installed?
first do a
Code:
cat /proc/mtd
and figure out which is boot / recovery / system
then do a
Code:
dd if=/dev/mtd/mtdx of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtdy of=/sdcard/boot.img bs=4096
where X and Y are the matching values from the first command
finally do a
Code:
cat /system /sdcard/system
then you'll have boot.img recovery.img (if you still have it) and a folder named system
send those 3 to me
TheManii said:
Do you still have the original recovery installed?
first do a
Code:
cat /proc/mtd
and figure out which is boot / recovery / system
then do a
Code:
dd if=/dev/mtd/mtdx of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtdy of=/sdcard/boot.img bs=4096
where X and Y are the matching values from the first command
finally do a
Code:
cat /system /sdcard/system
then you'll have boot.img recovery.img (if you still have it) and a folder named system
send those 3 to me
Click to expand...
Click to collapse
I used these commands in dell terminal app:
Code:
su
cat /proc/mtd
dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/recovery_bak.img bs=4096
dd if=/dev/mtd/mtd0 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/system.img bs=4096
After that operations 4 files added to sdcard (recovery.img, recovery_bak.img, boot.img, system.img)
Incorrect length message was displayed after cat /system /sdcard/system command.
All files were added to archive (WinRAR used) and uploaded to fileserver
You have to use
cat /system /sdcard/system
as DD will not work on the system partition
TheManii said:
You have to use
cat /system /sdcard/system
as DD will not work on the system partition
Click to expand...
Click to collapse
following text message is displayed when i try cat /system /sdcard/system command.
Code:
/system: invalid length
/sdcard/system: invalid length
my *nix is really weak,
try
Code:
cp -r /system/* /sdcard/temp
but you might need to manually make /sdcard/temp first or it might get confused
it will complain about symlinks but that's ok
Has anyone tried the method below to Re-Root and Re-Lock from Carrett's Thread:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How can I re-lock and un-root my phone? Remember the backups of the locked bootloader that you kept? You're going to need them. Obviously, you'll need USB Debugging enabled and LG USB drivers installed. Copy them to your phone's "Internal Storage" in a folder, in this example it's called "backups." Connect the phone to your computer via USB, open a command line (cmd) and type the following:
Code:
cd C:/some/folder/where/you/have/adb.exe/eg/your/freegee/download
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/backups/aboot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/recovery-att-backup of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd basically copies from the if= location and writes to the of= location. The first three dd steps write a bunch of zeros to the recovery, boot, and aboot partitons, the last three write the backups to aboot, recovery, and boot. If you want to know more, read all about dd here and/or Google. If you lost your backups, you can try writing mine.
Now you've restored the stock bootloader and recovery, but your phone is still rooted. To unroot it, open SuperSU, go to its settings, and tap "Full unroot." Do a factory reset (Settings->General->Backup & reset->Factory data reset) and you should be good to return the phone to AT&T (or whatever).
I did but I ended up having to LGNPST back to stock because I messed up somewhere along the way. You'll know if you messed up because when you try to boot you'll get the LG splash screen + Security Error.
If you choose to go this route, make sure you pay careful attention!
Murasakiii said:
I did but I ended up having to LGNPST back to stock because I messed up somewhere along the way. You'll know if you messed up because when you try to boot you'll get the LG splash screen + Security Error.
If you choose to go this route, make sure you pay careful attention!
Click to expand...
Click to collapse
Thanks for the response. So does it work and you simply messed up or is the code botched? It looks a lot simpler than LGNPST and I want a process that was a little simpler to do and quicker? Have not tried to LGNPST and was hoping not to but if I had to I wanted something I can't mess up.
Might want to check with SnowLeopard, I think there was a mention somewhere about making a zipped stock firmware that is unrooted and unlocked that can be installed.
Sent from my LG-E970 using xda app-developers app
jimi_pooh said:
Thanks for the response. So does it work and you simply messed up or is the code botched? It looks a lot simpler than LGNPST and I want a process that was a little simpler to do and quicker? Have not tried to LGNPST and was hoping not to but if I had to I wanted something I can't mess up.
Click to expand...
Click to collapse
There's a chance I messed up in the adb client, but there's no telling at this point. It was a few weeks ago. LGNPST really isn't hard, though some people think it is. Takes like one good run through to understand it, and there's several people in the LGOG IRC that can guide you through it.
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.
Hello
I'm creating a ClockworkMod recovery for my phone (K-Touch W68) and before I go any further, I wanted to check how dangerous this is?
How likely am I to brick the phone?
And, if I flash the wrong thing, how easy is it to recover?
I extracted the recovery using this (following a similar thread)
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
I've built a new recovery.img using builder.clockworkmod.com and was going to apply it using the following and then restart
Code:
cat recovery.img > /dev/block/platform/sdhci.1/by-name/recovery
Sound ok?
If you don't have a way to reload the stock OS either from the manufacturer or with a tool like MTK Droid (I'm assuming it has a MediaTek chip as most of those kinds of phones have them), then it will be risky. Sometimes it just doesn't do anything. Sometimes it messes up the recovery partition, but you can still boot. And sometimes it'll bootloop you. Not much way to tell without testing.
es0tericcha0s said:
If you don't have a way to reload the stock OS either from the manufacturer or with a tool like MTK Droid (I'm assuming it has a MediaTek chip as most of those kinds of phones have them), then it will be risky. Sometimes it just doesn't do anything. Sometimes it messes up the recovery partition, but you can still boot. And sometimes it'll bootloop you. Not much way to tell without testing.
Click to expand...
Click to collapse
Thanks for the reply.
The CPU is actually a Broadcom BCM21663 which seems pretty rare (other similar phones: Symphony W68, Karbonn A8). There are K-Touch W68 ROMs on needrom.com and some Broadcom flashing tools for the Karbonn A8 (can't post links yet).
Good deal. Sounds like it might be worth a try then. Good luck!
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.