Related
My Nexus S i9020T won't boot past the Google splash screen* (with an unlocked padlock at the bottom) after I unlocked to boot loader and tried to root it. I'm using a Mac but I can boot into Win7 if need be.
How do I diagnose this and obviously how can I recover the os? Thanks in advance!
Facts:
-Running 2.3.4 before unlock/root attempt
-Booted fine after the unlock but the root screwed something up
-There were errors in terminal during the process (ERROR: could not get pipe properties)
*=samsunghub.com/wp-content/uploads/2011/03/nexus-s-handson-google.jpg
Sorry if out smarting the spam bot is breaking any rules.
I'm guessing you flashed a boot.img to try and root it?
That's what screwed up.
Take battery out, put it back in, hold volume up and power at the same time to get to Bootloader.
Flash the latest cwm recovery, boot to recovery. mount the internal usb,
go to: http://forum.xda-developers.com/showthread.php?t=1056062
download: http://android.clients.google.com/p...206299fe6.signed-soju-ota-121341.da820629.zip (Model: i9020T Full Rom: GRJ22, KD1 )
put it in the root of the internal sd.
boot back up to bootloader and start it, it will auto wipe/restore back to stock 2.3.4
Thanks that did it.
EDIT: I was using this guide and got to step 17, then everything went bad. As I understand it, I am unlocked but not rooted at this point, correct? If so what's the easiest way of rooting from here? (Also, does root=super user?)
willjeffery said:
Thanks that did it.
EDIT: I was using this guide and got to step 17, then everything went bad. As I understand it, I am unlocked but not rooted at this point, correct? If so what's the easiest way of rooting from here? (Also, does root=super user?)
Click to expand...
Click to collapse
Yes flashing the superuser zip = root.
What version of CWM recovery did you install?
Sent from my Nexus S using XDA App
matt2053 said:
Yes flashing the superuser zip = root.
What version of CWM recovery did you install?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
3.0.0.5, tho its not on my device anymore since I refreshed it.
Use this newer version from this thread:
http://forum.xda-developers.com/showthread.php?t=1039584
3.0.0.5 has issues. Doesn't flash correctly many times. 3.0.2.4 works much better
Alright I've installed the new version and flashed "su-2.3.6.1-ef-signed.zip". How do I know if I'm rooted?
Boot up ur phone and you should have an su app.
Download titanium backup ans check if you have problems.you can also install busybox while using it.
Sent from my Nexus S using Tapatalk
nxt said:
I'm guessing you flashed a boot.img to try and root it?
That's what screwed up.
Take battery out, put it back in, hold volume up and power at the same time to get to Bootloader.
Flash the latest cwm recovery, boot to recovery. mount the internal usb,
go to: http://forum.xda-developers.com/showthread.php?t=1056062
download: http://android.clients.google.com/p...206299fe6.signed-soju-ota-121341.da820629.zip (Model: i9020T Full Rom: GRJ22, KD1 )
put it in the root of the internal sd.
boot back up to bootloader and start it, it will auto wipe/restore back to stock 2.3.4
Click to expand...
Click to collapse
How can I flash CWM recovery? I have the same problem as OP. I guess it would be from ADB but don't have it installed. ANy guide for this?
Thanks
SpoonerPS3 said:
How can I flash CWM recovery? I have the same problem as OP. I guess it would be from ADB but don't have it installed. ANy guide for this?
Thanks
Click to expand...
Click to collapse
All the info you need is here:
http://forum.xda-developers.com/showthread.php?t=1007782
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Make sure you're using a perm root method. and make sure you have the correct updated SU application. My root wouldn't come through because I didn't have the latest SU.
Hopefully I helped.
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Vs Nexus S4G using tapatalk2
Unlocked the boot loader with fast boot commands then flashed superuser.zip with clockwork 3.x.x and twrp 2.2.0 haven't tried flashing any Roms since nothing seems to stick...
Sent from my Nexus S 4G using Tapatalk 2
And Vidal I used the toolkit you linked me to in my last q&a post...
Sent from my Nexus S 4G using Tapatalk 2
vidaljs said:
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Also after looking into the scripts and files in the method with the toolkit it seems none of the files get pushed to the device to begin flashing
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
By default, any recovery you flash on the system will be gone by the next reboot. This is a security measure the android os does I think.
1. You can flash a ROM. Anyone. I prefer aokp or cna. That way the recovery sticks (the recovery sticks on all the ROMs besides stock)
OR
P.S. You will need the latest cwm recovery
2. So all you need to do is to flash the recovery of your choice. I would recommend CWM for this short guide. Then once flashed go to the recovery make a backup. Then if it reboots flash the same recovery again. Boot into it and restore that backup. When you restore it and go reboot system now it should come up with a menu saying recovery flash fix (or something around those lines). Hit/navigate to yes and you should get a sticky recovery from there. BTW I have not tried this method.
You cannot blame me for bricking, damaging or done anything to your phone
Hope this helps.
Regards,
UselessSniper001
P.S. I don't know how root isn't sticking. I mean if you have flashed the su is the recovery already well then you are all set to go. Unless you haven't actually flashed the su in the recovery. Then flash the recovery from your PC boot into the recovery and flash the su files in the recovery. Reboot and enjoy. Then follow this guide above. Or follow this link:
http://forum.xda-developers.com/showthread.php?t=875875&page=2
I finally figured out the SU and CWM I was flashing was ancient so I found the newest and they stuck with help of the fix ya mentioned inside CWM... Thanks
Sent from my Nexus S 4G using Tapatalk 2
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.
PROBLEM SOLVED, THREAD CLOSED, THANKS FOR YOUR HELP
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock
Try BETA-SuperSU-v2.65.
lost101 said:
Try BETA-SuperSU-v2.65.
Click to expand...
Click to collapse
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app
@Chainfire please do have a look, it's a supersu problem.
Sent from my MotoG3 using XDA-Developers mobile app
@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.
Aman Dewett said:
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you try 2.62-3?
lost101 said:
@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.
Click to expand...
Click to collapse
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Sent from my MotoG3 using XDA-Developers mobile app
Aman Dewett said:
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Click to expand...
Click to collapse
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.
lost101 said:
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.
Click to expand...
Click to collapse
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
That is the reason everything was working perfectly before and still i'm following the same process but this time after flashing supersu on stock it stuck on logo.
Sent from my MotoG3 using XDA-Developers mobile app
MrTooPhone said:
Did you try 2.62-3?
Click to expand...
Click to collapse
Yes
Sent from my MotoG3 using XDA-Developers mobile app
Aman Dewett said:
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
Click to expand...
Click to collapse
Please state clearly that you did a Factory data reset via Settings > Backup & reset.
lost101 said:
Please state clearly that you did a Factory data reset via Settings > Backup & reset.
Click to expand...
Click to collapse
No i did not performed "factory data reset" through backup & reset settings.
I format phone through twrp only..
At first i wiped it normally, then format it through advance wipe option and removed whole os from phone then flashed stock through CMD.
Sent from my MotoG3 using XDA-Developers mobile app
I cannot help you as you refuse to follow the instructions I have provided.
lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
Ok this time i will follow proper instruction likewise format phone through backup & reset option and then will open boot loader mode and flash the rom according to instruction (commands) provided. Let's see what will happen.
As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.
lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
I did properly what you said, at first i "factory reset" through backup & reset option, then i open bootloader mode and flashed it according to given instructions. At the end after flashing supersu 2.65 stuck n logo. Same issue.
arunhebbare said:
As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.
Click to expand...
Click to collapse
removed cache and user data as well bro didn't worked.
I faced the same problem on 6.0.1 only, and I tried every su version "UPDATE" "BETA", rooted with kingroot and unfortunately I lost my SIM card recognition!
Sent from my MotoG3 using Tapatalk
Aman Dewett said:
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock
Click to expand...
Click to collapse
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?
arunhebbare said:
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?
Click to expand...
Click to collapse
If you can read i mentioned in OP that phone gets freeze on logo, It is not going on booting stage.
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
I don't think the update will even proceed being that you're on a rooted ROM. I have that notification too, and i just don't know how to turn it off.
I to am rooted,unlockboot and stock rom. I don't feel like taking a chance. So I used titanium backup to freeze the software update and in the drop down notification if you press it, it's a notification from Google play services if you block it in apps it will disappear from your drop down. I also deleted the update zip in the cache folder.I used es file explorer ,device/cache/update
popwar said:
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
Click to expand...
Click to collapse
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
Why can't you flash the phone that is already rooted and has TWRP?
All you are doing is opening the LGUP tool and flashing the new H90120j .kdz file using the "refurbish" option then flashing the H90120j .tot file that has TWRP using the "update" option which will flash the phone regardless of what is running on your phone. The guides on the first link explain that. I believe your concern is keeping all of your settings and apps. Look up Titanium backup, it works for me.
Thank you. I only flash the LGH901AT-01-V20j-310-260-JUL-12-2016-ARB02+0ROOTTWRP tot file and all is good.
Well except that I lost Dolby audio.
I will look for a fix.
jun19inf said:
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Click to expand...
Click to collapse
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Anyone?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
There's a guide in general that tells how to do all this. In fact jun19inf WROTE it.
In a nutshell, do a twrp backup.
Upgrade to 20j by flashing the stock 20j kbz.
Enable usb debugging and oem unlock
flash tot that has twrp in it.
Now you can go into twrp and 1) root via supersu 2) restore ONLY data from your twrp backup taken previously to get your apps etc back. Alternatively Titanium Backup will also do just fine.
njdevils28 said:
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Click to expand...
Click to collapse
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ah. Thank you very much!
-NJ
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Where can I download the update file?
wbexpress said:
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Click to expand...
Click to collapse
Did you select refurbish or upgrade?
I believe you need to select upgrade when flashing or you get stuck in TWRP
Sent from my LG-H901 using XDA-Developers mobile app
How to root V10 T-mobile M.M ver V20L
How to root V10 T-mobile M.M ver V20L
Can some one guide me on the following:
1. Can I flash back and downgrade to Software version V20J from V20L.
2. Is there any root method for V10 t-mobile MM ver V20L.
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
jonsat said:
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
Click to expand...
Click to collapse
Thanks so much for your reply, I was about to flash it to downgrade my V10 from V20L to V20J i even downloaded the files for it Phew....
Okay, I have searched most of the rootings are V20J i have not found a method for rooting and twrp for V20L software update.
Please if u can share the link, that would be helpful...
thanks regards,
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
jonsat said:
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
Click to expand...
Click to collapse
Awwhh GOD!!! big thanks for your help, u r truly an awesome person. Peace and blessing upon u.
regards,