Develop Bugs

[GUIDE]How to unbrick your Defy and solve other bugs

So your Defy is bricked. It's really hard to brick a Defy or a Defy+ due to locked bootloader, so you can't really brick it but you can get it in state of not booting. In this simple guide i will show you how to unbrick Defy and fix some common errors!
Lets get started!
How to unbrick your Defy
What do you need!
You need the following:
Motorola Defy
RSD Lite (download here: http://goo.gl/KRSRp
SBF (i reccomend 2.2 CEE Froyo) (download here: http://goo.gl/Jhz84) (for other SBFs use this link: http://goo.gl/dYQTl )
USB Cable
Charged battery (at least 50%)
Motorola USB Drivers (download here: http://goo.gl/bWg1M )
Download and install USB Drivers
Download and install RSD Lite
Turn off your phone
Go into bootloader by pressing Power button and Vol+ button
Connect your phone to your PC via USB cable
Make sure everything is OK
Locate downloaded SBF. In popup dialog press Uncompress and start flashing
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
That's it, you unbricked your Defy!
How to repair damaged Dalvik or cache
Use the same method for unbricking your Defy. If you still have problems...do the same procedure again.
How to fix empty battery
If your battery is so empty that you can't even charge it, there are 2 options
Option 1. (McGyver method)
Get a USB cable, cut the off the B plug (the one that plugs into the device) and strip away the shielding, revealing the 4 individual wires inside: White, Green, Red and Black. Red is +5V DC and Black is ground. strip a few (1-2) mm's off each and gently push them into the + and - slots on the battery. Apply some tape to keep them in place, but don't cover the other connectors. Now plug the battery back in, a tight fit, but possible if you've peeled back the shielding and the white and green wires so that only Black and Red are actually being crammed in there with the battery
It should look like this:
{
"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"
}
Red goes to the + terminal,Black goes to the - terminal
Plug the business end of the newly modded usb cable into your computer.
That's it, your Defy should be alive now
McGyver method found at this thread:http://forum.xda-developers.com/showthread.php?t=892026
I was lazy to write the method by my words...so i just copied from that thread....because he wrote it so well
If original author has problems with copyrights, he can PM me and we will sort it out.
Option 2.
Connect Defy to PC via USB cable. Make sure that your PC is powered on. LED in the top left-hand corner should be white coloured. Leave the Defy overnight to charge. In the morning it should be charged a little bit to charge it via normal method
I have not tested McGyver method, but option 2 worked for me (happened to me once)
This is the end of this tutorial. I hope i helped!
Froyo nandroid backup here
Guys I created a prerooted and with cwm installed froyo nandroid backup. Make full restore
Link: http://d-h.st/RxH
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE DURING THE PROCESS I AM NOT RESPONSIBLE!

is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.

prax31 said:
is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.
Click to expand...
Click to collapse
Well try it...you can always go back by flashing another SBF
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE , I AM NOT RESPONSIBLE!

bricked/not booting defy
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(

melowed said:
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(
Click to expand...
Click to collapse
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!

bricked/not booting defy
ppero196 said:
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
tried that, still not working

melowed said:
tried that, still not working
Click to expand...
Click to collapse
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!

bricked/not booting defy
ppero196 said:
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
i can get it to go to boot menu but it wont connect to rsd lite for me to flash another sbf. is there some other way im not aware of?

I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!

bricked/not booting defy
ppero196 said:
I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!

i need help asap
melowed said:
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!
Click to expand...
Click to collapse
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?

drakefrancis said:
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?
Click to expand...
Click to collapse
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app

ppero196 said:
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Hey ppero, Thanks for the guide.
Some random Chinese build finally worked for my phone, phone was bough used: http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143

Froyo nandroid backup
Extract in the root of SD card and restore using cwm
Make full restore
http://d-h.st/RxH
Sent from my iPhone 5 using Tapatalk 2

bricked MB526 BL7 no recovery available
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance

butcherr said:
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance
Click to expand...
Click to collapse
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere

ppero196 said:
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere
Click to expand...
Click to collapse
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?

butcherr said:
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?
Click to expand...
Click to collapse
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.

_ossie_ said:
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.
Click to expand...
Click to collapse
Thank you VERY much. I spent too much time with CWM it appears. I dont remember having used the stock recovery once. I thought BL7 was my enemy with that screen. My phone must feel like its been gangbangraped now with all the different ROMS I have flash upon it. Thanks again, quarx build 20121018+v4 running. Am creating a backup right now.

When I connect to pc (battery empty) it charges white led then boots up hangs on motorola logo for sometime then shutsdown to white led again, is that normal?

My Xperia Arc wont boot up, need help!!!!

Hey, I'm new here. I have a Sony ericsson arc that is rooted and unlocked bootloader. I downloaded a room that I installed via recorvery mode. I did just like how it was done, but I think something went wrong.
I turned on my cell phone after the installation but the phone will not turn on. The only thing that shows up is the Sony Ericcson logo. The mobile phone will not charge, and when I insert the USB cable that comes up the logo. If not turned off the phone unless I take out the battery. I do not know what to do.
I think I have to flash the firmware oginale, but do not know where I can find it and I'm really not sure. Appreciate all the comments that will help me and my Xperia arc. Sorry for my bad english!

Do you know the name of the rom?
It might be helpful to myself and other users if you tell us the name of the rom, if it was a "CM7" "CM9" or "CM10" rom, you will need to flash a different kernel for it to boot. There are also other methods of fixing it, such as flashing an ftf in flashtool, or a different rom.
First, tell us the name of the rom, and I will try to help more from there
Hope I can help!
- Jack

Actully, i tried to install this http://forum.xda-developers.com/showthread.php?t=1657848 !!

Your problem is probably your kernel, you may have tried to use an ICS ROM with a GingerBread Kernel
Do a search on "ArcKnight Kernel" I recommend it
I'll help you some more when I get on my computer tomorrow if you need it
-Jack
Sent from my LT18i using xda premium

JackJoeR said:
Your problem is probably your kernel, you may have tried to use an ICS ROM with a GingerBread Kernel
Do a search on "ArcKnight Kernel" I recommend it
I'll help you some more when I get on my computer tomorrow if you need it
-Jack
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
Thanks, I will do a search! I will need your help, just leave a reply tomorrow when you hit your computer!
Thanks again, I appreciate it!!!!!
-Bitonii

I tried searching the ArcKnight Kernel but can not find where my problem can be solved by ArcKnight Kernel .. + I will not do anything stupid, because I'm not too familiar with rooms, kernel, etc..
I would rather wait for a response from you in the morning, and still looking for solution ..
Thanks.
-Bitonii

Bitonii said:
I tried searching the ArcKnight Kernel but can not find where my problem can be solved by ArcKnight Kernel .. + I will not do anything stupid, because I'm not too familiar with rooms, kernel, etc..
I would rather wait for a response from you in the morning, and still looking for solution ..
Thanks.
-Bitonii
Click to expand...
Click to collapse
HI,
You have to flash the Arcknight or stock(ICS 4.0.4) kernel first using flashtool (trhough fastboot==>install kernel), after that you can install your chosed Room like that one in your post, because you may made mistake installing the Room with a wrong Kernel, it's happened to most of pepeole, like me

How to flash a kernel
What kupuku says is correct
HOW TO FLASH A KERNEL
STEP 1 - Picking a kernel:
Download the kernel you want to use, as I said, I recommend "ArcKnight" you can download this here:
http://forum.xda-developers.com/showpost.php?p=24807655&postcount=2
The files you need to get are
Main Kernel OverClocked CPU - ArcKnight Kernel_RC_3.5.1_OC_TEST
Click to expand...
Click to collapse
and
Wifi and Zram Modules for Kernel - ArcKnight_Kernel_RC_3.5.1_Wifi_Module
Click to expand...
Click to collapse
STEP 2 - A program that will help:
I find the easiest way to flash a new kernel is to use this program called QuikIMG
Which you can download here:
http://forum.xda-developers.com/showpost.php?p=23714241&postcount=1
STEP 3 - How to setup QuikIMG:
So you have the file "ArcKnight_RC3.5.1_OC.img"
and you have "QuikIMG" EXTRACTED
1)Go to the folder where you extracted QuikIMG to and open the folder called "images":
{
"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"
}
2) Drag the file "ArcKnight_RC3.5.1_OC.img" into the folder called images - so it looks like this:
3) Go back to the QuikIMG folder and open up QuikIMG and select "ArcKnight_RC3.5.1_OC.img"
4) You will then need to connect your phone in "Fastboot mode"
To do this you need to:
1) Connect your usb to the computer but NOT the phone
2) Turn your phone off
3) Hold down the menu button (the one on the right at the bottom)
4) Connect your usb cable to the phone
5) There should be a blue light on the side of your phone, this is when you know it is connected and QuikIMG should look like this:
5) If QuikIMG says "Connected" all that is left to do is to press "Flash" and then remove the cable and turn your phone on
EXTRA:
If your WiFi does not work when you turn your phone on, you will need to flash the zip file "ArcKnight_RC3.5.1_Test_Version_Modules.zip"
You do this by putting the "ArcKnight_RC3.5.1_Test_Version_Modules.zip" on your SD card and using recovery to flash it
Hope this helps somehow! any other questions on anything, let me know!
- Jack

