Hey guys. So I got an LG G3 from someone on Craig's list. The device was on 10f so I tried stump root but to my delight it reported it had already been rooted so I just had to download SuperSu. Problem is I'm not sure tha status of it's recovery because there are folders in the phone called CWM and TWRP. I installed TRWP manager and rebooted to recovery from there and it booted into TRWP. So now my issue is I am confused because according to the bump tutorial I have to have some twrp image on the internal storage but I don't see it. I just need to verify what the status of this phone is before I go flashing roms. I don't want to try booting recovery and choosing erase data to test it cuz yea... Any advice?
Related
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
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.
ok im in serious ****!!.I had been using cm13 peacefully ,then i received cm14 update and now i am stuck.First update worked fine ,I used titanium backup .Then I installed the third update then things just went haywire.To mention i had cwm.
1.Phone wont reboot in recovery mode rather cm stock recovery.
2.official downloads wont update/install.
3.no .zip would flash in cm recovery.
4.cmw just vanished,but still rooted.
I Think i should mention on first cm 14 update titanium backup posed problems like root acess denied and SU bimary needs to be updated.I somehow solved it by instaliing new version of titanium backup.
Now i tried all methods to boot in cwm using rom manager and stuff,I finally went to cmrecovery and while browsing clicked WIPE PARTITION CACHE.AND NOW PHONE WONT REBOOT IT JUST HANGS ON MI LOGO .FASTBOOT is opening recovery also phone is charging but wont start HELPP!!!!
hamza12345bohemia said:
ok im in serious ****!!.I had been using cm13 peacefully ,then i received cm14 update and now i am stuck.First update worked fine ,I used titanium backup .Then I installed the third update then things just went haywire.To mention i had cwm.
1.Phone wont reboot in recovery mode rather cm stock recovery.
2.official downloads wont update/install.
3.no .zip would flash in cm recovery.
4.cmw just vanished,but still rooted.
I Think i should mention on first cm 14 update titanium backup posed problems like root acess denied and SU bimary needs to be updated.I somehow solved it by instaliing new version of titanium backup.
Now i tried all methods to boot in cwm using rom manager and stuff,I finally went to cmrecovery and while browsing clicked WIPE PARTITION CACHE.AND NOW PHONE WONT REBOOT IT JUST HANGS ON MI LOGO .FASTBOOT is opening recovery also phone is charging but wont start HELPP!!!!
Click to expand...
Click to collapse
Hello,
Can you access fastboot?
Regards
Vatsal,
Forum Moderator.
Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.
Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.
O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs
Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!
Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.
Hello everyone , so... i decided to root my phone , i made with magisk, then i decided to put twrp on my phone (to recover images and stuff (just in case) but then i already had magisk, and then i installed twrp, and now everytime i turned my phone op, it was loading the twrp recovery mode, so me in an act of dumbness just wipped all my stuff (internal storage included) , and now when i turn my phone the screen is all black and has a blue led! then i fastloaded twrp, made an adb push and instaled twrp recovery again , but now i have no SO i downloaded the rom oneplus6oxygen_22_OTA(...) but it says invalid zip format, please help?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
If you have twrp and can get into fastboot, just adb push the full 5.1.9 rom zip from this thread:
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Make sure you check MD5 after downloading. Then just flash in twrp, flash the twrp installer again, reboot to recovery, and flash magisk.
thanks, both of you, i unrooted my phone, i will root it again, but at least in not a paperweight anymore =D