Hi all,
I installed the E988 Kitkat stock (OTA) rom on my AT&T E980. The flashing went fine but there was no network/signal. I realised that the modem of E988 and E980 are incompatible and that I need to flash the correct modem for E980. So, I needed to root,install CWM recovery and flash the modem. I did some searching around on xda and found the methods to root, install recovery and flash the modem. In this thread, I want to list out the steps I carried out to get it working so that it may help others who are struggling to get it right.
Steps:
Flash E988 Kitkat OTA Rom on E980
Download the E988 Kitkat rom KDZ file from here :
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW453895432109876543213/E98820A_00.kdz
The instructions to flash the KDZ onto your device are in this thread (Thanks to hyelton) :
http://forum.xda-developers.com/showthread.php?t=2420219
Factory Reset after reboot
When the device reboots after flashing, it will ask to enter a pin to decrypt. To solve it you will have to factory reset the device. Press the power button till the device powers off. Then, press the volume down button and power button simultaneously till the screen powers on. It will show instruction on how to factory reset. Press power button once and it will ask for confirmation. Press power button again and the factory reset procedure will start. Your device will reboot after that. On reboot, you can then proceed in the usual way you would after a factory reset.
Root the Kitkat Rom
Now, you need to root your device. I searched xda for a rooting method that will work with E988 4.4.2 rom but could not find anything specific. Then, I stumbled upon the method from the following thread and it worked !!!
http://forum.xda-developers.com/showthread.php?p=51575993
Thanks to jarari2
Install CWM recovery
To install the CWM recovery on 4.4.2, I downloaded G Pro Kitkat Recovery app from the following link and installed on my device :
https://drive.google.com/file/d/0B4vSbKccbcIOV1NjMDlqWUdmVm8/edit?usp=sharing
Thanks to hoangnova from lgviet forum
Flash the E980 modem
Download the correct modem that will work with E980 from here:
http://storagecow.eu/index.php?dir=Xda%2FLG+Optimus+G+Pro%2FModems%2FPanama+E980H+Modem%2F
Thanks to hyelton again.
After downloading, transfer it to your internal SD card so that you can flash it through CWM recovery. Take care that you copy it to the "internal" SD card as Kitkat reportedly has problems with accessing the external SD card. Though there may be workarounds for accessing the external SD card, I did not want to get involved in those at the moment.
After you transfer the modem zip file to internal SD card, reboot your device into recovery mode. You can easily boot into recovery mode from the G Pro Kitkat Recovery app that I wrote about in the previous step.
Once you are in CWM recovery, flash the modem zip file as you would usually do and then restart the device. You should be able to see that the network starts working and your carrier's signal bars.
The only issue that I have observed till now with this E988 rom is that it shows the internal SD card storage from 32 GB to 16 GB.
If someone can point to some method to increase the storage to its original, it will be excellent. Otherwise, I do not really mind it for the time being. I am using this rom till the time a Kitkat OTA for E980 is released. Once that is there, I will flash that stock rom.
Hope this post helps someone
Excellent! Does the speakerphone work? Regarding the internal sd showing as 16gb, I believe I remember this issue so try searching some of the other hk kitkat roms
Sent from my LG-E980 using Tapatalk
Logic717 said:
Excellent! Does the speakerphone work? Regarding the internal sd showing as 16gb, I believe I remember this issue so try searching some of the other hk kitkat roms
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
The speaker phone does appear to work fine. I tested listening to a couple of calls and I could hear loud enough on the speakerphone. The speaker phone volume can be adjusted by the volume up/down keys when the speaker phone is on.
I wonder if flashing madmack's kernell would fix the storage issue.
Thanks a lot for the guide, it appears near perfect, if only we can figure out a way to fix the internal sd capacity issue. Keep us posted if you find anything.
Sent from my LG-E980 using XDA Premium 4 mobile app
luisoman2000 said:
I wonder if flashing madmack's kernell would fix the storage issue.
Click to expand...
Click to collapse
I want to be as close to stock as possible. Thus, I am avoiding using a custom kernel to fix the storage issue.
A kernel may very well be the fix as storage allocation is done by a kernel. And the stock E988 kernel is made for a 16 GB storage. Is there any other possible way other than using a custom kernel ?
Sent from my LG-E980 using Tapatalk
Damn. I cant flash it when it gives me low battery error. It makes me raging all the time.... also i am not even able to extract it.
Sent from my LG-E986 using XDA Free mobile app
Ok. I flashed.. Now I have an issue on the screen I hope will get handled easily.
Once the flash completed, my phone rebooted and now I have this on my screen.
"Enter PIN/password to decrypt"
"30/30 attempts remaining"
Ok, so whats the pin? Never had one on here before.
fosunite said:
Damn. I cant flash it when it gives me low battery error. It makes me raging all the time.... also i am not even able to extract it.
Sent from my LG-E986 using XDA Free mobile app
Click to expand...
Click to collapse
Try charging the battery to 40% or above and then flash and see if it succeeds. Also, try changing the connection mode to 'LG Software ' before flashing.
Sent from my LG-E980 using Tapatalk
fastvan67 said:
Ok. I flashed.. Now I have an issue on the screen I hope will get handled easily.
Once the flash completed, my phone rebooted and now I have this on my screen.
"Enter PIN/password to decrypt"
"30/30 attempts remaining"
Ok, so whats the pin? Never had one on here before.
Click to expand...
Click to collapse
Oops, I forgot to mention this small issue in the guide. When the device reboots after flashing, it will ask to enter a pin to decrypt. To solve it you will have to factory reset the device. Press the power button till the device powers off. Then, press the volume down button and power button simultaneously till the screen powers on. It will show instruction on how to factory reset. Press power button once and it will ask for confirmation. Press power button again and the factory reset procedure will start. Your device will reboot after that. On reboot, you can then proceed in the usual way you would after a factory reset.
Sent from my LG-E980 using Tapatalk
sandyiscool said:
Oops, I forgot to mention this small issue in the guide. When the device reboots after flashing, it will ask to enter a pin to decrypt. To solve it you will have to factory reset the device. Press the power button till the device powers off. Then, press the volume down button and power button simultaneously till the screen powers on. It will show instruction on how to factory reset. Press power button once and it will ask for confirmation. Press power button again and the factory reset procedure will start. Your device will reboot after that. On reboot, you can then proceed in the usual way you would after a factory reset.
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
Ok, got that out of the way. I'm in and installed CWM. I placed the modem.zip file in the phone. I went to CWM and chose to reboot into recovery so I can flash the modem. All it did was reboot into "Android System Recovery" and not CWM. How do I fix this so I can flash the modem?
fastvan67 said:
Ok, got that out of the way. I'm in and installed CWM. I placed the modem.zip file in the phone. I went to CWM and chose to reboot into recovery so I can flash the modem. All it did was reboot into "Android System Recovery" and not CWM. How do I fix this so I can flash the modem?
Click to expand...
Click to collapse
Did you install CWM using the G Pro Kitkat Recovery app ? If you did then make sure you tap on 'Flash Kitkat Recovery for G Pro' and when it's done boot into recovery from the app itself.
Sent from my LG-E980 using Tapatalk
sandyiscool said:
Did you install CWM using the G Pro Kitkat Recovery app ? If you did then make sure you tap on 'Flash Kitkat Recovery for G Pro' and when it's done boot into recovery from the app itself.
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
AHH! Miss that part! Working Beautifully Now!
fastvan67 said:
AHH! Miss that part! Working Beautifully Now!
Click to expand...
Click to collapse
cool....enjoy then
Sent from my LG-E980 using Tapatalk
Witch languages are avaiable?
elvitas said:
Witch languages are avaiable?
Click to expand...
Click to collapse
Available languages :
{
"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"
}
Sent from my LG-E980 using Tapatalk
16 or 32 GB
sandyiscool said:
The only issue that I have observed till now with this E988 rom is that it shows the internal SD card storage from 32 GB to 16 GB.
Click to expand...
Click to collapse
Flashing KDZ file rewrites partition table of a phone. If you use other model's KDZ (with another internal memory size) you will get partition sizes of that model. Custom and stock kernel will see the same size. What to do? The long way:
(1) Make backup of your boot, system, and data partitions with the custom recovery you have; (2) backup somewhere your sdcard data; (3) flash AT&T's TOT file (complete factory state restore); (4) root it, install custom recovery (the same you used in p.1); (5) restore the boot, system, data backups you saved in p.1; (6) restore your sdcard data (from p.2); (7) do not forget to upload and make available boot and system partitions you got in p.1 for others, helping them to jump to the new version using custom recovery with a single step.
Thanks for this guide - its a bit time consuming, but worth it - everything works including speakerphone and its stable. Almost no bloat. The only caveat is internal storage capacity is 16gb instead of 32gb. NextApp SDFix takes care of un-writable external SD cards, and for me it made all 32gb of internal storage available.
Of course I tried to flash madmack's hacked TWRP after i had completed everything and it soft bricked. Putting the phone in download mode and reflashing fixed it and didn't wipe data, but I had to root and install CWM again and after running NextApp SDFix, this time I didn't get all internal storage capacity back, so who knows, I think that might be an easy fix for someone with some skills.
Bottom line, right now this is the best stock based kitkat solution for the E980.
I can confirm that sandyiscool guide works on the international E989 16GB (it's the same as international E988). If somebody have problems with the root (after flashing CWM/TWRP recovery) you can flash the latest Philz CWM recovery and do re-root, it works and keeps the root working as it should.
If you using custom DPI (by editing the build.prop) it will not work as it worked in Jelly Bean, most of LG's app will not work. I recommend to use Xposed Framework and AppSetting module for setting app by app your favorite DPI (I use 360/380/400 depending on the app), you have to use AppSettings v1.9 any earlier version will not work properly, you can download the last version here -
http://repo.xposed.info/module/de.robv.android.xposed.mods.appsettings
My impression so far (I did a factory reset before and after flashing the rom). Everything working very smooth the Dialer opens the first time a bit faster than in JB. I love the new addons like the call popup and the floating apps (now it supports more apps) the double tap for screen off and more. One of the first things that I notice is that the sound quality is much better over the BT and the earphones jack.
I also notice a better call quality. The speaker is loader and the sound quality better so I didn't flash my old Modem back.
The only problem I haven't found a solution for it yet is when I get a call from someone in my contacts the phone doesn't show his name only the number, also in call log there are only numbers instead of names+numbers.
That's it for now, will update about the battery after some more usage.
elvitas said:
Witch languages are avaiable?
Click to expand...
Click to collapse
You can use an app like Morelocal2 for more languages support (you'll need root).
sandyiscool said:
Hi all,
I installed the E988 Kitkat stock (OTA) rom on my AT&T E980. The flashing went fine but there was no network/signal. I realised that the modem of E988 and E980 are incompatible and that I need to flash the correct modem for E980. So, I needed to root,install CWM recovery and flash the modem. I did some searching around on xda and found the methods to root, install recovery and flash the modem. In this thread, I want to list out the steps I carried out to get it working so that it may help others who are struggling to get it right.
Steps:
Flash E988 Kitkat OTA Rom on E980
Download the E988 Kitkat rom KDZ file from here :
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW453895432109876543213/E98820A_00.kdz
The instructions to flash the KDZ onto your device are in this thread (Thanks to hyelton) :
http://forum.xda-developers.com/showthread.php?t=2420219
Factory Reset after reboot
When the device reboots after flashing, it will ask to enter a pin to decrypt. To solve it you will have to factory reset the device. Press the power button till the device powers off. Then, press the volume down button and power button simultaneously till the screen powers on. It will show instruction on how to factory reset. Press power button once and it will ask for confirmation. Press power button again and the factory reset procedure will start. Your device will reboot after that. On reboot, you can then proceed in the usual way you would after a factory reset.
Root the Kitkat Rom
Now, you need to root your device. I searched xda for a rooting method that will work with E988 4.4.2 rom but could not find anything specific. Then, I stumbled upon the method from the following thread and it worked !!!
http://forum.xda-developers.com/showthread.php?p=51575993
Thanks to jarari2
Install CWM recovery
To install the CWM recovery on 4.4.2, I downloaded G Pro Kitkat Recovery app from the following link and installed on my device :
https://drive.google.com/file/d/0B4vSbKccbcIOV1NjMDlqWUdmVm8/edit?usp=sharing
Thanks to hoangnova from lgviet forum
Flash the E980 modem
Download the correct modem that will work with E980 from here:
http://storagecow.eu/index.php?dir=Xda%2FLG+Optimus+G+Pro%2FModems%2FPanama+E980H+Modem%2F
Thanks to hyelton again.
After downloading, transfer it to your internal SD card so that you can flash it through CWM recovery. Take care that you copy it to the "internal" SD card as Kitkat reportedly has problems with accessing the external SD card. Though there may be workarounds for accessing the external SD card, I did not want to get involved in those at the moment.
After you transfer the modem zip file to internal SD card, reboot your device into recovery mode. You can easily boot into recovery mode from the G Pro Kitkat Recovery app that I wrote about in the previous step.
Once you are in CWM recovery, flash the modem zip file as you would usually do and then restart the device. You should be able to see that the network starts working and your carrier's signal bars.
The only issue that I have observed till now with this E988 rom is that it shows the internal SD card storage from 32 GB to 16 GB.
If someone can point to some method to increase the storage to its original, it will be excellent. Otherwise, I do not really mind it for the time being. I am using this rom till the time a Kitkat OTA for E980 is released. Once that is there, I will flash that stock rom.
Hope this post helps someone
Click to expand...
Click to collapse
here is the guide to restore 32gb back
1. install kdz kk (e988) on e980....
2. root and install cwn 6.0.4.4
3. reboot into recovery
4. take a backup on ur external sd card
5. reboot to download mode... install stock e980 rom (4.1)
6. factory reset and reboot
7. install cwm 6.0.4.4
8. reboot to recovery and restore in advance mode only two things....
9. restore system
10. restore boot
11. factory format, wipe cache and dalvik
12. restart
you will have kitkat rom installed (e988) on e980 with 32gb internal storage.....
ENJOY...............
I seen in http://lgviet.com/forum/threads/up-rom-kitkat-stock-cua-e988-hongkong-len-may-e980-at-t.18912/
Tranks @chochweet
Related
I've been browsing the forums for a couple of months. Read lots of how-to guides but they all give different ways of doing the same thing.
Thought I knew a lot about computers, but feeling like a noob
GT-N7100 (international) running 4.1.1. Rooted using N7100. Backed up all my apks and data using Carbon, the backup app. I assume that if I wipe the device I can restore... so I'm good to go.
Wanted to put on a custom 4.2 rom so I picked Carbon (1.4-2FEB2003). Reviews looked favourable.
Downloaded Rom Manager v5.5.2.3. Clicked "Recovery Setup", rebooted, my Current Recovery is now Clockworkod 6.0.1.9.
Downloaded the rom using goomanager. Rom is sitting in a zip in a directory on my sd card.
Installed Mobile ODIN Lite v3.65 since I wanted to keep the flash count at 0.
Mobile ODIN doesn't see any of the files (they're zip). If I unzip them using an external zipper then I can manual select "Kernel" boot.img, but no idea what files to select for the rest of the options. Ok, so abandoned ODIN.
Back to ROM Manager. Install ROM from SD Card, however that app appears to be bugged since it's not able to show the external sd card, (extSdCard) and just shows internal memory.
Installed ROM Toolbox Lite. Install ROM from SD card. Browsed onto the SD card. Hurrah... picked the rom. ROM Pre-Installation appears, picked Backup Existing ROM, Wipe Data and Cache (shudder), Wipe Dalvik Cache. Ok. Reboot and install. OK. Phone reboots.
Into ClockworkMod.
Screen appears with a falled down droid. Options are: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset/ wipe cache partition, apply update from cache.
No idea what to pick. I'd have expected to get a "install rom from sd card" or some other such option, since "update" sounds like just changing clockworkmod.
Choosing "reboot system now" and the system comes back up as if I hadn't told it to install rom. Apply from external allows me to browse the rom but then I get ann E:signature veritifcation failed.
Hard-reboot. Back into 4.1.1.
I can plug into my computer (mac - so no Odin). While I'd like to keep my trianges away etc for warranty, it's not 100% critical.
How to progress further? Which of the several flashing tools should I use? What noob mistakes am I making?
1st Of all Every time You Flash a Custom Rom or boot into recovery mode ur binary will be increased so its pointless to use Triangle away while you are rooted , But when you decide to make ur device completely stock then use Triangle away and flash a Stock Rom which will unroot ur device and get ota updates back.
Now for flashing custom Roms its simple By Using any custom recovery Clockworkod or TWR.. etc:
1- Turn Off ur device then boot into recovery ( Vol up + Home + Power)
2- Make sure you have downloaded the Rom to your external SD Card
3- Wipe data Factory Reset ( Your External will remain untouched)
4- Wipe Cach
5- Wipe Dalvik cach
6- Finally Install Zip From SD Card an choose install Zip from External Card , Aroma Installer will popup then you can take it from here
Dark.Soul085 said:
1- Turn Off ur device then boot into recovery ( Vol up + Home + Power)
6- Finally Install Zip From SD Card an choose install Zip from External Card , Aroma Installer will popup then you can take it from here
Click to expand...
Click to collapse
Would you expect the Install Zip from SD Card option to appear if I'd skipped steps 2-5. I.e. if I haven't factory wiped yet, would the option not appear? Or should it always be there and there is something else wrong?
Thanks for your help BTW.
ohmegosh said:
Would you expect the Install Zip from SD Card option to appear if I'd skipped steps 2-5. I.e. if I haven't factory wiped yet, would the option not appear? Or should it always be there and there is something else wrong?
Thanks for your help BTW.
Click to expand...
Click to collapse
if u skip steps 2-5 you will face problems in the new rom. even worse the new rom may not boot normally due to leftover system data files n settings of the previous rom.
best way to flash is to reboot to recovery rather than using some softwares.
always make a nandroid in clockwork "backup n restore" option prior to flashing new rom.
souravtarafdar said:
always make a nandroid in clockwork "backup n restore" option prior to flashing new rom.
Click to expand...
Click to collapse
Maybe this is where my confusion is coming from. I'm not seeing a backup option in the clockwork menu. Nor am I seeing a flash rom option, or anything other than the few options.
Those options are: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset/ wipe cache partition, apply update from cache.
That means you haven't flashed cwm recovery.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
That means you haven't flashed cwm recovery.
Click to expand...
Click to collapse
According to ROM Manager on the phone I'm getting told
"Current Recovery: ClockworkMod 6.0.1.9
Latest Recovery: ClockworkMod 6.0.1.9"
I've tried reflashing the recovery a couple of times but it makes no difference.
I've checked clockworkmod.com/rommanager and indeed 6.0.1.9 appears correct.
Is there a different tool I should be using to put the cwm recovery into place?
Again, thanks to everyone so far for your help. This noob wants to not be a noob
In recovery does it say stock recovery ?
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
In recovery does it say stock recovery ?
Click to expand...
Click to collapse
When you say "in recovery" did you mean in the ROM Manager app, or somewhere else? I'll assume you meant when booting in recovery mode.
If I boot into recovery mode (from ROM Manager, click the reboot into recovery, or by power off/on with keys) I get the fallen down droid, and the following:
"Android system recovery <3e>
Volume up/down to move highlight:
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
-------
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : BTU
Successfully applied multi-CSC."
I guess you still have the stock recovery , You should have the option to install a zip from SD Card check the Screenshot
Dark.Soul085 said:
I guess you still have the stock recovery , You should have the option to install a zip from SD Card check the Screenshot
Click to expand...
Click to collapse
Hmm... screenshot definitely doesn't look like that. So what do I need to do to get that recovery installed? ROM Manager doesn't seem to want to do it. I wonder if the way I got root is the problem?
Download the recovery from clockworkmod site and flash it via mobile odin.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Download the recovery from clockworkmod site and flash it via mobile odin.
Click to expand...
Click to collapse
I've downloaded the file (6.0.1.9) and it comes as a .img file. However, by default, mobile odin wouldn't handle it. Searched and found another post that said to rename it to "recovery.img" and... MO found it. Hurrah. Flashed. Hurrah.
It rebooted into it once. All looked good. But on reboot it's gone. I'm a lot further along than this morning so thank you. I'll go play some more!
Rename the following file
/system/recovery-from-boot.p
to
/system/recovery-from-boot.p-bak
With root explorer or something.
Then flash custom recovery again.
Sent from my GT-N7100 using xda app-developers app
Flash it via odin
UtkarshGupta said:
Rename the following file
Click to expand...
Click to collapse
That did it, thanks!
souravtarafdar said:
if u skip steps 2-5 you will face problems in the new rom. even worse the new rom may not boot normally due to leftover system data files n settings of the previous rom.
best way to flash is to reboot to recovery rather than using some softwares.
always make a nandroid in clockwork "backup n restore" option prior to flashing new rom.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2028103
go to second post for installation instruction of philz cwm recovery.......I guess u even dont have root access, so try the odin instructions.
or try the original cwm touch version:::::::::
http://forum.xda-developers.com/showthread.php?p=34315245
-Reboot device to download mode(vol down+home+power at once keep pressed until restarts)
-Open odin and select downloaded file for PDA tab
-Connect device to PC, and wait till device successfully added to com port
-Flash
-Use Triangle away reset flash counter(thanks chainfire).
hope it helped u.:good:
souravtarafdar said:
http://forum.xda-developers.com/showthread.php?t=2028103
go to second post for installation instruction of philz cwm recovery.......I guess u even dont have root access, so try the odin instructions.
or try the original cwm touch version:::::::::
http://forum.xda-developers.com/showthread.php?p=34315245
-Reboot device to download mode(vol down+home+power at once keep pressed until restarts)
-Open odin and select downloaded file for PDA tab
-Connect device to PC, and wait till device successfully added to com port
-Flash
-Use Triangle away reset flash counter(thanks chainfire).
hope it helped u.:good:
Click to expand...
Click to collapse
How can he triangle away if he has a custom recovery?
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
How can he triangle away if he has a custom recovery?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Triangle away ----used to reset flash counter....thAT IS it resets the times u flash something....when u flash recovery ur counter increases...simply open triangle away & reset counter to 00000000000000000000.........so ur doubt cleared
didn't thought u would ask this after seeing ur previous posts
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
Hello all,
I flashed and rooted my SGIII about 6 months back using these threads
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showpost.php?p=47747640&postcount=1
Everything was running fine until Saturday, I noticed my phone kept shutting off in my pocket. Once i got home and started doing diagnostics, i couldn't really tell what caused it, i uninstalled the realtor.com app i had downloaded Saturday during the day just in case and wiped the cache of a bunch of apps I had before the problem started. The problem still exists, the phone will randomly flicker 3 or 4 times, the shutdown menu shows up then goes away, then it turns off and i have to boot it back up manually.
Anyone else had this issue?
It seems as though these threads come pretty frequently here lately, I am going to suggest a power button, it is a fairly common failure. On a good working phone if you push and hold the power button for 10 seconds it will turn the phone off, but not before popping up the power/reset menu.
Good luck hope you get it fixed quickly and perhaps I'm wrong?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Starting to think this is hardware related, i did a complete factory reset and same issue occurred. Now I have to take it back to stock and see if I have a case for a replacement.
Since i updated and rooted as I did, am I screwed?
now it seems to be soft bricked.. this is fun
Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.
audit13 said:
Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.
Click to expand...
Click to collapse
Yea I did, I'm currently searching how to do this process post-4.3 update
update: so i can get into TWRP just fine, cannot reflash 4.3 update, getting an error no MD5 file found, and "assert failed: apply_patch_check ("system/app/Bo.. it cuts off from there.. then says E:Error executing updater binary in zip
if i reboot it just hangs at the ATT logo
what I have done so far was backed up before this brick started, then factory reset, data and all cache, since the factory reset I haven't gotten past the ATT logo.
Not going to sleep tonight until this is solved, I know someone can help me since I can still get into TWRP
Was thinking of trying to ODIN back to 4.1.1 then flash 4.2 then flash 4.3 but I am pretty sure that will hard brick it right?
$5 paypal to whoever fixes this for me!
wellppp think i bricked it
serstylz2 said:
wellppp think i bricked it
Click to expand...
Click to collapse
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
JEdad26 said:
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
Click to expand...
Click to collapse
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something
serstylz2 said:
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something
Click to expand...
Click to collapse
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068
JEdad26 said:
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
Also would have probably worked if I had any life at all from this thing. I think this was destined to break, I believe hardware failed.
It broke when I tried flashing d2att_I747UCUEMJ2_bootloader_modem after flashing boot_CWM_I747UCUEMJB
UPDATE: Able to get back into Download mode, TWRP and it still hangs at the ATT logo. Was able to do that by sticking a debrick dump img on my sd card and doing that method. Now I am trying to fully follow thru with that thread (http://forum.xda-developers.com/showthread.php?t=2549068) but I still have never seen a stock 4.3 that i can flash via ODIN, i asked them where I can find that. I may try these directions in the meantime (Also, I tried to update to TWRP 2.6.3.1 and ODIN froze on the checking .md5 step so, maybe that's the issue to begin with?)
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2a....3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/show...1&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
Welp I'm finally back up.. here's what I had to do
First, had to get a debrick img from http://forum.xda-developers.com/showthread.php?t=2549068&page=3
Then carried out these steps
First:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.
On Windows:
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.
On Linux:
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.
Second:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
booted to Recovery, then basically whipped through these steps
"You will need to copy all of the files you are going to flash (you can download them below) onto your 1GB or larger SD card. You then Need Put your Debrick SD card in the Phone, Remove and reinstall the battery,Put the Phone in Recovery Mode (Must Be Either TWRP or CWM Instructions and TWRP Download Below), Dismount the Debrick SD card, Insert your SD card with your Bootloaders, ROM, kernel, and Modem into the Phone, Mount the SD card, Flash your files one at a time, wipe the cache and dalvik between each file, Once you are done reboot the system, You Might have to put the debrick SD back in and do another battery pull, boot up the phone, after you get in the phone reboot it without the Debrick SD card in. If it will not Boot on its own see the link below."
My original problem came when i removed the debrick SD and inserted the file SD, i wasn't mounting so i was confused for a min. Then the ROM i was trying to flash was the "update43" from the OTA 4.3 update thread, that does not work, ended up using the "almost Stock" from here http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
And I was good after that. Basically I just went a long way to do what the tuts had already said to do, and the screen flickering is also gone along with the random reboots i was getting.
Very thankful for this forum and you all
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
cjkline83 said:
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
Click to expand...
Click to collapse
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
Sent from my SPH-L900 using XDA Premium 4 mobile app
Pending Testing
jlmancuso said:
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Click to expand...
Click to collapse
Yeah, I wiped everything when I got home from work (don't know what I was thinking, really). TWRP even warned me no OS was installed, and I was like "so?". Anyway, as soon as it got stuck on the Samsung Galaxy Note II screen, I started the download of that rom you linked to. Still has 10 minutes left (big file is big). I'll come back with an update once I complete these first set of steps.
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
====================================
ADB Sideload
Since the device is not bootable, and I don't have an adapter to copy to my SD card via a usb reader, I struggled, but got the ADB Sideload function of the Android Development Toolkit to work once I upgrade to Team Win Recovery 2.7.0.0 via ODIN.
sideload log is as follows:
Code:
Updating partition details...
Full SELinux support is present.
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
UnRooted MC2 Stock Restore by blizzard412
Formatting /system and installing..
This will take a while
...Flashing temp special recovery
...Again just in case
Installing Radio...
Flashing firmware...
Flashing garwrnn & -EViL-KoNCEPTz- carrier partition fix...
You will automatically reboot to twrp to finish up...
[COLOR="Red"]E:Unable to mount '/preload'[/COLOR]
Should I be worried about the preload error?
Edit: rebooted but currently in a reboot loop without the startup sound. I'm going to let this go for about 10 minutes before I try to wipe and re-sideload? Before TouchWin rebooted it asked me if I wanted to install SU-SuperUser for root. Should I not install the root at this time?
Edit 2 THANK YOU!
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin.
Click to expand...
Click to collapse
I could not get this to flash via ODIN. The stock recovery kept loading instead
Decided to just try and move down the list.
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Click to expand...
Click to collapse
Phone is now out of reboot loop once I cleared the data and cache. Text messages immediately came in after OTA activation and PRL update. I am now running stock rooted 4.1.2 without KNOX.
Reboot into recovery
Flash your 4.4 rom
Click to expand...
Click to collapse
Might wait on that for a minute. So thankful to at least have a working device again. Thanks for your help. Would you like the bounty? Please PM me a paypal address or your preferred methods.
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Systems nominal
jlmancuso said:
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I had a rooted stock rom, replied to my texts from the day, then loaded rom manager, installed clockwork recovery. downloaded omni directly to the phone from their website, rebooted into clockwork, flashed, and things were fine. Booted into rooted kitkat 4.4.2, and now I'm flashin the gapps update to enable google services. network and wifi working fine under omni.
Can't thank you enough for helping me out of that hole from earlier.
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I flashed SuperSU in CWM and fixed that. Things are running great. Just need to see what the battery life is like now on a new rom.
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
TrippyAzN said:
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
Click to expand...
Click to collapse
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Larry2999 said:
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Click to expand...
Click to collapse
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
TrippyAzN said:
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
Click to expand...
Click to collapse
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Larry2999 said:
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Click to expand...
Click to collapse
Just did that, still at the boot screen
TrippyAzN said:
Just did that, still at the boot screen
Click to expand...
Click to collapse
Sometimes, it may take several minutes after the reset for your phone to finally boot up so you may have to wait a bit before deciding it didn't work. However, do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Larry2999 said:
Do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Click to expand...
Click to collapse
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
TrippyAzN said:
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
Click to expand...
Click to collapse
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Larry2999 said:
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Click to expand...
Click to collapse
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
TrippyAzN said:
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
Click to expand...
Click to collapse
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Larry2999 said:
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Click to expand...
Click to collapse
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
TrippyAzN said:
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
Click to expand...
Click to collapse
Glad to know your phone is now functioning normally. One of your earlier restore operations probably restored your data whilst the new ROM you flashed restored the system without deleting data. Thankfully, you didn't lose anything. Now the phone is back to normal, please be careful with flashing ROMs especially custom ones.