Good evening!
I did like you said, but but the flashing failed because it says that my phone is not rooted!
Im pretty sure that my phone was rooted, i used Titanium backup, superuser.. I could use apps which requied rooted phone!
Thanks for any kind of solusion!
-Bitonii

Did QuikIMG display your phone as "Connected" ?

JackJoeR said:
Did QuikIMG display your phone as "Connected" ?
Click to expand...
Click to collapse
Yes, it says that its connected! Shold the partition of flash be on ''boot''? becase it is on boot.

Yes it should be on boot, don't ever change that
Are you sure your bootloader is unlocked?
What does QuikIMG say, can you copy and paste the text?
Also try different usb ports and restarting your computer
Sent from my LT18i using xda premium

JackJoeR said:
Yes it should be on boot, don't ever change that
Are you sure your bootloader is unlocked?
What does QuikIMG say, can you copy and paste the text?
Also try different usb ports and restarting your computer
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
Im not sure if my phone is unlocked bootloader, but i THINK it is..
QuickIMG says:
Flashing, please wait...
sending 'boot' (5606 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Done. Please check log for errors.
I dont have any other USB ports, but i will try to restart my computer.. It has been on in like over 24 hours xD
I tried flashing after restaring my computer, but didn't make any changes.. same problem

That is an error that occurs from not having an unlocked bootloader
If you want to unlock your bootloader then there are a few ways you can do it
I personally used these instructions
unlockbootloader.sonymobile.com/instructions
But there are other ways to, but it is your decision on if you unlock it and how you unlock it
I personally recommend you do unlock it however to get full access to all ROMs for the Arc S

JackJoeR said:
That is an error that occurs from not having an unlocked bootloader
If you want to unlock your bootloader then there are a few ways you can do it
I personally used these instructions
unlockbootloader.sonymobile.com/instructions
But there are other ways to, but it is your decision on if you unlock it and how you unlock it
I personally recommend you do unlock it however to get full access to all ROMs for the Arc S
Click to expand...
Click to collapse
ahaa, but how can i use this method (http://unlockbootloader.sonymobile.com/instructions) to unlock bootloader when i even cant turn my phone on.. There must be another ways.
-Bitonii

Finally made it
yes! I managed to fix the problem in the end! I downloaded the original firmware to Xperia arc (LT15i_4.0.2.A.0.62_Generic Global World.ftf) and flashed it using the program flash tool 9 The phone is now my life again, and that's all I care about!
Of course, I lost all my apps, contact and everything but the phone will survive and that is what I care most about!
I appreciate all the answers that have come to help me, and I hope people who have the same problem with help from this post.
A big thanks to Jack who has used his time to help me and others who are in the same situation I was in. Thank you, everyone!
-Bitonii

That was the final thing I was gonna try haha, glad you got it working and it's not a bother, glad I could offer some help
-Jack
Sent from my LT18i using xda premium

same prob here My Xperia Arc wont boot up, need help!!!!
JackJoeR said:
Did QuikIMG display your phone as "Connected" ?
Click to expand...
Click to collapse
QuikIMG display your phone as "Connected"
and my phone start up with the arcKnight logo and then nothing happend just the logo

JackJoeR said:
Did QuikIMG display your phone as "Connected" ?
Click to expand...
Click to collapse
no

Automatic Restart Problem

Hello. I was using my phone and suddenly in the afternoon it started to restart automatically.. its never ending and it only stops when I take out the battery... When I put the battery again SAMSUNG Logo comes up followed by Samsung Galaxy W (CyanogenMod 9) screen then it restarts again and back to SAMSUNG logo... this process is never ending...
I also plugged in the charger and all i see is battery meter trying to calibrate but phone restarts and again i get to see the un-calibrated battery meter... this process also never ending...
I'm using ''CyanogenMod 9 Final Release (EOL)'' for past 3 weeks and there wasn't any problem... all this happened all of a sudden... I don't know what to do... So experts kindly help me out... Thanks a lot!!

hiitsme123 said:
Hello. I was using my phone and suddenly in the afternoon it started to restart automatically.. its never ending and it only stops when I take out the battery... When I put the battery again SAMSUNG Logo comes up followed by Samsung Galaxy W (CyanogenMod 9) screen then it restarts again and back to SAMSUNG logo... this process is never ending...
I also plugged in the charger and all i see is battery meter trying to calibrate but phone restarts and again i get to see the un-calibrated battery meter... this process also never ending...
I'm using ''CyanogenMod 9 Final Release (EOL)'' for past 3 weeks and there wasn't any problem... all this happened all of a sudden... I don't know what to do... So experts kindly help me out... Thanks a lot!!
Click to expand...
Click to collapse
I'm not an expert, but i would like to help Try to enter cwm recovery, reflash the rom and gapps. Hope it works

reply
thank you so much for your quick response... the problem is i cannot enter into CWM... i just googled and found the problem to be a SOft Brick/ Boot Loop issue... I hope someone has a solution for it...
geniusboy93 said:
I'm not an expert, but i would like to help Try to enter cwm recovery, reflash the rom and gapps. Hope it works
Click to expand...
Click to collapse

U have to flash stock rom via odin and start everything again
Sent from my GT-I8150 using xda premium

1) a bootloop won't stop you from getting into cwm.
2) cwm will usually stop a bootloop.
Something else is going on here. The symptoms you describe *could* indicate a damaged power button.
With a normally working W, if you press and hold the power button for long enough, the phone will switch off. If you continue to hold the power button, the phone will come back on....and then switch off again.....in a continual loop.....
It *could* be that the power button has failed by *maybe* being pressed into the phone (it can happen)...this would replicate the above scenario....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

