You need three things besides your phone:
You lost data/wifi when flashing a CM UPDATE, this is your fault for not reading the threads, The FIX IS BELOW, in simple, plain english, easy to understand. DON'T MAKE ME DRAW PICTURES
1) Android SDK
https://developer.an.../sdk/index.html
Download it and install it. I'll only describe it for Windows OS.
2) The correct ROM
https://download.cya.../?device=enrc2b
or from my CM-12.1/AOSP threads
Download it and open it with WinRAR or Winzip or just unpack the whole thing. Directly in the root folder you'll see a file called boot.img
3) USB Cable connection between the phone and your PC
Connect the device to your PC. On your phone go to settings and enable USB debugging.
Now you are ready to flash the boot image.
a) copy the boot.img to the same folder as fastboot
if you downloaded the package from above, you'll see a folder structure that is a bit overwhelming. Navigate to
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools
and copy the file called boot.img from the ROM there.
B) open up the terminal
click on start and enter cmd.exe
enter the folder with
cd /
cd C:\adt-bundle-windows-x86-20140702\sdk\platform-tools
c) start the flashing
Now type:
adb reboot bootloader
or alternatively, restart your phone manually and press the buttons Power and Volume down until you see a white menu screen.
Now type:
fastboot devices
and you should see your phone
d) flash the boot.img
type:
fastboot flash boot boot.img
That's it, 3G and WiFi should work now. A more extensive How-To can be found here:
http://wiki.cyanogen...l_CM_for_enrc2b
Taken from my thread of the same title from the CM forums
http://forum.cyanogenmod.org/topic/101207-no-wifi-no-data-read-this/
IF YOU CANNOT FOLLOW THOSE SIMPLE INSTRUCTIONS GIVE UP NOW
Hi @Lloir,
as far as i can see you have removed the aosp5.1 thread, right? that means no work from you for one x+ anymore?
now i also see that there is no one x+ in your signature...
mmm...bad news...
is it just because of the newbies and there stupdi questions? the best way to get rid of them is to ingore them!!!
.
el-Loko said:
Hi @Lloir,
as far as i can see you have removed the aosp5.1 thread, right? that means no work from you for one x+ anymore?
now i also see that there is no one x+ in your signature...
mmm...bad news...
.
Click to expand...
Click to collapse
My X+ is dead and I'm now mostly working on Huawei devices.
shhh....ititit :'(
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey,@ Lloir
Ive tried this for my stock ROM that ive reverted to after having cyanogenmod 11, but it didnt work, I used the same boot.img from the firmware.zip. it did work successfully when reverting to cyanogen after it didn't work though.
What have I missed?
Any help would be appreciated.
Related
Disclaimer:
Code:
You will be doing everything at your own risk.
Only you will be held responsible if you end up damaging or bricking your device.
About this guide
This is a quick and easy guide to get rid of the ROOTED status in download mode on G2 devices.
By doing this, you will return to the factory look of download mode with it showing UNROOTED.
Special Note
I have only tested this on my LG-D802. I do NOT know if this works on other G2 devices.
Therefore, please report back whether it works for you so I can add your device to the OP.
Requirements
LG USB Drivers (Easy to find & install - Google is your friend)
Your G2 must be rooted to use this.
USB Debugging must be enabled in Developers Options.
A software to extract the attached .zip file.
Notepad++
Instructions
Connect your G2 to your PC using MTP. At this point, USB debugging is not necessary. If phone is not recognized, then install/reinstall USB drivers.
Now head into PC - right click on your phone and hit properties. Copy this line as shown in this screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the attached .zip and extract the content to anywhere you like.
Open rct.cfg using Notepad++. Now delete SERIAL because here you shall paste the serial number of your phone which you copied earlier.
You must now enable USB Debugging in Developers Options. It does not matter if you had it enabled earlier or not.
Cant find Developers Options? Enter Settings - General - About Phone - Software Information - hit buildnumber 7 times and go back to Settings menu.
Open the file named install from the extracted .zip and give it root access on your phone.
Done. Download mode will now show UNROOTED.
OPTIONAL: You can now flash KDZ/TOT file if you want to fully return to stock. The status in download mode will remain unrooted after flashing a stock firmware.
Credits
@Drachenminister - check out his thread
Reserved for FAQ and more.
Deleted
LOL this was very easy and it works like a charm. I am on CloudyG3 and download mode shows unrooted
Hello XDA
Today we're going to flash a touch CWM recovery to our phones.
First of all I want to thank all developers who made this become possible for our device,
-Kingo ROOT for giving root permissions (this is the one I used for my E460 and it worked like a charm)
-Optima Team for bringing us the unlocked bootloader.
-Chimey Jimmey for giving a non touch recovery and easy method to push it.
If you want a non touch recovery just tell me and I will post the file(it also may be found in some thread)
PRE-REQUISITES
1.Root Permissions on your LG L5II
2. Unlocked bootlader
NOTE: I tested this only on E460, I hope this works also on other L5IIs but I'm not sure.
EDIT: This will work if the non touch CWM version works on your device, the non touch version can be easily found in this forum section
I DO NOT ASSUME ANY RESPONSABILITY FOR BRICKED DEVICES OR ANY OTHER DAMAGE DURING THIS PROCEDURE, DO THIS ON YOUR OWN RISK.
1.Download this file and extract it. http://www.filedropper.com/touchcwmrecovery
MD5 sum:
Code:
94B805ADF74CD810CCF417C1FB985723
2.Then place it in your SDcard and open your terminal emulator(which can be downloaded from Play Store)
and type the following text:
Code:
su
dd if=/mnt/sdcard2/touchcwm_recovery.img of=/dev/recovery
3. When you have successfuly executed the previous commands in terminal emulator reboot in recovery mode to test it(this is the only method i know how to boot into recovery on this device)
Type this in terminal emulator
Code:
su
reboot recovery
I hope this worked for you and now you can do whatever you want with your new recovery.
Thanks for the attention, let me know if this was useful.
will this work with e450-10b
I did test this only on E460, if you can dump me your recovery.img i can build it for your model.
soo, it's opening a new way to build a custom rom for our phone?
I hope it is, now I am learning new stuff about kernel and other stuff in order to work on a costum ROM for our phones. Unfortunately our phones is the only one from LII Series with mediatek chipset and porting cyanogenmod is very difficult because mediatek refuses of sharing any data.
EDIT: I just saw that there's some open source stuff release on LG official site, I'm not sure if it includes kernerl source and all other stuff needed.
HTML:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=e460
include:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good as soon I can download that I will give a look to this! Hopefully we have everything opensource (now I can't downlad this because I'm using my phone and I'm without fast internet connection)
i think same, but keep calm
Just as the title says, I get this error when I flash cm13 Roms. I don't know if it is a bug with twrp or something actually wrong with my device. The only rom that I can flash is cypher for reason.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what to do.
Sent from my XT1526 using XDA-Developers mobile app
Download Minimal ADB and Fastboot, unzip to Desktop: http://forum.xda-developers.com/showthread.php?t=2317790
Reboot Moto E into bootloader mode, connect to PC.
Open a command prompt to the unzipped Minimal ADB and Fastboot folder.
Type (I'm assuming you're on Boost, given your forum carrier avatar): fastboot oem config fsg-id boost
Should only take a second to config, then disconnect and reboot the phone back into the bootloader, then go to recovery and try flashing CM13 again.
xtermmin said:
Download Minimal ADB and Fastboot, unzip to Desktop: http://forum.xda-developers.com/showthread.php?t=2317790
Reboot Moto E into bootloader mode, connect to PC.
Open a command prompt to the unzipped Minimal ADB and Fastboot folder.
Type (I'm assuming you're on Boost, given your forum carrier avatar): fastboot oem config fsg-id boost
Should only take a second to config, then disconnect and reboot the phone back into the bootloader, then go to recovery and try flashing CM13 again.
Click to expand...
Click to collapse
That worked thanks
Sent from my XT1526 using XDA-Developers mobile app
Have similar issue on Xiaomi Mi5. Not familiar with the command you're talking about but wonder if it would work there... can you explain what this minimal fastboot deal is? The only other solution I've found is delete the code that prevents flashing a rom for a diff device & hardbricking... which I don't wanna risk. Thanks for any help you can offer.
fourth1 said:
Have similar issue on Xiaomi Mi5. Not familiar with the command you're talking about but wonder if it would work there... can you explain what this minimal fastboot deal is? The only other solution I've found is delete the code that prevents flashing a rom for a diff device & hardbricking... which I don't wanna risk. Thanks for any help you can offer.
Click to expand...
Click to collapse
Can you post a screenshot of the error so I'll know exactly which one you're getting? I don't want to give you the wrong information.
Android_noob17 said:
Can you post a screenshot of the error so I'll know exactly which one you're getting? I don't want to give you the wrong information.
Click to expand...
Click to collapse
Well, I'm afraid not, but for the happy reason that it was fixed by flashing yet another ROM and checking all the options in TWRP manager to backup & wipe before flashing. Not sure if it was that I found the right ROM (screenshotted below) finally or that I should've been wiping while flashing in a single step like that (also screenshotted)
I too getting same problem ,how to solve
shiva sai teja said:
I too getting same problem ,how to solve
Click to expand...
Click to collapse
Just follow the instructions given by @xtermmin, the process is simple.
Hey,
I want to install a costum rom to get a free of bloatware system, but I have problems with rooting my device and installing TWRP. I tried some tutorials today, but none worked for the same reason. For example this one: https://forum.xda-developers.com/m4-aqua/general/root-t3421932 I have a e2303 so I downloaded the e2303 file and went into the adb folder opened cmd connected my phone with pc while I pressed volume down. after that I copy pasted the command "fastboot devices" but it didn't show me any phone, so I went to the next step and copy pasted the command "fastboot flash recovery recovery.img" , but cmd only said <waiting devices>, so I did that what a different guide said (connecting the phone with volume up), but even that didn't worked. I installed adb with adb setup 1.4.3 and answered every question with "y".
I unlocked the bootloader with Flashtool, and it worked. I even relocked and unlocked the phone again.
My phone is a E2303 with build number 26.3.A.1.33 on android 6.0.1, which should be marshmallow.
That is the adb folder where I tried it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I really hope that have an idea to help me <3
(picture if that is not working: https://picload.org/view/rpwdarpa/adb.png.html
update: https://www.youtube.com/watch?v=nQjg6ePnGAc this tutorial fixed my problem
You forgot to install ADB and Fastboot drivers }:->
Gray47Maxx said:
You forgot to install ADB and Fastboot drivers }:->
Click to expand...
Click to collapse
yeah, I used that tool but the phone didn't use the drivers automatically. which rom has the fewest bugs and no bloatware and is optimized?
GamingAori said:
yeah, I used that tool but the phone didn't use the drivers automatically. which rom has the fewest bugs and no bloatware and is optimized?
Click to expand...
Click to collapse
No one. But you can install stock, root it, install one of the bloatware-deleting scripts (I can provide you one), install SMK and then it'll be fine )))
Gray47Maxx said:
No one. But you can install stock, root it, install one of the bloatware-deleting scripts (I can provide you one), install SMK and then it'll be fine )))
Click to expand...
Click to collapse
yeah then I'm interested in a bloatware delecting script.
GamingAori said:
yeah then I'm interested in a bloatware delecting script.
Click to expand...
Click to collapse
Sorry for the delay >:^)
View attachment ClearModv2.zip
Followed the Unofficial TWRP link, this one https://forum.xda-developers.com/t/...215-twrp-for-sony-xperia-1-iii.4515465/unread
TWRP didn't flash to slot b, and like an idiot I thought, "well let's just do a and see if that works..."
It didn't work, and now only getting a blinking red light when connected to power and computer. No amount of trying to go in to fastboot, bootloader, recovery works. Newflasher, XperiaCompanion, and Emma are not showing anything. I saw this post, and wondering if I've actually managed to brick it beyond repair https://forum.xda-developers.com/t/how-to-save-a-black-brick.4426071/post-86959167
Please help. Any and all feedback welcome!
Thank you!
smmate3 said:
Followed the Unofficial TWRP link, this one https://forum.xda-developers.com/t/...215-twrp-for-sony-xperia-1-iii.4515465/unread
TWRP didn't flash to slot b, and like an idiot I thought, "well let's just do a and see if that works..."
It didn't work, and now only getting a blinking red light when connected to power and computer. No amount of trying to go in to fastboot, bootloader, recovery works. Newflasher, XperiaCompanion, and Emma are not showing anything. I saw this post, and wondering if I've actually managed to brick it beyond repair https://forum.xda-developers.com/t/how-to-save-a-black-brick.4426071/post-86959167
Please help. Any and all feedback welcome!
Thank you!
Click to expand...
Click to collapse
Where did you have the twrp file saved? I personally save any file I flash to my phone in the same directory as Platform Tools/ADB Fastboot install...that way I don't have to add the path location to the terminal command line.
Ainz_Ooal_Gown said:
Where did you have the twrp file saved? I personally save any file I flash to my phone in the same directory as Platform Tools/ADB Fastboot install...that way I don't have to add the path location to the terminal command line.
Click to expand...
Click to collapse
It was saved in the platform tools folder with all the necessary files
smmate3 said:
It was saved in the platform tools and ADB folder
Click to expand...
Click to collapse
Okay well that rules out the possibility of flashing the wrong file..
Ainz_Ooal_Gown said:
Okay well that rules out the possibility of flashing the wrong file..
Click to expand...
Click to collapse
I made sure I was downloading the correct TWRP file for the 1 III, updated platform tools to the current version, renamed the img to twrp.img, attempted to flash, and now just getting the notification led blinking red
Here is everything I did- let me know if I messed up somewhere
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ainz_Ooal_Gown said:
Okay well that rules out the possibility of flashing the wrong file..
Click to expand...
Click to collapse