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.
Related
Can anyone tell me how I flash a recovery to the device from a zip file? Going into CWM and flashing the TWRP recovery initially seems to work, but if I then interrupt the reboot and go straight into recovery, I still see CWM, not TWRP. I'm stuck on the CWM recovery and need TWRP to try to install the Kitkat upgrade.
Should I unzip the components first and then flash the image using fastboot, or is there another way? I'm wary of fastboot as I've already (temporarily) "bricked" the Xoom by flashing a zip instead of an image that way. None of the instructions I've read has much advice on getting round installation problems.
I'm guessing the persistent CWM was caused by my selecting (at an earlier stage) the CWM option to fix the problem of the stock recovery being reinstated at each reboot. Can this be undone? Although I've installed Xoom-Universal-Root, apps that require root access - including GooManager - also fail with an access error. It's hard to tell whether the device is now rooted or not, so if there's any method of getting further without root access, that would be great.
====================
Edit: it looks as if the instructions I saw online, which mentioned two separate TWRP recoveries, were incorrect. To get Android Kitkat 4.4 onto my Xoom I didn't need the initial TWRP recovery, only the BigPart version. Once I skipped to the BigPart recovery, the problem described above did not recur.
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,
I'm trying to install lineage-15.1-20180918 on my new (second hand) Google Pixel (sailfish). It came with Android 7.1.0 (NDE63H, Oct 2016) pre-installed.
No mater what I try to do, after installing Lineage zip file, I always get a warning saying that there is no OS. When I try to reboot to System, I am stuck in a boot loop between a screen saying that I should lock the bootloader and another one displaying the Google logo.
General information about device and softwares used
I run Debian on the PC that is used for the install, adb (v 1:7.0.0+r33-1) and fastboot (v 1:7.0.0+r33-1) are installed.
I got the Lineage zip from there (the shasum is good).
I got the TWRP image from there (v 3.2.3-1).
What I did
I followed the official howto there.
I have unlocked the bootloader, can boot into the TWRP recovery.
TWRP is launched via
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
I did "Format Data", then "Advanced Wipe" (selected everything and wiped).
Then
Code:
adb push lineage-15.1-20180918-nightly-sailfish-signed.zip /sdcard/
(Note that I first tried to sideload both this zip and the suaddon one, given that it didn't seem to work, I wiped everything out again and went with the adb push method)
And, finally, went back to the "Install" menu, selected the zip and launched the install process (without checking the "Verify signature checkbox").
I managed to restore the initial backup created with TWRP, the system booted normally. I then tried a LOS install again and got stuck into a boot loop again.
Problem
At the end of this process, when offered with a swipe gesture to reboot, there is a warning saying that no OS is installed. Swiping to reboot leads to the reboot loop described above.
Any idea on what I can do to fix this issue?
Huge thank you in advance!
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
post-mortem said:
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
Click to expand...
Click to collapse
I did not. But there were other issues as well (I used outdated version of adb and fastboot), I followed the instructions there (due to the stupid rule for new users, I can't post a direct link to it) old.reddit.com/r/LineageOS/comments/9h0aqy/cant_install_lineage15120180918_on_a_google_pixel/e6nbqg6/ and it worked
Good evening /hello/hi,
i own moto one power device (Ram: 4gb, Version: 9.0 pie, MODEL: moto one power, qualcomm snapdragon 626) and i was trying to root my device..
i was successfully able to unlock my bootloader without any error, then i installed and flashed twrp.img(latest version) after flashing twrp i was trying to flash the magisk file which initially landed with a pop up msg (FAILED). After trying it several times i tried to sideload it using adb and was then finally successful and tried to reboot my phone. After rebooting the device i was constantly stuck in the bootloop for almost 20 minutes, i tried rebooting it later but was still in bootloop, so i realized the rom is deleted.
NOTE: The mistake i made was not backing up my device thinking everything will be done fine but i was wrong and landed with this problem.
I also tried to fetch STOCK ROM from forum and flash it, but those zip files was not working. Some say's "invalid zip file" and or "signature not matched".
I also tried to fix the signature error by turning off the option for signature verfication from twrp but still was unable to flash.
i am currently using a custom rom to work with it, but the stock rom was really very good and i would just like to use it.
SO IN THE END I MAKE A HUMBLE REQUEST TO PLEASE, CAN SOMEONE PROVIDE ME THE STOCK ROM SO I CAN FLASH IT CAN START MY PHONE.
Dear oneplus community,
the recent days I wanted to update my stock system and keep my magisk at the same time. But somehow things messed up and lost my root status so I had to go back and flash magisk via twrp again. Since I didn't install twrp as default recovery, I had to boot manually into it.
Here is one of the first issues: the command "fastboot boot recovery.img" had an output line which said that the file is unauthorized. That is quite a common error so I booted into twrp via the all in one tool. Alright here I am in the recovery, ready to install magisk again as usual. Now I am facing the unable to mount vendor, storage and system error, so I fixed it by going to exfat and back to ext4 if I am correct.
Now somehow things messed up even more because at this point I was stuck in a boot loop. I managed to get out of it with the MSM back to stock method.
So in the end I got a stock android 10 oxygenos system I want to have magisk on it again. But when I try to get into the recovery mode sometimes itll work and sometimes it wont. Sometimes the command prompt gives me the unauthorized error message again and sometimes I get stuck in the fastboot mode screen with the oneplus logo.
Eventually I get into the recovery by using various methods e.g. all in one tool, but also here it happenes that the command prompt gives me the unauthorized error.
At this point everything seems to be okay with the installation of magisk (no errors, etc.). But when I'm trying to boot up from the recovery it says that I have no OS installed whether I have magisk installed or not. In a second and third try I additionally tried to flash a rom before installing magisk so I am sure to actually having a OS installed. But it still gives me the same error.
Any ideas how to deal with that, so that I can install magisk on my stock rom properly without having these weird issues.
At this point I'm losing the belief in myself because it shouldn't be that hard at all, since I already rooted my previous phones like mi6 the oneplus 6 haswell..
I will post error codes later.
Thank you.
I actually just started a thread about installing TWRP and magisk yesterday. I am having the same problem installing. I assume it's the versions of each file that I am using that are incompatible, because I am following the instructions as written.
https://forum.xda-developers.com/oneplus-7-pro/help/current-twrp-magisk-unlocked-oneplus-7-t4094307
At this point, since no one seems to know what the problem is, I'm just gonna stay on stock, unlocked bootloader, no root. Which defeats the purpose of even having an unlocked bootloader, but at least I'll have functioning phone. If you need to install an OS on your phone, follow this method.
https://forum.xda-developers.com/oneplus-7-pro/how-to/bricked-oneplus-7-pro-stuck-fastboot-t3972469
This will get you back to factory settings, unlocked bootloader.
+1 here, actually quite confused how to get TWRP properly so it sticks, amd confused about two slots situation.
Now going back to stock via MSM Method. Im in a bootloop/bricked device again.
I'll try to do it one more time and i'll document my steps detailed, so more experienced users can follow the steps better.
Silencex33 said:
Now going back to stock via MSM Method. Im in a bootloop/bricked device again.
I'll try to do it one more time and i'll document my steps detailed, so more experienced users can follow the steps better.
Click to expand...
Click to collapse
Get twrp from here https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943. 3.3.1-79
im about to try this on my tmob oneplus 7 pro, any suggestions as to if I should wait for new updates ?