regarding odin
yeah im trying to flash everything again through odin... but the problem is when i go into the download mode the phone restarts... i dont know how to flash the file if it keeps on restarting like this... can u help me on that?
gameboy20131 said:
U have to flash stock rom via odin and start everything again
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse

regarding power button
i dont think so it is because of the power button...
you see the exact problem which i face on this video... http://www.youtube.com/watch?v=iWg0LifdXlQ
the sad thing is even the uploader hasnt found a solution yet...
let me know if you know anything... as i dont want to buy a new phone
keithross39 said:
1) a bootloop won't stop you from getting into cwm.
2) cwm will usually stop a bootloop.
Something else is going on here. The symptoms you describe *could* indicate a damaged power button.
With a normally working W, if you press and hold the power button for long enough, the phone will switch off. If you continue to hold the power button, the phone will come back on....and then switch off again.....in a continual loop.....
It *could* be that the power button has failed by *maybe* being pressed into the phone (it can happen)...this would replicate the above scenario....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse

i had this problem recently , i did a cmw sd phone partition and kinda bricked my phone , samsung logo restarts rapidly
so at the time u can do 2 things
flash the galaxy via odin , if that didn't work then there is no other ways to fix it
or go to samsung and play dum cuz i went to samsung and replaced the motherboard under warranty , like a fresh phone!
Cheers..

