Flashify fails to properly flash TWRP img files for my LG G2 D801 30c (T-Mobile). Any subsequent boot to recovery results in a "Demigod crash handler" screen being shown. The stock LG recovery seems destroyed. There were no errors or warnings prior to the start of flashing nor after its completion.
To further rub salt into the wound the author of Flashify has the gumption to ask for $ to remove the app's daily limit of 3 flashes. So recovery is held hostage for a day.
Guess I should be thankful that only recovery is trashed. At least the phone isn't bricked.
UPDATE: A day later I was able to flash the stock LG recovery. It has to be accessed via the "No Command" droid (which means there's still something wrong), but at least there's a way back to the original recovery. Of course knowing that doesn't help when it comes to installing TWRP.
Related
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.
Hey, I just received my new AT&T LG G2 in the mail and having flashed my phone and other peoples phones in the past, proceeded to do so. Unfortunately at every step in a guide there's been some unforeseen hurdle, I'll list my current software values and what I've tried below. I've tried as many methods as I've found, yielding less than desired results.
[Software]
Running 4.4.2 stock, version D80020y
[How I rooted]
-All of the conventional methods of ADB rooting failed, resulting in an obscure error loosely stating that the signature is invalid.
-I then tried Stump, which others had used in brute force mode to root. This worked, I proceeded to install super su and busybox.
[How I got the initial recovery loaded, and it's not fully working]
-After trying 4 different methods to install a custom recovery, the only method that worked was AutoRec "D800_AutoRec.apk". This installed quite an outdated recovery which is unable to flash a more up-to-date recovery, nor a rom or gapps. But it somehow manages to install a custom kernel.
[Methods I've tried to install a custom recovery]
-Results in blank recovery: http://forum.xda-developers.com/showthread.php?t=2468858
-Asks which recovery and then closes, even when run in a devoted cmd window: http://forum.xda-developers.com/showthread.php?t=2500441
-GooManager/Clockwork Mod app: Claims to have installed a custom recovery, but really doesn't. Ends up booting whatever was previously installed.
-Flasher app: Extracted the "recovery.img" file and flashed it, resulted in some brief LG message up the top left saying something's invalid, and then it boots into a blank recovery screen.
I've never had such a hard phone to root and flash. And I'm at a loss, nothing seems to work as it should.
Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
I was in the process of manually installing CWM Touch via Rashr Flash Tool to replace an old 6.0.1.1 non-touch version i had on it before, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS.
I've tried the following with no success:
Clearing data factory reset
Clearing cache
Clearing Dalvik cache
Full restore to V6 stock
Full restore to Cyanogen (I made a backup when I first got to CWM Touch)
This is the current behavior of my phone:
When powered on, it will display the LG logo, then it will flicker to black and then fade in the LG logo again, 5 seconds later recovery boots. If phone was off and you insert USB cable to charge, the LG logo appears, but the battery mode sort of screen never comes after. Its just stays at the LG logo, and never turns off the display.
It will keep rebooting to recovery no matter if I even tell the recovery to reboot to bootloader.
I don't know exactly how the bootup structure is for androids but the only thing I can think of that may be the issue is the recovery itself if it wasn't the app that caused this. It just doesn't make sense that after a full restore, it would still have an issue, other than the recovery itself, UNLESS there is some secret boot instruction file that's stuck with a "Reboot_to_Recovery = 1" parameter.
Since this thing is stuck in a recovery boot, how would I be able to manually, without OS access, reflash another version of CWM on the device? Or if there's another possible way to fix this, please help me.
Maybe the ROM hasn't flashed on your phone properly .try again with a clean flash. may help
HiT Thank$ If HelPed
I believe this is independent of the ROM. I had noticed in preparing to flash a new ROM that instead of restarting to the OS, it restarted to the recovery. I didn't take much note of this, but it was clear that this problem began when I flashed the new recovery. Also, the fact that I had used 2 seperate, very different restores (full restores) with no success means that it couldn't have been the ROM.
My only probably clue right now is that the recovery is to blame (which is weird since CWM notes 6.0.4.7 as compatible with LG Spectrum. I had 6.0.1.1 before with no issue). I have no idea how to change this recovery however, given that I can't even boot the OS at all, and there doesn't seem to be a "flash recovery' option in recovery (which is kinda annoying).
Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>
N101BL said:
Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>
Click to expand...
Click to collapse
A 504 error is a network error and has nothing to do with your phone or it's backup. http://pcsupport.about.com/od/findbyerrormessage/a/504error.htm You should research these error's or post a question before doing things that end up making the situation worse. At this point you need to restore your backup and don't do anything till you read the tutorials on how to install TWRP (which has it's own built in way to root the device) or read a supersu tutorial on how to root the device after twrp is up and running correctly THEN if you have issues ask your question in the proper thread...you say you are "booting" twrp...booting twrp means it's not installed and you are running the fastboot boot command. If you meant "booting INTO twrp" by using the vol up key while the phone is booting then you should clarify. You should also be verifying your supersu zip file has the proper size/md5sum. If your backup is not valid (or you didn't bother to make one) then go to the stock image thread and download the most recent image for your model and flash that via twrp.
Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
famewolf said:
go to the stock image thread and download the most recent image for your model and flash that via twrp.
Click to expand...
Click to collapse
N101BL said:
Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
Click to expand...
Click to collapse
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".
Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
famewolf said:
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".
Click to expand...
Click to collapse
N101BL said:
Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
Click to expand...
Click to collapse
While your thought is appreciated we currently have all the versions of stock that we need for the 6045i. The next time start by flashing twrp (not just booting it) following the tutorial in the twrp thread step by step...after twrp is installed boot into it and make a full backup for your OWN use before trying to root. I can't emphasize this enough...follow the tutorials..don't just jump out and start running whatevr. Your system was fine when you had the 504 network error...it was also STILL fine when you restored your backup and "continued to get the 504 error". It was after that you went off on a tangent somewhere. If you cause Alcatel enough grief they can check your returns for the presence of modifications such as attempting to root and opt to void your warranty especially after multiple returns.
Hi XDA, after searching over countless threads and not being able to find the answer i'm after here goes my first post, so the problem originated when I accidentally signed out of Snapchat and wasn't able to sign back in due to safetynet so I went about trying to unroot and reroot using Magisk, however when installing the Magisk.zip, I ran into "Error 1" which I fixed by flashing a stock boot image with "fastboot flash boot boot.img", finally the zip file "successfully" installed via TWRP but upon trying to boot my phone to OS it constantly just goes back to fastboot mode and refuses to boot properly, I still have access to TWRP and have tried flashing back to stock recovery as well to no avail. What i'm wondering is if I somehow flashed the boot improperly and that's causing it to not boot to OS and if not what else can I do to restore my phone to working order, at this point i'm not that fussed over having root access but need to know how I can fix this, I have also tried flashing a stock ROM from stock recovery but just after starting the install it and the loading bar going up slightly it stops and goes back to the file selection page. Please help!
Edit: I have flashed the boot.img again using a newer stock image and now when I attempt to boot normally I get taken to a black screen with a white LED