Database Info

[Completed] Help with reinstalling bootloader

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.

Need directions after 10.0.2 lost root

Hi there guys, as i know You are experts on this stuff i wanted to get your opinions on the steps i should do to get my root back with the least hussle.
device: GM1900
I had successfully rooted the device when it came with 9.5.8 from my linux machine by:
twrp-3.3.1-52-guacamole-unified.img
Magisk-v19.3.zip
Then the OTA 10.0.1 started to pop up, so i grabbed the oxygen updater and downloaded even newer OTA 10.0.2 to my internal storage... Made a TWRP backup and also a Titanium backup first, and then did everything exactly like this guy said:
(url to youtube which i cant post due to being a noob here: yt: watch?v=-x6Xh3uJaKM&t )
but i used different twrp files (downloaded from official twrp app):
twrp-installer-3.3.1-1-guacamoleb.zip
Magisk-v19.3.zip (same as before)
Everything went smooth, my new 10.0.2 booted up only to tell me that Magisk is not installed in Magisk Manager.. Ok the guy had the same problem no biggie - go to recovery flash magisk again he said.
Booting to recovery, TWRP 3.3.1-1 loads i press install and... see no files at all.
So before i do some more stupid steps i wanted to ask You guys how to get my root back on 10.0.2:
Current state:
-10.0.2 boots and works fine but no root
-No Magisk installed in Magisk Manager
-No file to be seen anywhere in recovery in TWRP 3.3.1-1

Everything you need to know.
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559

gvflavio said:
Everything you need to know.
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
Click to expand...
Click to collapse
Thanks mate!! ive already seen this post before, but i didnt exactly know if that would solve my problem... but PROBLEM SOLVED
steps if someone encounters the same problem:
1. Downloaded:
twrp-3.3.1-74-guacamole-unified-Q-mauronofrio.img - to my linux machine
twrp-3.3.1-74-guacamole-unified-installer-mauronofrio.zip - to my phone internal storage
Magisk-v20.1.zip - to my phone internal storage
2. Rebooted phone to bootloader
3. As i had unlocked bootloader already (and my device visible by my linux machine with command fastboot device) i executed:
Code:
fastboot boot twrp-3.3.1-74-guacamole-unified-Q-mauronofrio.img
which made my phone enter TWRP
4. From TWRP i installed aka flashed the 2 files i put on my internal storage earlier in that order: TWRP....zip > Magisk....zip
5. Rebooted to system and had everything working fine!
so the initial problem was caused by the official twrp not working? i kinda get overwhelmed with all that new stuff nowadays

I lost root. This was yesterday going to 10.0.2 ( and was unexpected . . . )
did magisk un-install followed by a magisk install and got back root . . .

Stuck in a bootloop, please help

Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]​
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.

Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?

next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.

NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?

You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....

Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.

[Q] Kind of bricked tablet but works oO : no gapps and restricted by Family Link

Hi,
[first post here]
I just flashed Omnirom 7.1 on a Nexus 10 because it was lagging with Omnirom 6.1 using the TWRP recovery that was present.
[NOTE : I don't think the ROM or the tablet are relevant to my issues]
I made a mistake and tried to flash the nano gapps (instead of pico) and it failed. I thought I'll do that later, wiped cache and rebooted.
It rebooted OK. The system works much better.
Unfortunately, the tablet is supervised by Family Link (and I did not allow my son to get into developper mode).
Now are the issues...
I'm no longer root (as I can not enter any parental code) and I can not enter developer mode (forbidden by Family link), so no USB debugging.
Family Link app crashes (I guess because of gapps is not installed properly).
Recovery got dead in the process (no more TWRP recovery or any recovery).
Bootloader is 'waiting for download' only (download what ?).
I have the official TWRP app and sometimes I can run it without crash but as the user is not root (the system is rooted, though) it seems like a dead end.
I have a Termux app but, again, it does not run as root so I can not edit the system file that would enable me to flash a new recovery...
I tried to activate adb over TCIP on the tablet but it needs 'UDB debugging enabled' oO.
I understand that I made a few mistakes (gapps, not allowing to enter developper mode in Family Link,...)...
If someone has an idea to allow me to flash anything (ROM, TWRP, gapps,...), I'd be quite grateful... as I feel I now have a soft brick...
Thanks,
Z

have you tried flashing a custom rom or a stock rom trough odin?

Thanks for taking the time to answer.
Since my post, I've read that, in bootloader mode, the device does not need to be 'USB debugging enabled' (that's a relief).
With the device in bootloader mode ('Downloading' and no choice other than 'start'), I'm now trying various tools (adb/fastboot/Nexus Root Toolkit, but not Odin yet) to flash something and I suspect that I don't have the correct USB drivers for it. My PC does detect the USB device but the flashing tools don't (yet).
At least, I now have a lead I can follow...
Thanks for your help and sugestion.
I'll report back when I get something interesting...

Hi Again,
I managed to flash TWRP via Odin... Pretty straightforward tool (despite a cryptic interface)... Thanks a lot for suggesting it.
I was then able to get into TWRP (from the boatloader, that proposes other options than just 'start')...
I then flashed the gapps. The tablet rebooted during the flashing (?)...
I'll have another try... There's hope !
Thanks again !

Hi,
I retried flashing gapps thru TWRP and it now works...
Thanks

urgent: oneplus 7 pro TWRP bootloop

I'm very new to everything related to rooting and I think I screwed up, I'm not even sure if this is what a bootloop is.
My device won't boot back into android, I've tried to look for a solution but I don't understand any of the terms those people use.
I followed a tutorial to help me root my phone which I think might have worked but now I can't do anything.
I installed the latest twrp .zip on my phone and elementalX (I think I downloaded it for android 10 instead of 11), I tried a couple of commands in the terminal suggested by other people but none of them did anything.
I really want my phone back, even if that means that it won't be rooted, I made a backup of my data so all that matters to me is that I can use my phone again.
If you know anything that can help me, please try to explain it in a way I might understand as I don't even really know what flashing means.

wattage0 said:
I'm very new to everything related to rooting and I think I screwed up, I'm not even sure if this is what a bootloop is.
My device won't boot back into android, I've tried to look for a solution but I don't understand any of the terms those people use.
I followed a tutorial to help me root my phone which I think might have worked but now I can't do anything.
I installed the latest twrp .zip on my phone and elementalX (I think I downloaded it for android 10 instead of 11), I tried a couple of commands in the terminal suggested by other people but none of them did anything.
I really want my phone back, even if that means that it won't be rooted, I made a backup of my data so all that matters to me is that I can use my phone again.
If you know anything that can help me, please try to explain it in a way I might understand as I don't even really know what flashing means.
Click to expand...
Click to collapse
Can you boot into fastboot then toggle the volume key to recovery , does it go to twrp or something else?

hammered58 said:
Can you boot into fastboot then toggle the volume key to recovery , does it go to twrp or something else?
Click to expand...
Click to collapse
that goes back to twrp

wattage0 said:
that goes back to twrp
Click to expand...
Click to collapse
Good then try the below steps
This sequence has worked for me every time
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage. Or OTG drive,, Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS in both slots