Ok.....so watched that video....in his case, it ain't software related.....if it was, the phone would restart at the same point every time. You notice that the phone would restart after the galaxy w logo screen but when he started hitting the phone it fully booted. That's defo hardware related. I'm not suggesting you mistreat your phone the way he did, but if you did, I bet you'd notice a certain lack of regularity as to where the boot process fails.
My money's still on hardware as the cause of your phones problem.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

regarding odin
can you tell me how you fixed it using odin? because when i put my phone into download mode, the phone restart keeps continuing... all the youtube tutorials and posts say that you got to start off with download mode and then proceed... i can go to download mode for just like 5 seconds and my mobile restarts again....
help me!!
redshift9 said:
i had this problem recently , i did a cmw sd phone partition and kinda bricked my phone , samsung logo restarts rapidly
so at the time u can do 2 things
flash the galaxy via odin , if that didn't work then there is no other ways to fix it
or go to samsung and play dum cuz i went to samsung and replaced the motherboard under warranty , like a fresh phone!
Cheers..
Click to expand...
Click to collapse

regarding rebooting
it is definitely restarting at the same time for me... i just pasted the link just get an idea of it... when i see SAMSUNG logo and SAMSUNG Samsung Galaxy W screen it restarts at that point... as shown in the video i tried doing that and the phone proceeded to load till i stopped hitting it... but once it restarted it went back to the same rebooting sequence...
keithross39 said:
Ok.....so watched that video....in his case, it ain't software related.....if it was, the phone would restart at the same point every time. You notice that the phone would restart after the galaxy w logo screen but when he started hitting the phone it fully booted. That's defo hardware related. I'm not suggesting you mistreat your phone the way he did, but if you did, I bet you'd notice a certain lack of regularity as to where the boot process fails.
My money's still on hardware as the cause of your phones problem.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse

