Related
I was just preparing for leaving on holiday so I said I should unlock my phone. Rooted my phone, installed galaxy s2 unlock tool- didn;t get a code
then tried galaxy s unlock app from helroz and after step 2, restart and my phone had a no signal sign, tried to put it on plane mode and it is stuck now like that.
Opened galaxy sII repair tool but it doesn't work... What do I do wrong? Should I wipe the phone, install the galaxy sII repair tool? I have two folders now with efs files...one is from unlock app and one from the repair one. Please tell me what to do. I am desperate
You could jsut reflash original samsung rom, and use the app(I think chainfire made it) that will unlock you'r sg2 for free, or charge I don't remember.
thanks! So any original uk samsung rom and after that install that app?
I am so stupid for trying my luck with this...even in description helroz said clear that it's risky
Save quickly your efs!!!!!!! Is your phone this!!!without this is ipod!!!!no phone or imei code!!!!!!
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
Oooh my..actually I used that app in the first place...and it didn't work...then second option was this, and like chainfire said...more risky :/ oh my...
valentinrascu said:
Save quickly your efs!!!!!!! Is your phone this!!!without this is ipod!!!!no phone or imei code!!!!!!
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
Click to expand...
Click to collapse
where? I saved it several times with those 2 apps...I don't know what are they...the first app told me to save the efs as a backup in the unlock sgs2 folder. Second app as well... God knows what effs I have there...the original or the one with problems...take my words with a grain of salt, I really don't know nothing about this...please..should I copy those files somewhere in my computer?
screenshots here with what efs files on my phone.. so what do I do now?
ok it looks like I have a clean backup of the efs folder. I took a look and I find the 17 june date at some files
So I am missing the .nv_data.bak, .nv_data.bak.md5 and nv_data.bin.md5 but it looks like I have them in the backup that the app did it. So far only these files are missing... Should I make a full restore or only those files? And should I do it with root explorer copy paste?
Allright friends...that was hell of a scare. I deleted everything from efs folder after downloading a root explorer. Obviously I couldn't delete the folder itself nor rename it, so I had to paste the good files carefully.
All set now back in business, lesson learned, now I have the folder in my computer.
I wonder where did I do wrong, and why none of the method of unlock didn't work...neither chainfire or helroz.
the problem was you messed with 2 different tools.
All you need is the helroz unlock app, be running ics, follow the instructions, backup ya efs, and unlock.
IF YOU change ya mind and need to restore it, do it through the unlock app, NOT through the repair tool he made, yes, it does a similar thing, but if youd used the unlock app to restore efs you wouldnt or shouldnt have had any issues, your the first person i know to come unstuck with it.
be VERY CAREFUL with chains unlock app, it quite often wont work or gives ya the wrong code, which then ends up freezing ya phone, prob best to avoid that all together and take it to an unlock shop.
graemeg said:
the problem was you messed with 2 different tools.
All you need is the helroz unlock app, be running ics, follow the instructions, backup ya efs, and unlock.
IF YOU change ya mind and need to restore it, do it through the unlock app, NOT through the repair tool he made, yes, it does a similar thing, but if youd used the unlock app to restore efs you wouldnt or shouldnt have had any issues, your the first person i know to come unstuck with it.
be VERY CAREFUL with chains unlock app, it quite often wont work or gives ya the wrong code, which then ends up freezing ya phone, prob best to avoid that all together and take it to an unlock shop.
Click to expand...
Click to collapse
Yes, you are right, but I didn't thought about it, The first backup made was from the unlock tool. The second one obviously was made by the repair tool, only the problem was that it just backed up the damaged efs folder. I kept trying to restore but that was not the place for repair. Thanks to helroz that he made the backup in 2 different folders, so the bad efs didn't overwrite the good one.
Strange, I thought that chain's method was the safest, already tried it, it took a lot of minutes and prompted that couldn't find any code, I guess I won't try it again.
Should I try helroz app again? I am thinking to do so
And...one more thing, last night when it came back to life I only tested the data part of the sim. In the morning I tried to give a test call and didn't work although I had network signal.
I also tried to contact myself and it was like I had it shut off.
Everything came back to normal after shutting down and turning on again. Do you think it something I should worry,could it be because root/efs folder?
Oh no, Now I lost root acces, after installing busybox 1.17.1 ...what should I do?
anyone... superuser app cant be updated...version legacy, update fail...I know for sure this superbox messed it...
ok, so what you need to do is a new start.
Starting with odin, do no wipe anything from recovery, just go straight to odin and flash your usual ics rom, when you get the green pass, pull the usb lead and pull the battery.
put ya battery back in and boot to recovery, standard one, do a factory reset.
After that boot ya phone up, all should be good, set it up how you want, do the usual to gain root access.
After this use once you have root access, download the appropriate CF-ROOT kernel that matches your rom, and download mobile odin from the market, unzip ya kernel and flash ya kernel through that, if ya must use odin pc, then use triangle away afterwards.
Once youve done this, any EFS backup from the previous attempts on your usb storage or sd card, DELETE the entire folders and contents.
Once youre all set, recovery, cwm and everything, get the unlock app from the market, and follow the steps exactly as is said in the instruction, and unlock your phone and backup EFS.
Now go back to your sd card, backup the efs folder it created to a safe place on your pc and keep it safe.
You should now be unlocked and sorted. after using this app DO NOT USE SGS REPAIR TOOL, it does create a different backup for different purposes, if you feel the need to restore the efs folder and relock your phone, then you must do it from the unlock app.
im confident if you do it all right, you will be ok.
Now I understand what happened: I ran the unlock app, but the developer suggests superbox 1.17, I saw that I already had a superbox version installed but ..huh newbie...went ahead and that was the point where I lost root, I couldn't even passs step 1 with backup efs.
Thanks again....but I was on fire and again acted DIY spirit. I did so many times wipe caceh, factory data and saw that it didn't work.
So I just downloaded a stock rom (btw it's not my network rom, only the firmware matched not the baseband or csc).
-went to recovery, wiped cache, wiped data
- odin flash stock rom
- then odin root siyah
- then, and here is the clever part: screw that 1.17 recommendation and just installed galaxy s unlock without superbox, backed up efs; step 2, restart, step 3 (though I don't know if it was necessary)
And IT's UNLOCKED
Now please tell me if I did something wrong. I should copy that efs created backup in my computer right? and that's it....so much work for what it supposed to be 1 minute job...I guess I'm learning the hard way.
OK, here's what I will do when I come back, I'm late lol because of this,
Flash my H3G LP3 XWLP7 STOCK ROM.
now I don't know the right order, could u please help me here
Root and backup first or backup first and then root?
after these CF-ROOT Kernel - what is this actually? and why? shouldn't this syiah kernel be ok enough?
use triangle away
copy that efs folder that was created last time in my pc.
Delete? all the efs folder related files from sdcard?
what other files should I keep just in case? becaue I find myself formating the sdcard partition often. thanks
the kernel choice you use to root is your preference, i use CFROOT, because chainfire is a tried and tested longtime reliable developer, is apps are usually solid, i was on the galaxy note and chainfires work was always the best.
Always backup the efs to the pc and keep it safe, no real reason other than you then have a backup to restore just in case your usb storage or sd card gets accidentally damaged or wiped, its always wise to have an extra copy of a backup.
i also use cfroot because it includes a version of clockworkmode recovery and the cwm app, using the cwm app you are then able to flash custom roms from recovery, stock roms from the app or even kernels, without ever having to use the pc odin again and everytime you flash a new stock rom through cwm app you keep the root, so no messing afterwards and no horrible triangles or counter increase,. its just the job.
So in order of prefernece, this is how i install and gain root, from scratch.
1 - install my stock rom through odin.
2 - i then use Initial cfroot flasher to flash the zimage of the kernel and gain root.
3 - i then install mobile odin which i purchased because its also a good flashing tool for the phone and of course i already have the cwm app from step 2.
----------------------------
in the future
If i want to flash customisations or mods, themes, custom roms, i use cwm app to boot to recovery mode and flash them from the sd card.
if i ever want to flash another stock rom, the procedure is this -
1 - create a folder in the root of your sd card called firmware.
2 - copy the unzipped file(s) from the downloaded stock rom to the folder you made, and also the matching cfroot kernel for that rom.
3 - Then run cwm app, select Flash Stock Firmware, itll ask a couple of questions and ask about root, select the cfroot kernel you copied to the card as the source for root, not to keep the stock kernel, or youll lose the root.
4 - it then reboots to flashing mode and does what it needs to do, it will again reboot and appl the multi-csc etc.
After this it will reboot to the firmware where you are now on new rom and rooted, bingo.
IF YOU GET A HANG OR BOOTLOOP
dont panic, just pull battery, put battery back in, hold the 3 buttons down to boot to recovery and do a full wipe, then restart the system, job done.
Ok people do you different kernels and methods of flashing, but seriously this is why i flash the way i do, purely so i dont have to piss around with triangle away or jigs to reset counters, all that can be avoided and anyone who flashes a custom kernel through pc odin is just being lazy, there really isnt any need to do that, you can gain root by other methods like the ones ive already mentioned, even mobile odin lets you root your phone when flashing a new rom.
It sounds like you have the system sorted now and running anyway, if its working for you with that kernel then just stick as you are, happy days, i just always stick with cfroot for the reasons ive mentioned.
Anyway glad youve got sorted now, hopefully no more problems.
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.
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Ilikecheese said:
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Click to expand...
Click to collapse
you could try putting the sd in your pc to put the rom back on it, then back and try flashing. if that fails, sounds like its toast.
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Ilikecheese said:
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Click to expand...
Click to collapse
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Jewveeski said:
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Click to expand...
Click to collapse
thank you so much for the help (; ill let you know if i succeed
I think you will be okay, maybe try LG Flashtool and usb flash back to stock if those don't work.
I got it. Put the Rom in sd and it worked perfect. Whooo
Whew!..congrats.:good:
For some reason I can't flash from recovery menu..failed to mount sd/card, unknown error 150...
Maybe your SD is formatted in a file system twrp doesn't recognize? I had to reformat my 64gb to fat. I used twrp's built-in advanced wipe function to change external SD file system to fat, others have used a pc-based tool from ridgecomp.
You end up with the couple GB maximum individual file size limit, but I just copied my 11c 2.8gb system.img onto it without any trouble.
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
richsapf said:
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
Click to expand...
Click to collapse
You might be on the 11C update. Try downgrading (there's a thread in here somewhere) to 10b and you should be solid. I don't know if those numbers are correct, but check your build number.
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
B-Nice_88 said:
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And this check this for blocking an OTA: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
richsapf said:
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
Click to expand...
Click to collapse
Never ever take an OTA if you're rooted. In the future, just get rid of the notification, and then come here. Better yet - after you root, disable updates entirely.
Also, another reason to not take an OTA is because often times there are anti-rollback code in them, just like there is almost always a root patch. The regular "usb back to stock" and all the current root methods don't work on 11C for that very reason, and you have to use the KDZ method instead. If you jump on an OTA too early and find out there isn't a way to get back to the previous version... you're stuck. That happened to tons of people on one of the Galaxys I heard, and it so happened that the patch was a very good one. I've heard that the people who took that OTA are still stuck with it.
For 11C, there were early reports of those that rooted, but did not Bump or edit the system, got lucky and sometimes kept root after the OTA. Have you used a root checker to confirm you don't have root? None of the root methods are going to work on 11C, but you might still have it. If you don't, or something else is messed up, you'll need to get back to 10B to fix it.
Edit: Also, you're going to want THIS thread, not the other two I posted!
I did unroot before ota.. the only way I could at that time, via simple root. I just wanted to get the OTA out of the way(dont know why)
I used root checker, says no root.. If I go back to 10B I will try KDZ; or can I use the LG flashtool and try again with that using port 41, the 10B .dll, and 10B TOT?
For now I will follow your link and do as instructed..
Thank you laura
richsapf said:
I did unroot before ota.. the only way I could at that time.
Click to expand...
Click to collapse
Did you do anything else when you had root? Change anything in the system at all?
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
richsapf said:
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
Click to expand...
Click to collapse
Awesome! And yes, the sd card needs to be reformatted as fat32 for TWRP to see it.
Now that you're back on 10B, you can get the 11C update again if you want using this. The 11C OTA already has a rooted, deodexed flashable zip.
I do have that exact Rom/zip on both internal and ext card. Is there a program in particular to format, or just any, and should I format via pc(hook up usb with Windows 7), or is there a good .apk app.
Also, is 64gigs in any way too much.
Could I go up to 128gigs provided I use fat32.
Should the allocation just stay default? It looks like I can go up to around 4 mbs. Is that a cache type thing.
Sorry I am bombarding all these questions. I love learning this stuff. Need a break from studying for comptia 801/802.
Last, where is the thank u button?
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.
I have the LG v10 from T-Mobile. I bought the phone a few weeks ago and it had Marshmallow installed. Somehow I managed to install TWRP/SuperSU, but then had issues and flashed the official/stock MM image with LGUP. Afterwards I discovered that MM for this device is not currently rootable, and TWRP cant be flashed via fastboot because MM blocks it. So I returned the device to T-Mo store, lied and said it force-upgrade to MM and had began freezing up. They did an in-store trade for an identical model that had 5.1.1 Lollipop.
The device is currently still in factory condition in every way, with the exceptions that I unlocked the bootloader via fastboot and installed TWRP. Nothing else is modified yet and no custom ROMs have been flashed.
I recently became aware that there is no stock LP image for the T-Mo v10, only MM images are available. After all the issues I've had, I'm now paranoid and want to have a complete dump of the phone's entire contents (partitions, bootloader, system, etc) that is in KDZ or TOT format, and can be reflashed with the standard tools available. Since there is nothing official then I would have to do this myself. This would be useful in the event that I run into lots of issues and need to do a emergency stock restore.
I found a thread by XDA user @tungkick, in which he created a modified dump of the device while it was running LP. However, because it was unofficial and he didn't disclose this upfront, his thread was shut down. His file bricked multiple MM users. I assume it would work if one was still on LP and hadn't upgraded to MM. Not to mention that I cant seem to find his file anywhere. So I figure the safest way is to do this myself. I would be willing to make this file available to the community when finished, with full disclosure that it is unofficial. But the problem is, I don't know how.
I know that the Linux dd command can be used to dump images of various things, and I have read that this can be done on PC by connecting to the device via ADB or fastboot. This would hopefully result in an image file that contained the contents of all the device's partitions.
But another issue would be converting it to KDZ or TOT. And it would have to be done in such a way that it would be flashable with the standard tools.
Can someone please give me a technical understanding of the tools and knowledge I would need to undertake this? Would it be too complicated for someone like myself that has little Android/Linux experience (but is generally competent with computers/technology)?
Thanks for any advice!
Noone can help me with this?
To the mods/admins: I think maybe I posted this in an area where it is unlikely to get any useful answers. Can someone move the thread to the Help& Troubleshooting area of the general LG v10 forum (not here in the T-Mobile subforum)? Thanks!
I think it's just that if that could. have been done someone would have done it already. Even tungkick didn't make one for tmobile for some reason. I think because he made his root injected files from official lg files and lg has not released a kdz or tot for tmobile LP.
Just my observation... I could be wrong.
Sent from my pretty nifty brand new LG V10
@ planetbeen: I don't see why it wouldn't be possible. Linux's dd program can dump almost any connected device that it can see. But then it needs to be converted into a standard TOT/KDZ that can be flashed with any standard software. Which is why I want to create an unofficial backup of the entire phone before modifying it further, so I can do an emergency restore if necessary. I just need the right instructions from people who have the technical expertise.
I had trouble with my old LG v10, I had used LG's LGUP program to flash it to Marshmallow from my PC, only to realize that it couldn't be rooted or have a custom recovery. And I also discovered that I couldn't downgrade to Lollipop. So I returned the phone to the store and exchanged it for an identical model that still had LP. I just told them it had auto-upgraded to MM and started crashing. They exchanged, no questions. Before this I had various issues, like GPS crashing randomly when turning it on, Bluetooth also doing the same thing, and the Settings app also crashed sometimes when accessing the Security menu. I had flashed multiple ROMs, but stock-based and CM/AOSP-based, but kept running into issues, oftentimes the same ones. So I figured that something in the phone had become corrupt and figured that flashing stock MM would fix everything. Big mistake. I'll never let this phone upgrade again until MM is solidly hacked, which from what I've read may be a long time away. I paid enough for this phone and I really value hackability. I'm not the average Joe that just uses my phone for Facebook, etc. To me, if a phone cant be hacked, then buying/owning it is a waste of time/money. Same thing with every computer/electronics device I've ever owned.
Thanks again!
It looks like I'm going to have problems getting answers from knowledgable people, so instead of waiting, I'm going to take a little initiative and at least try to do the dump with dd. I found a post by @tungkick that says to enable USB debugging and make a backup file via dd with the 'adb shell' and 'su' commands. Is the following syntax correct?
dd if=/dev/block/mmcblk0 of=/sdcard/H901.bin bs=1024 count=6291456
Do I run these commands from a PC via command line while connected via USB? Or directly on the device in a terminal emulator? Or do I need to run the command while in fastboot/bootloader mode, while Android is powered down?
Thanks again!
Stock use tool extract kdz then choose file dz (use lgup)
remember can not flash if phone update 6.0
Never downgrade because phone brick now.
version 5.1.1
https://drive.google.com/file/d/0B_Hol5T47S-bQkJVemgzMDV0Nzg/view?usp=sharing
@ tungkick: Thanks for the info. I had used the dd command to dump my phone to external SD before, but the file was 6GB! I was unable to use Tool KDZ Extract to extract the *.dz from the *.kdz file you provided. I was able to flash your KDZ with LGUP, but it boots me into TWRP recovery near the end.
Do you mind if I publicly distribute a mirror copy of your file on my Dropbox, so that it will be available to others that need the stock LP firmware for this device?
Thanks again!
I just wanted to say that flashing your KDZ has possibly screwed up my device permanently. Your image has TWRP, not the stock recovery, and is pre-rooted with SuperSU. Normally this would be good but...............
Near the end of LGUP, the device boots into TWRP. System and MicroSD are mounted, but nothing else (data, cache, dalvik, etc). I was able to obtain a stock recovery *.img, then copied it over to my MicroSD while in recovery. Then I flashed it, booted the phone into stock recovery, and performed a factory reset. Afterwards I booted into system, and all looked good, until it got to the "Checking connection" screen, then a lot of apps started force-closing repeatedly. Because of this I can't get to the Home screen, and no amount of factory reset is working. It just keeps happening over and over again.
How to get out of this mess, anyone?
Help please!!!
Still looking for a solution and would really appreciate any help!
My theory is that the /cache and /data partitions somehow got corrupted during the flash. So I tried booting into FastBoot mode and issueing the commands:
fastboot erase cache
fastboot format cache
fastboot erase userdata
fastboot format userdata
It just says something something along the lines of "remote: cant format/erase in an unlocked state". If I relock the bootloader, it says that it cant erase/format in a locked state.
TWRP still cant read those partitions (they won't mount and cant be mounted), and the apps still start force-closing almost immediately after rebooting into system, before I can complete the setup, preventing me from getting to the home screen.
@ tungkick: Is there any possibility we can arrange a TeamViewer meeting to fix this?
Thanks!