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.
Related
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.
After installing a KK beta build rom I noticed my cell service was disabled so I checked the settings/status and everything showed up
as unknown including imei. Here's the full process I went through until finally fixing/restoring service on my phone.
NOTE: all of this was possible because I still had two very important files called modemst1.img and modemst2.img
these are what hold the important info about the phone including imei and such. Luckily @autoprime has a script in ioroot that'll backup
these files if you're on JB but if you're on KK you have to MANUALLY back them up. With that being said if you don't have these files
then this guide isn't for you.
So the first thing I tried (after restoring my nandroid backup which I found out didnt backup those modemst files) was take the two modemst files from my ioroot folder on my computer and putting them on the internal storage of the phone in a folder called EFS_Backup. I renamed the two files to efs1.img and efs2.img (if you don't have the option to show the files extension in the name enabled then you would just type in efs1 and efs2 or else the filename would end up efs1.img.img etc.) After that I put the phone into recovery (twrp) and plugged the usb cable. Then I ran cmd as administrator and typed these commands:
adb shell
su
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
It said that it copied them however I checked the folder with root browser and it still showed the empty modemst files (my backup ones were 3mb). So I tried the commands while the phone was booted up I granted root access and it said it copied again but still nothing. Around this time I got into a bootloop and was getting stuck so I flashed a KK baseband which helped me at first. At this point @dr87 gave me a flashable efs zip file to use which I'm going to attach to this post. To use it you have to drag your two modemst backups into it name then efs1 and efs2 then flash the zip in recovery.
Like the other steps though that didnt seem to replace the modemst files and I was stuck without service. I then got a bootloop again and tried flashing my nandroid backup with the KK baseband but this time it wouldn't work so I went back to the KK beta build so I could boot up again. I tried running the dd commands again this time with the efs files on the root directory on the internal storage of the phone. The command I used for that was this:
dd if=/sdcard/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
I got the same results as before. However another member said something about running the dd commands in stock recovery so I decided to do a zvc tot and try running the dd commands in the stock recovery. I downloaded the zvc tot from here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
I extracted the tot from the zip file and put it on my desktop and then I followed the sprint version of this guide:
http://forum.xda-developers.com/showthread.php?t=2432476
Scroll down to the part where it says RETURN TO STOCK TOT Method! AT&T & Sprint Verzion & The Few International TOTs I have available
Follow those instructions there however after step number 10 where you set your G2's port to COM 41 turn off and unplug your phone then after 13 where you click the yellow arrow in LG Flash Tool put your G2 back into download mode and the Flash Tool will then connect to your device and start the process. Once that was finished I went through the setup and was about to reboot to get to stock recovery when I noticed something.......MY CELL SERVICE WAS BACK!!!! Apparently with the custom roms replacing the modemst files didn't stick but after moving to stock zvc it seemed to replace it and I'm now back up and running. If you have any questions let me know and I'll get back to you as soon as I can. Wish you all the best.
P.S. I would like to give a very big thanks to @GizmoKaca he really helped me alot through this whole process.
OfficialPerson said:
After installing a KK beta build rom I noticed my cell service was disabled so I checked the settings/status and everything showed up
as unknown including imei. Here's the full process I went through until finally fixing/restoring service on my phone.
NOTE: all of this was possible because I still had two very important files called modemst1.img and modemst2.img
these are what hold the important info about the phone including imei and such. Luckily @autoprime has a script in ioroot that'll backup
these files if you're on JB but if you're on KK you have to MANUALLY back them up. With that being said if you don't have these files
then this guide isn't for you.
So the first thing I tried (after restoring my nandroid backup which I found out didnt backup those modemst files) was take the two modemst files from my ioroot folder on my computer and putting them on the internal storage of the phone in a folder called EFS_Backup. I renamed the two files to efs1.img and efs2.img (if you don't have the option to show the files extension in the name enabled then you would just type in efs1 and efs2 or else the filename would end up efs1.img.img etc.) After that I put the phone into recovery (twrp) and plugged the usb cable. Then I ran cmd as administrator and typed these commands:
adb shell
su
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
It said that it copied them however I checked the folder with root browser and it still showed the empty modemst files (my backup ones were 3mb). So I tried the commands while the phone was booted up I granted root access and it said it copied again but still nothing. Around this time I got into a bootloop and was getting stuck so I flashed a KK baseband which helped me at first. At this point @dr87 gave me a flashable efs zip file to use which I'm going to attach to this post. To use it you have to drag your two modemst backups into it name then efs1 and efs2 then flash the zip in recovery.
Like the other steps though that didnt seem to replace the modemst files and I was stuck without service. I then got a bootloop again and tried flashing my nandroid backup with the KK baseband but this time it wouldn't work so I went back to the KK beta build so I could boot up again. I tried running the dd commands again this time with the efs files on the root directory on the internal storage of the phone. The command I used for that was this:
dd if=/sdcard/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
I got the same results as before. However another member said something about running the dd commands in stock recovery so I decided to do a zvc tot and try running the dd commands in the stock recovery. I downloaded the zvc tot from here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
I extracted the tot from the zip file and put it on my desktop and then I followed the sprint version of this guide:
http://forum.xda-developers.com/showthread.php?t=2432476
Scroll down to the part where it says RETURN TO STOCK TOT Method! AT&T & Sprint Verzion & The Few International TOTs I have available
Follow those instructions there however after step number 10 where you set your G2's port to COM 41 turn off and unplug your phone then after 13 where you click the yellow arrow in LG Flash Tool put your G2 back into download mode and the Flash Tool will then connect to your device and start the process. Once that was finished I went through the setup and was about to reboot to get to stock recovery when I noticed something.......MY CELL SERVICE WAS BACK!!!! Apparently with the custom roms replacing the modemst files didn't stick but after moving to stock zvc it seemed to replace it and I'm now back up and running. If you have any questions let me know and I'll get back to you as soon as I can. Wish you all the best.
P.S. I would like to give a very big thanks to @GizmoKaca he really helped me alot through this whole process.
Click to expand...
Click to collapse
I have exactly the same issue and can't do anything. Phone boots up fine but no cell or data. I don't have those 2 files...is it something I can download? I really need help. I'm so frustrated, especially because it's my FRIEND's phone. Help me, please!
See this: http://forum.xda-developers.com/spr...nal-please-t2814919/post54122384#post54122384
THANK YOU!!!!
im sorry, but those files are unique to each phone, each one is different. It is not something you can download. Best thing to try is tot back to 100% stock, then hope he has insurance on the phone and take it to a repair center, once they determine it cant be fixed, they will order a replacement (or give you one), if he doesnt have insurance, hope its under warranty and do a RMA to LG
LoveistheGroove said:
I have exactly the same issue and can't do anything. Phone boots up fine but no cell or data. I don't have those 2 files...is it something I can download? I really need help. I'm so frustrated, especially because it's my FRIEND's phone. Help me, please!
See this: http://forum.xda-developers.com/spr...nal-please-t2814919/post54122384#post54122384
THANK YOU!!!!
Click to expand...
Click to collapse
I'm sorry to hear about your predicament. When you rooted your phone did you use ioroot? What version were you on when you rooted i.e. Jelly Bean, Kit Kat, etc.?
OfficialPerson said:
I'm sorry to hear about your predicament. When you rooted your phone did you use ioroot? What version were you on when you rooted i.e. Jelly Bean, Kit Kat, etc.?
Click to expand...
Click to collapse
I was on KK. Used AutoRec for TWRP.
LoveistheGroove said:
I was on KK. Used AutoRec for TWRP.
Click to expand...
Click to collapse
Autorec and twrp are different then ioroot which is rooting. But since you were on KK then I'm pretty
sure when you rooted it didn't automatically backup your EFS files. When you go into settings to where
it say PRL, IMEI, MEID, etc. does it say unknown for all of them? Or do some of they have numbers and
stuff?
OfficialPerson said:
Autorec and twrp are different then ioroot which is rooting. But since you were on KK then I'm pretty
sure when you rooted it didn't automatically backup your EFS files. When you go into settings to where
it say PRL, IMEI, MEID, etc. does it say unknown for all of them? Or do some of they have numbers and
stuff?
Click to expand...
Click to collapse
I used iroot and all of those are blank or unknown
Is it really that easy to permanently ruin a phone? Wow.
I'm sure it is, I just can't believe it's impossible to fix.
LoveistheGroove said:
I used iroot and all of those are blank or unknown
Is it really that easy to permanently ruin a phone? Wow.
I'm sure it is, I just can't believe it's impossible to fix.
Click to expand...
Click to collapse
Hmm ok and yeah things can go down south very easily which is why they put
warnings all the time but people (including myself) usually take them lightly lol.
However it may not be permanently ruined I read a post a couple days ago about
someone taking the optimus g and writing the prl imei and other info himself with
certain programs. He mentioned ways to get those numbers for your specific phone
I'm not exactly sure if it'll work but it may be your only option at this point. I'm going
to see if I can find the post again and put the link here. This is a pretty advanced
process though I've never done it myself so don't really know that much about it.
If anything though are you insured?
OfficialPerson said:
Hmm ok and yeah things can go down south very easily which is why they put
warnings all the time but people (including myself) usually take them lightly lol.
However it may not be permanently ruined I read a post a couple days ago about
someone taking the optimus g and writing the prl imei and other info himself with
certain programs. He mentioned ways to get those numbers for your specific phone
I'm not exactly sure if it'll work but it may be your only option at this point. I'm going
to see if I can find the post again and put the link here. This is a pretty advanced
process though I've never done it myself so don't really know that much about it.
If anything though are you insured?
Click to expand...
Click to collapse
Thank you and please do if you can. I know the codes to program them. I just don't have them.
I have insurance. Last effort though.
Please share if you can!
Billy
LoveistheGroove said:
Thank you and please do if you can. I know the codes to program them. I just don't have them.
I have insurance. Last effort though.
Please share if you can!
Billy
Click to expand...
Click to collapse
Here's the post the section I was referring to is repairing EFS.
http://forum.xda-developers.com/showthread.php?t=2161498
OfficialPerson said:
After installing a KK beta build rom I noticed my cell service was disabled so I checked the settings/status and everything showed up
as unknown including imei. Here's the full process I went through until finally fixing/restoring service on my phone.
NOTE: all of this was possible because I still had two very important files called modemst1.img and modemst2.img
these are what hold the important info about the phone including imei and such. Luckily @autoprime has a script in ioroot that'll backup
these files if you're on JB but if you're on KK you have to MANUALLY back them up. With that being said if you don't have these files
then this guide isn't for you.
So the first thing I tried (after restoring my nandroid backup which I found out didnt backup those modemst files) was take the two modemst files from my ioroot folder on my computer and putting them on the internal storage of the phone in a folder called EFS_Backup. I renamed the two files to efs1.img and efs2.img (if you don't have the option to show the files extension in the name enabled then you would just type in efs1 and efs2 or else the filename would end up efs1.img.img etc.) After that I put the phone into recovery (twrp) and plugged the usb cable. Then I ran cmd as administrator and typed these commands:
adb shell
su
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
It said that it copied them however I checked the folder with root browser and it still showed the empty modemst files (my backup ones were 3mb). So I tried the commands while the phone was booted up I granted root access and it said it copied again but still nothing. Around this time I got into a bootloop and was getting stuck so I flashed a KK baseband which helped me at first. At this point @dr87 gave me a flashable efs zip file to use which I'm going to attach to this post. To use it you have to drag your two modemst backups into it name then efs1 and efs2 then flash the zip in recovery.
Like the other steps though that didnt seem to replace the modemst files and I was stuck without service. I then got a bootloop again and tried flashing my nandroid backup with the KK baseband but this time it wouldn't work so I went back to the KK beta build so I could boot up again. I tried running the dd commands again this time with the efs files on the root directory on the internal storage of the phone. The command I used for that was this:
dd if=/sdcard/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
I got the same results as before. However another member said something about running the dd commands in stock recovery so I decided to do a zvc tot and try running the dd commands in the stock recovery. I downloaded the zvc tot from here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
I extracted the tot from the zip file and put it on my desktop and then I followed the sprint version of this guide:
http://forum.xda-developers.com/showthread.php?t=2432476
Scroll down to the part where it says RETURN TO STOCK TOT Method! AT&T & Sprint Verzion & The Few International TOTs I have available
Follow those instructions there however after step number 10 where you set your G2's port to COM 41 turn off and unplug your phone then after 13 where you click the yellow arrow in LG Flash Tool put your G2 back into download mode and the Flash Tool will then connect to your device and start the process. Once that was finished I went through the setup and was about to reboot to get to stock recovery when I noticed something.......MY CELL SERVICE WAS BACK!!!! Apparently with the custom roms replacing the modemst files didn't stick but after moving to stock zvc it seemed to replace it and I'm now back up and running. If you have any questions let me know and I'll get back to you as soon as I can. Wish you all the best.
P.S. I would like to give a very big thanks to @GizmoKaca he really helped me alot through this whole process.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________
I think I have great news. I looked in my ioroot folder and found both of the files (3 MB each) that are modemst1.img and modemst2.img.
I created a folder on the Internal called EFS_Backup, and I copied and pasted those two files into the new folder, renaming them efs1 and efs2. They renamed and stuck in the folder just fine, but running the ADB commands didn't work. So I used the flashable EFS zip in TWRP and it said FAILED.
I'm thinking since I have these 2 files I should be able to fix this, right???? But...the thing that's driving me nuts is that LG Flash Tool, no matter what version, will NOT work on my device anymore. Not with either of my PC's.
Does anyone have a suggestion for what to do now that I found those modem files in my ioroot folder?
I feel like this is the closest I have gotten and now I'm stuck. LG Flash Tools never worked on Windows 8. The OLDER versions worked fine with .tot files BEFORE all of this happened, in Windows 7. Now even Windows 7 won't work to use LG Flash Tools, after I created this mess.
Can anyone PLEASE help me take these 2 files and get them to fix my EFS? I really don't know what I'm doing, clearly, or I would have backed up my EFS first. Problem here is probably same everywhere...I've always done this, never bothered with Nandroid or EFS backups, but also never had the issue of only having an internal memory on an Android device. Stupid mistake.
I would greatly appreciate any help that can be offered. I have one more day and I can still take this phone back...IF I can fix it. Thank you in advance!
PS: I Have my ESN, MEID HEX, MEID DEC, IMEI, ICCID AND IMSI - ALL POPULATED WITH NUMBERS IN SETTINGS. WHAT IS "UNKNOWN" IS MY PHONE NUMBER AND MY PRL.
Did my best to avoid having to ask for help, but looks like I've run out of ideas. I've got a 7840 that currently refuses to boot past the recovery screen, thanks (probably) to my own incompetence. Here's what happened along the way to this point:
First, probably important to note: my tablet is a Chinese-released 7840 running 5.0.2 Lollipop. The hardware is identical from what I can tell, but the software was definitely a bit tweaked as there were no Google services installed. (And sideloading any of the Google services always failed no matter how I went about it.) This is basically why I decided to start messing around with things.
Attempted to load the developer firmware. Wound up in the dreaded "Intel Inside" bootloop, but thanks to @xBIGREDDx and his unbrick.zip (http://forum.xda-developers.com/showpost.php?p=60663442&postcount=2) I was able to return to normal booting. No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
I then decided to use the tethered CWM method to root the device for the purposes of giving sideloading the Play Store another try. That worked just fine and I was able to root my 7840 without a hitch. I then created a nandroid backup (which suspiciously didn't generate an MD5 file) in case I managed to really screw things up trying to sideload the Google Services.
That's when I thought wiping and recovering the 4.4.4 Kit Kat nandroid backup might be a good idea. This of course didn't work, so I wiped and restored my own 5.0.2 backup. However, at this point things wouldn't boot no matter what I did. I would see the boot screen with the Dell logo and the Lollipop-style ANDROID text, but after a couple of minutes everything would reboot and after a couple of tries the device would boot to recovery and just sit.
After fiddling around with trying different restore methods, I decided to see if I could flash the developer firmware to no avail. (Unable to write to OSIP, security error, etc.) Then I gave @anggusss's 5.0.1 OTA update.zip a try. (http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21) That gave me a different error:
"Can't install this package (Fri Apr 24 13:29:34 CST 2015) over newer build (Fri Apr 24 13:58:18 CST 2015)."
Frustrating to see that a build a half hour newer might be all I need. So, if any of you happen to have captured the 5.0.2 OTA build (or can help me tweak the 5.0.1 build to report itself as newer), would you mind giving me a hand? Would be most appreciative. I've written to Dell open-source support but don't expect to hear back for another week or so. It'd be nice to not be using the Venue as a paperweight for a week.
wirebook said:
No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
Click to expand...
Click to collapse
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
anggusss said:
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Click to expand...
Click to collapse
I've never gotten vol. up + power to do anything, is that normal? Only vol. down + power, and that'll get me into fastboot mode.
xBIGREDDx said:
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
Click to expand...
Click to collapse
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
wirebook said:
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
Click to expand...
Click to collapse
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
xBIGREDDx said:
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
Click to expand...
Click to collapse
Thanks a lot for those! Flashed both boot and system, though the system gave me some sort of error on my machine ("Invalid sparse file format at header magi") and then continued to flash something ("sending sparse 'system'"). I saw the red text of some sort of error on the tablet but wasn't able to read it fast enough. The system flash did seem a bit suspiciously fast, though...
Anyway, now waiting to see if anything boots. Been sitting on the Dell/Powered By Android screen for a couple of minutes, though, so if nothing else it looks like I've at least found myself in a new place. Will try reflashing if no improvement and then get back with results!
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
xBIGREDDx said:
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
Click to expand...
Click to collapse
wirebook said:
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Click to expand...
Click to collapse
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
social-design-concepts said:
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
Click to expand...
Click to collapse
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
wirebook said:
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
Click to expand...
Click to collapse
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
EDIT: For anyone else coming along, don't do this, it didn't work out well for wirebrook. /EDIT
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
That must be what's happening. I'll fiddle with things a bit more later on. It's a bummer there aren't any custom ROMs I could simply flash as an alternative to getting stock up and running...
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
social-design-concepts said:
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
Click to expand...
Click to collapse
Not sure this'll be useful for me any more because... (see below)
xBIGREDDx said:
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
Click to expand...
Click to collapse
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
vampirefo said:
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Thanks for the thought, but if I can't get into Fastboot mode (or get the computer to recognize the device as being in Fastboot mode)... kinda unable to use it.
wirebook said:
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
Click to expand...
Click to collapse
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
xBIGREDDx said:
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
Click to expand...
Click to collapse
Fingers shall stay crossed till the end of the month, then! Contacted Dell Support and- just as I predicted- they don't want to help out. Something about being unable to do anything at all for Dell products purchased outside of their support areas (US and Canada). What a joy of a phone call that was...
An internet search landed me on guides for unbricking the Asus Zenfone displaying a similar USB symbol. They used the xFSTK Downloader to flash a set of files which then gave them renewed access to the bootloader (and thus fastboot). Played around with the xFSTK-Downloader and Manufacturing Flash Tool apps and can see the 7840 and even flash the (open-source and unbrick.zip) firmware, however I'm at a loss for what I might use for the Operating System flash files. Anybody have any thoughts?
Feel like I'm so close to getting this thing unbricked. If I could just figure out where to find the .bin "OS Image" that the tool wants...
Edit: Would also need the droidboot binary. FIngers crossed for Dell to release all of this soon...
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.
My phone is stuck in a TWRP bootloop, meaning it doesn't boot to Android but it goes back to TWRP (It actually happened with the phone being in my pocket). I've tried restoring different backups, but none of them have any effect booting back to normal. I'm travelling at the moment so I don't have access to my computer to attempt restoring using SP Flash Tools. Any one have any ideas?
David C.
mantarkus said:
My phone is stuck in a TWRP bootloop, meaning it doesn't boot to Android but it goes back to TWRP (It actually happened with the phone being in my pocket). I've tried restoring different backups, but none of them have any effect booting back to normal. I'm travelling at the moment so I don't have access to my computer to attempt restoring using SP Flash Tools. Any one have any ideas?
David C.
Click to expand...
Click to collapse
Possibly it was from an ota update. And twrp is failing to do ota. But the command to install ota is not cleared, so it keeps trying.
If that is the case , then the solution from other mtk based devices I have had , is to clear the /misc partiton
Can be done from terminal in twrp.
I added the option to wipe /misc partition in the ported twrp I am working on. but have not tested that out.
In your case because you cannot boot to system, you cannot download it and try. So need to use first option and clear /misc with dd commands in the terminal window.
Do you want or need instruction on doing that?
If that is the problem this line of code entered into the twrp terminal window should fix it
Code:
dd if=/dev/zero of=/dev/block/platform/bootdevice/by-name/para count=1 bs=32
mrmazak said:
Possibly it was from an ota update. And twrp is failing to do ota. But the command to install ota is not cleared, so it keeps trying.
If that is the case , then the solution from other mtk based devices I have had , is to clear the /misc partiton......
Click to expand...
Click to collapse
Dude you are a life saver, I used the command line, rebooted and BAM!! back to normal. I checked the Update section and it did have one update pending, I deleted it just in case. Like I said I'm traveling for work and this left me incommunicado. Thanks again, let me know if I can buy you a drink or a cup of coffee ?
mantarkus said:
Dude you are a life saver, I used the command line, rebooted and BAM!! back to normal. I checked the Update section and it did have one update pending, I deleted it just in case. Like I said I'm traveling for work and this left me incommunicado. Thanks again, let me know if I can buy you a drink or a cup of coffee
Click to expand...
Click to collapse
Yes, best to remove the update app, or block it at least. because it will keep trying to do its update.
@mantarkus
I made a simple twrp flash install package that disables the ota apk by renaming it. This will prevent that type of problem in future. Of course You will not be able to automaticly chec for OTA, but as you found out, that would cause bootloop anyway.
look at thread here for file
https://forum.xda-developers.com/showpost.php?p=79644458&postcount=3
mrmazak said:
@mantarkus
I made a simple twrp flash install package that disables the ota apk by renaming it. This will prevent that type of problem in future. Of course You will not be able to automaticly chec for OTA, but as you found out, that would cause bootloop anyway.
look at thread here for file
https://forum.xda-developers.com/showpost.php?p=79644458&postcount=3
Click to expand...
Click to collapse
Awesome, thanks!!
I suppose the process to update safely is flashing the new ROM via SP flash tools and root as before, right?
David C.
David C.
can you explain exactly step by step on what should be done i have same issue Thank you so much
Thanks!
Just wanted to say thanks for identifying this and posting the fix