Related
I have created this thread to give a step-by-step on how to flash a stock ROM build available on Google's developer site. (For those that are unaware, an unlocked bootloader is needed, and unlocking is part of the instructions below.)
I've also added a section on how to root for those that want it.
Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. See here for some further explanation.
So, without further ado:
How to flash a stock ROM
Step-by-step
Notes:
1) For the n00bs: read the entire post before proceeding;
2) MacOS-specific instructions: a) no drivers needed, and b) replace fastboot in the steps below with ./fastboot-mac
A. Install the drivers
1) Do not install LG drivers or the PDAnet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here or from here;
3) Install the drivers. See here on how to install them. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). (To enable USB Debugging, you first need to enable Developer options by going to Settings->About phone and tapping 7 times on the build number.) If you are using Windows 8, you will need to do this before installing the drivers.
B. Backup your data
1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
3) See here on how to backup your apps and app data if you don't have root.
C. Download the required files to your computer and extract them
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
3) Download the version of Android you want from here. Make sure you are using an occam image which is for the Nexus 4. Most old versions are not usually available on that site; however, there is a mirror on this site: Random Phantasmagoria.
4) Download the appropriate version (for your computer) of 7-zip from here and install it.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (which will obviously delete all your data & files in /sdcard...). Or do this.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU or Koush's Superuser; NOTE: So far, only SuperSU v1.43 and newer currently work properly with JWR66V (i.e., 4.3). I've attached v1.51 below.
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: Only if you are running the z20i bootloader: the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
Notes:
1) Yes, you will receive the OTA update notification (when it is available) for the next update. WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the bootloader, radio, boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically.
2) There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
3) Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all. If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects. If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader. If you do want to lock your bootloader, the command is: fastboot oem lock
How to return to stock if your USB port is broken
I am adding this how-to in case people need it, for return their device to Google, etc.
This is NOT meant to replace going through the steps in post #1. They are there for your learning, and should be used as a primary method of returning your device to stock. However, if your USB port is indeed messed up, then you will not be able to use the instructions in post #1.
Warning: if your USB port is indeed broken, and you complete all the steps below, you will have NO possible way at all to unlock your bootloader, or get root, or install a custom recovery. Period.
1) Ensure that you have root, and a custom recovery (CWM or TWRP) installed;
2) Download segv11's BootUnlocker app from the Play Store, install it and lock your bootloader with it;
3) Download the odexed version of this file (stock JDQ39 ROM) and place it on your device;
4) Download the JDQ39 stock boot image from here and the stock JDQ39 recovery from here.
5) If you want, you can also download the 0.48 radio and the z10o bootloader from here.
6) Reboot into CWM and flash the three files you downloaded in steps 3 and 4, and the file(s) you downloaded in step 5;
5) Turn off your device and reboot into the bootloader;
6) Go to recovery and access the stock recovery menu (i.e., when you see the android with the red triangle, hold power and press vol up) and do a factory reset and then wipe cache.
7) Reboot your device. Do NOT install any OTA updates if they present themselves. Read and follow this post.
8) Done. Now you are fully stock JDQ39 with a locked bootloader.
Reserved.
Awesome! Thanks again efrant!
Ok...
So I consider myself fairly good at this stuff. I've been rooting and doing custom stuff since the N1. I have messed up somewhere...
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc... It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
Ummmm... ****! I even rooted the Desire HD back when you had to do a bunch of weird terminal stuff. What happened? Little help?
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Jesus...
tomedic said:
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc...
Click to expand...
Click to collapse
Yeah, you know I personally don't recommend that
tomedic said:
It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
Click to expand...
Click to collapse
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
tomedic said:
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Click to expand...
Click to collapse
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
efrant said:
Yeah, you know I personally don't recommend that
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
Click to expand...
Click to collapse
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...
tomedic said:
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...
Click to expand...
Click to collapse
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
efrant said:
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
Click to expand...
Click to collapse
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------
tomedic said:
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
Click to expand...
Click to collapse
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...
tomedic said:
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...
Click to expand...
Click to collapse
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.
efrant said:
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
evaradar said:
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.
Click to expand...
Click to collapse
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
tomedic said:
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
Click to expand...
Click to collapse
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
This is indeed strange, as steps D10 and D13 do exactly that: factory reset and wipe cache.
In any case, I will make a note of it in the first post.
efrant said:
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.
Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
It worked! Thanks man!
And thank you efrant. Now to switch recoveries and get root! :laugh:
---------- Post added at 10:55 AM ---------- Previous post was at 10:40 AM ----------
evaradar said:
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.
Click to expand...
Click to collapse
Yup, I just rooted and had to do the same thing.
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Thanks again all. These little hiccups make it interesting!
evaradar said:
By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Click to expand...
Click to collapse
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
evaradar said:
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
Click to expand...
Click to collapse
Again, interesting. Not sure why this is.
tomedic said:
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Click to expand...
Click to collapse
Correct.
efrant said:
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
Again, interesting. Not sure why this is.
Correct.
Click to expand...
Click to collapse
I'm assuming that like the GN we need to rename the recovery-from-boot.p file if we want our custom recovery to survive a reboot?
EDIT- never mind I just looked through your 101 thread and answered my own question- thanks!!
Thank you for making this thread over here. Glad to have you as a moderator. I hope every noob reads all of your threads.
Sent from my BAKED N7
I recently unlocked and rooted my nexus 6, installed twrp for back up. Then I wiped before making a back up. No I have no os on phone. Is there a fix or am I screwed?
Try using fastboot to flash factory images
Just grab a factory image and flash it.
Remember wiping a device does just that. Wipes it clean
The thing is, I can boot into recovery, but my phone does not show up on my laptop. So I am not sure how to load a factory image. Thx in advance for all the help.
If it doesn't connect while in recovery, uninstall/reinstall drivers.
Doogadoo said:
The thing is, I can boot into recovery, but my phone does not show up on my laptop. So I am not sure how to load a factory image. Thx in advance for all the help.
Click to expand...
Click to collapse
Boot in to recovery, choose reboot system, TWRP will say, no OS installed are you sure? answer yes / swipe, TWRP will ask/say your device is not rooted, do you want to root it? Swipe to confirm.
Reboot your phone, pressing power and volume down, choose recovery mode again, your phone should show up on your lappy.
If not, re-install drivers - adb/fastboot as mentioned before.
For some more info and factory image:
http://https://developers.google.com/android/nexus/images
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Try to check your USB cable, most of the time charging issue is due to cable
shubham1358 said:
Try to check your USB cable, most of the time charging issue is due to cable
Click to expand...
Click to collapse
Cable is ok. I have another Le2 and it is charging with that cable very well
I am facing same problem. How you solve this issue? Blue led blinks after flashing any rom and bootloop.
xerol said:
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Click to expand...
Click to collapse
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Forthe55 said:
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Click to expand...
Click to collapse
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Brother same thing happened to me, a week ago. I cant say about your problem but my problem was due to faulty power button. Actually due to that reason my phone actually kept restarting itself. It showed red light blinking while charging and wasn't able to bypass the optimizing app screen. I also thought it was a software issue but actually it wasn't. I spent about 2 hours figuring out what the actual problem was. The problem was: As we know when power button is hard pressed for about 10-15 seconds it reboots itself.
Although the repair shop guy didn't put new power button but he added a tiny piece of paper in between the power button and body housing to prevent the issue and voila the problem was solved.
delltech1 said:
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Click to expand...
Click to collapse
Hi, Thanks. I actually did that first, flashing through qfil the same rom. it helped me to go to settings after umpteen attempts to go past language selection screen, and i was just able to oem unlock and enable usb debugging (actually after a 2nd partial failed flashing). the phone kept freezing within seconds of booting up. Now After i unlocked the bootloader and installing twrp and flashing many roms thru twrp, i am still having the same problem of booting up and freezing at start-up. cant flash again through qfil, as i will again loose the unlocked bootloader and twrp.
At least , now i can try different roms to see which can unbrick it. last one used was the twrp flashable rom based on eui (small eui by aurel) but it also freezes on language selection screen or beyond.
I am running out of ideas, lets see.
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
If nothing helps it can be only a HW failure, maybe the power button, try usb 2.0 port during the flash process, i had issues with 3.0 on my pc, if that doesnt help.try a different cable, no more suggestions, sorry.
delltech1 said:
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
Click to expand...
Click to collapse
My phone has been flashed multiple times by qfil method. And always it hangs at initial setup (so it boots up, but hangs at language selection or further up screens, before setup can complete and launcher could be loaded).
While trying to flash again with qfil once it stopped at 25 percent (because the battery went dead). Charged the battery and booted up the phone, and i was surprised it booted up. After 2-3 attempts i was able to reach the launcher screen and immediately enabled developer options and oem unlock / usb debugging. Only had few split seconds to do this and the phone froze again. After that i installed twrp and hence treying different roms. Most fail at setup.
Just tried MIUI 9PRO ROM. It also froze at setup multiple times, but once i was able to complete the setup and miui launcher is up , but it reboots or turn off the phone just after that. So cant do anything with the phone. Unsure of whether a newer bootloader will help in these freezing issues as i have been able to boot up at least in some roms only if for few seconds. Will try to tinker the settings of miui rom (if the phone let me do it before freezing/hanging). Lets see. Thanks for suggestions. More suggestions welcome, because i am still unsure weather this is a software or hardware related problem. I am guessing that it may have something to do with Google security as earlier i was getting msg that phone has been wrongly resetted and needs to verify with Google (but i couldn't get a chance to use the same account, as phone kept freezing at setup).
Did you fully charge the battery, if not let it fully charge in twrp. Flashing the roms in twrp works everytime or do you see any errors? Before you flash anything disconnect the usb cable.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
Try to flash the 21s bootloarder with modem, one zip using twrp. Go to fastboot mode and wipe modems. fastboot erase modem1st fastboot erase modem2st. Put the phone to flash mode and reimage with qfil. Before you do it write down both imeis, you can find them also on the original package on the backside. Also try to remove all sim cards from the phone and try a different cable. If nothing helps, hw issue, maybe the power button mention earlier in this thread.
After reflash skip everything at setup and reset phone to factory defaults. OEM is already unlocked, you dont have to do it again.
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Forthe55 said:
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Click to expand...
Click to collapse
Yeah sorry i screwed the command its fastboot erase modest1 modemst2, my bad.
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Forthe55 said:
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Click to expand...
Click to collapse
So you erased modems and reflashed with qfil right? If so i assume its a HW problem. Try the fix with the power button, i ran out of ideas
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
delltech1 said:
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
Click to expand...
Click to collapse
Did that also, the same problem. The phone freezes after the os is booted. I was wondering what is that isnt touched by flashing ( in download mode or fastboot mode or through twrp). I may need to tinker that. The roms are all fine in the sense they all stop at the same points. Something in the phones partition, which isnt touched by flashing? (There must be, as i flashed with qfil, the oem unlock remains, the bootloader didn't lock, and it remains unaffected by re-imaging)
Try this, maybe it helps:
https://forum.xda-developers.com/le-2/help/issues-installing-twrp-rom-le-s3-x522-t3618662/page2
Hello
I followed the instructions on the main Magisk thread to add Magisk via Odin to a stock phone without a custom recovery. All seemed to work as expected. On rebooting the phone after flashing my security pattern isn't recognised and I'm locked out. I extracted the boot.img from the correct firmware at sammobile. I'm guessing the patched boot image may somehow invalidate my pattern. There's no way I'm getting the pattern wrong as I've used it for years.
The phone has been reset to factory setting before I started so there's no data on it I need to save. What's my best option to get back in?
OK. I've worked it out myself. It initially just said restart your phone after a number of incorrect attempts, which it did 3 or 4 times, but in the end gave me a countdown from 10 more attempts to a factory reset. Now reset and all is fine.
Did you have to factory reset after applying boot image to get it to boot? I've tried this a few times without doing but it just boot loops on my S7 Edge.
to reset your lock screen settings back to default swipe only, use TWRP to delete the file
/data/system/lock settings.db
syndre said:
to reset your lock screen settings back to default swipe only, use TWRP to delete the file
/data/system/lock settings.db
Click to expand...
Click to collapse
thats one way..... or you can flash this.https://drive.google.com/open?id=0B68teDtzimGpNDNsQUN1WGdXVEU
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Post any bricks below that you have encountered!
I'm interested in how many variations there are, and how common they are.
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Hovo said:
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Click to expand...
Click to collapse
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
TechNash said:
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
Click to expand...
Click to collapse
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
It goes away when u log in to google with the last account that is associated with the phone
Hovo said:
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
Click to expand...
Click to collapse
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
TechNash said:
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
Click to expand...
Click to collapse
It would make sense if it was an OTA update TY
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Nightwinter said:
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Click to expand...
Click to collapse
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
TechNash said:
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
Click to expand...
Click to collapse
Keep what in the SD card? the is no file in your quote.
Nightwinter said:
Keep what in the SD card? the is no file in your quote.
Click to expand...
Click to collapse
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
graevon said:
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
Click to expand...
Click to collapse
Thanks for explaining that to him.
TechNash said:
Thanks for explaining that to him.
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data
Mujeeb64 said:
how to remove Verification Failed or root in the TWRP file manager without losing data
Click to expand...
Click to collapse
Flash ashyx-no-verity-no-encrypt.zip in twrp.
Reboot
TechNash said:
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Click to expand...
Click to collapse
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
smirk24 said:
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
Click to expand...
Click to collapse
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
TechNash said:
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
Click to expand...
Click to collapse
Id love to but i dont know how to get the marshmallow software and install it to the phone but id like to learn how.
How to recover from Verification Failed without losing data ?Does installing TWRP via Oddin Works and does it able me to transfer my data after installing TWRP ? I dare not try doing it as i have never did it b4