Ok...going back to OS basics to try to explain this.....
As I'm sure you know, an operating system will load up files in a specific and pre defined order. The ONLY thing that will stop this process is an interruption of the power or a corrupted file that the OS is trying to load. The phone in the video is NOT suffering from a bootloop due to a corrupted file......hitting the phone will not suddenly make that file ok and allow the phone to fully boot. If there was a corrupted file, the boot process would fail at EXACTLY the SAME point EVERY time.....regardless of what was done to the phone.
You say you've managed to reproduce the results in the video and get your phone to boot past the startup screen?.......that being the case, it's NOT software related....simply because the boot process doesn't fail at the same point and gets further in.
You say you can't access recovery or download mode because the phone restarts......this is another indication that the OS has nothing to do with it as during these tasks, the OS isn't even being used.
EVERYTHING I've seen and read here is telling me that it's a hardware issue....specifically the power button......wouldn't hurt to get it checked
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

regarding rebooting
thank you for your reply... now it makes sense...
and what do you mean by get it checked? my phone is rooted and its using Cyanogen Mod 9 custom rom and its more than a year old (Out of Warranty period) So if I contact Samsung service center will they help me out? I mean with all the rooted stuff?
keithross39 said:
Ok...going back to OS basics to try to explain this.....
As I'm sure you know, an operating system will load up files in a specific and pre defined order. The ONLY thing that will stop this process is an interruption of the power or a corrupted file that the OS is trying to load. The phone in the video is NOT suffering from a bootloop due to a corrupted file......hitting the phone will not suddenly make that file ok and allow the phone to fully boot. If there was a corrupted file, the boot process would fail at EXACTLY the SAME point EVERY time.....regardless of what was done to the phone.
You say you've managed to reproduce the results in the video and get your phone to boot past the startup screen?.......that being the case, it's NOT software related....simply because the boot process doesn't fail at the same point and gets further in.
You say you can't access recovery or download mode because the phone restarts......this is another indication that the OS has nothing to do with it as during these tasks, the OS isn't even being used.
EVERYTHING I've seen and read here is telling me that it's a hardware issue....specifically the power button......wouldn't hurt to get it checked
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse

If the phone is out of warranty, it shouldn't matter that you've rooted and gone custom as they'll charge you anyway....just got to tell them that you want to stay custom or they're likely to return you to stock and unroot the phone (and charge you for that too).......
You could always try an unauthorized repair shop and see what they say.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
{
"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"
}
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

Power Button
Thank you for that quick search... i dont know what to do... i badly wish the mobile is stable in download mode so that i can flash the rom into it
keithross39 said:
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
View attachment 2132195
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse

regarding odin
Just one more thing...
1.Can you tell me how to approach this problem if it is totally related to software? I mean like there is a mobile phone which is stuck with boot-loop and I want the mobile to snap out of it?
2. Kind of a general question... if the phone restarts even in download mode how to use ODIN? Because then the process might fail... any other way to flash?
keithross39 said:
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
View attachment 2132195
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse

To answer both of your questions together....if it is software related and odin can't be used because download mode can't be relied on.....jtagging is the only option.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

jtagging
is there any forum which gives info about the jtag? because i couldnt find much info about it...
P.S. I just want to make sure to try out all options before taking it to service center... thanks
keithross39 said:
To answer both of your questions together....if it is software related and odin can't be used because download mode can't be relied on.....jtagging is the only option.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse

In my opinion, I don't think jtagging will help in this case. I'm 99.999% certain that it's hardware related. Even if you did jtag, I still reckon you will have a phone that continually restarts. All you'd be doing is replacing one functioning OS with another. Jtag is primarily used for a phone that will not boot at all......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

[Discontinued]

Download the LG Mobile Launcher:
http://www21.zippyshare.com/v/80474003/file.html
Download an install the LG mobile driver:
http://www30.zippyshare.com/v/13539744/file.html
Note your phone model & serial number - it is located here:
{
"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"
}
Now boot your phone into download mode:
Put your Optimus G Pro into download mode by switching it off, holding both the up and down volume buttons at the same time and insert the usb cable into the phone; wait for the drivers to finish loading if doing it for the first time.
Click to expand...
Click to collapse
Start the LG Launcher and click on Options -> Upgrade Recovery
enter your phone model & serial number:
Click on OK - It should now download the firmware (about 2gb) and flash it - this may take some time.
After that you should do a factory reset or you will stuck in a bootloop:
1. Turn the phone off.
2. Press and hold Volume Down Key + Power/Lock Key at the same time.
3. Release the keys when the FACTORY HARD RESET screen appears.
4. Read the warning and press the Power/ Lock Key to confirm. Press any other key to cancel.
5. Press the Power/Lock Key to confirm once more or press any other key to cancel.
6. Your device will perform a hard reset.
Click to expand...
Click to collapse

bootloader
Will this method work if your on custom ROM and bootloader is unlocked?

n0rthstar88 said:
Will this method work if your on custom ROM and bootloader is unlocked?
Click to expand...
Click to collapse
Yes, and your bootloader will be relock, your phone will be unroot.

low battery wront
Wootever said:
Download the LG Mobile Launcher:
http://www21.zippyshare.com/v/80474003/file.html
Download an install the LG mobile driver:
http://www30.zippyshare.com/v/13539744/file.html
Note your phone model & serial number - it is located here:
Now boot your phone into download mode:
Start the LG Launcher and click on Options -> Upgrade Recovery
enter your phone model & serial number:
Click on OK - It should now download the firmware (about 2gb) and flash it - this may take some time.
After that you should do a factory reset or you will stuck in a bootloop:
Click to expand...
Click to collapse
Hi , I am trying but always I get low battery wront.. but the battery is full charged. Can you help me? My phone is f240k but the model info is E988AT. I am using win 7 64bit.
thanks in advance

Will this restore an IMEI number after a botched unlocking?
(The IMEI is good, legit, and mine--I messed up a step in FreeGee and now it reports as 0.)

nothing works always abort because battery not full, although battery is fully charged

lg-user45 said:
nothing works always abort because battery not full, although battery is fully charged
Click to expand...
Click to collapse
seem... my OGP HAVEING TROUBLE SAME LIKE YOU, any solution??

lg-user45 said:
nothing works always abort because battery not full, although battery is fully charged
Click to expand...
Click to collapse
kuwir said:
seem... my OGP HAVEING TROUBLE SAME LIKE YOU, any solution??
Click to expand...
Click to collapse
I am getting the same error. Anybody know how to bypass the warning?

uppon2 said:
I am getting the same error. Anybody know how to bypass the warning?
Click to expand...
Click to collapse
any solutions to the problem guys? or still the same?

tillicollide said:
any solutions to the problem guys? or still the same?
Click to expand...
Click to collapse
Still the same.

So - this doesn't work.
uppon2 said:
Still the same.
Click to expand...
Click to collapse
The LGMLauncher can't find the internet. yes, it was run as administrator (?)
Too bad.

MDMTahiti said:
The LGMLauncher can't find the internet. yes, it was run as administrator (?)
Too bad.
Click to expand...
Click to collapse
I have never seen that error unless they had server maintenance. You might want to reinstall and try again mate

RecoverY?
Hi..
Just wonder if I'm using CWM recovery.. will this method work and the recovery image back to stock as well? Thanks!

MDMTahiti said:
The LGMLauncher can't find the internet. yes, it was run as administrator (?)
Too bad.
Click to expand...
Click to collapse
herroyuy said:
Hi..
Just wonder if I'm using CWM recovery.. will this method work and the recovery image back to stock as well? Thanks!
Click to expand...
Click to collapse
This is the one I have used the last 5 times under a variety of messed up situations and it always works. READ AND FOLLOW ALL INSTRUCTIONS AND TAKE YOUR TIME. It seems like a lot to do but it is not that bad after the first time you have all the files. Make a "Phone" folder on your computer and put all the files in there and keep everything nice and tidy. Follow the instructions and it will fix just about everything.
http://forum.xda-developers.com/showthread.php?t=2302660
P.S. When you get everything downloaded and unzipped..and you start flash tools with a # you found on the internet..maybe something like 39B0-IH19-4UAO-G6T8. you have checked manual mode on flash tools and put in the file locations in the top two slots, and you finally hit the yellow arrow at the top left....it will say "waiting" for about a minute. THIS IS NOT waiting on you to plug phone in!! You plug phone in when it says ready and that window with "waiting" goes away. Do not unplug the phone either just because it reboots. You need to wait until the bar turns blue and it says complete. This happens around 522 seconds or after.

this just saved my phone from being stuck on recovery! thanks!

I wonder if anyone has solved the battery issue with this method ????
Many users report that while using this method all goes well till around 45% complete and they get a message "Can not continue due to low battery level, please charge phone fully and try again".
This despite the phone being fully charged.
A very common problem it seems.
LL13-

Couldn't do it with this method.
Sent from my LG-E980 using XDA Premium 4 mobile app

lg-e980
stulzerl said:
Couldn't do it with this method.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
me neither i have tried evry methos just cant find a kdz file have tot file and dll file??? any help

wanted warranty back!! plz help
Is this method resets the binary counter on my device?? And do i get my warranty back! plz help.
the reason behind doing so is...
1. When i was on stock unrooted new phone all seemed good.. but after 3 months when i open gallery app half of the imaged is gone. i have to again tap on screen to get back the full image. half upper screen gets randomly colored including the status bar. i thought it was an rom issue. so i rooted and put the custom (g2 apps added) rom. but the problem still continues. so i decided to follow these instructions. but can i get my warranty back? please help!

I am doing this right now and it says it is downloading but I don't see the progress bar
Sent from my GT-P5210 using Tapatalk

Save My Note 4

Would someone mind helping me out, I cant use my phone any more. The last thing I did was install Emotion OS and then I installed the Emotion Kernel, upon reboot the phone was stuck on the emotion boot screen after restarting the phone Im not sure how it happened however the phone went from TWRP to some recovery that looks like the lineageos logo, I cant install any updates from this recovery and my phone via USB in download mode or ADB is not detected by any computer I have tried 3 computers in my house. I have never seen this recovery screen and I do not know what to do. I downloaded a stock MM firmware and converted it to a zip file from a tutorial on here however I keep getting an error message from this recovery. I really need my phone back up and running Im not sure what the heck happened.
Continued from other posts
Quote:
Originally Posted by shadeau
Do you have any options in recovery? Even if you could perform a "factory reset" with lineage OS you'd at least be able to enable ADB and reinstall TWRP. Also, when you say that the phone isn't recognized by the computer does that mean ADB, ODIN, and your OS don't recognize the phone?
So I do have options in this Lineage Recover but I cant get anything to work, Here are my options Reboot System Now, Apply Update, Factory Reset, Advanced. I have already tried factory reset however I may have deleted the OS all together with the Wipe Data Option. When I reboot the phone it stays on the the Samsung Galaxy Note 4 Screen with the little padlock that shows my bootloader is unlocked. I was messing around with flashing betwen several roms, I went from CM 14.1 to Lineage to Emotion OS, I then flashed the emotion kernel. If I select Apply update it gives me these several options, Apply from ADB choose from emulated (no typo) choose from sdcard1. I have tried to sideload via adb shell and my pc ( have tried multiple computers) does not detect the device. I even went to the extent of reinstalling windows and all Samsung USB and ADB drivers. Selecting choose from sdcard1 I can see the various zip files on my sd card however when it goes to install any roms it fails and just says error. There is a error log however it will not let me view these. My phone before this stopped connecting to any pc's I could plug the phone in via usb and it would charge but I would not get any notifications from windows! I will seriously send money to who ever can hlep me out I do not want to shell out for a new phone. Placing the phone in download mode still works however odin will not detect the phone either lol what the heck is going on here. I do have a micro sd card reader for the mc so i can place files on the phones card but I dont know what kind of file this recovery is looking for. I do not know how this recovery even got on here as I have been using TWRP from the very beginning. Please help me
I have never seen this recovery it has the lineage os logo and just says RECOVERY. I wish I could take a picture of the screen.

I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.

ziggsta2 said:
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
Click to expand...
Click to collapse
Are you using the Samsung OEM USB cord?

quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
good questions will try another usb cable all I have is 1 for right now

quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name

ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.

quinciebee said:
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
Click to expand...
Click to collapse
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.

ziggsta2 said:
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
Click to expand...
Click to collapse
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.

quinciebee said:
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
Click to expand...
Click to collapse
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set

ziggsta2 said:
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
Click to expand...
Click to collapse
CHECK THIS OUT People are having the same issues
https://forum.xda-developers.com/android/help/phone-stuck-bootloop-t3510266

{
"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"
}

ziggsta2 said:
Click to expand...
Click to collapse
In the advanced menu is there an option to "mount system" or something? Also see if there's a setting in there for chmod

I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?

ziggsta2 said:
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
Click to expand...
Click to collapse
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.

shadeau said:
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
Click to expand...
Click to collapse
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol

ziggsta2 said:
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
Click to expand...
Click to collapse
Well, good luck! Send me a PM if you have trouble finding the links to unlocking and rooting.

Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop

mojoswagger1980 said:
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
Click to expand...
Click to collapse
Ouch ! I kinda failed to take into account the very real possibility the ROM you wished to flash might not be on your device and you may have no means to get it there.....in which case flash twrp then you need (if you don't want relock bootloader) to flash a system only image . vague I know I'm thinking .....bottom line is whatever you flash cannot contain aboot image or you will relock boot loader. If on 6.0.1 boot loader there is a safeupgrade to the most recent firmware that won't relock if on 5.1.1 (bpa1 ) idk if there is one . I think there is . in fact I'm sure there is hsbrad made Odin flashable IMG for all Verizon note 4 firmware broth dev and retail . look under his profile on XDA should link you to it

ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.

weard1212 said:
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
Click to expand...
Click to collapse
Yeah ty I went ahead and tried last night cause I was bored ....meh lack luster . oh and I did it intentionally and just restored recovery with flashify and I just realized this probably wasn't directed at me but yep lineage