Okay, happy post Vday. :good:
So, Im trying to root an unlocked Blu J1, running Marsh. 6.0.
I recently reset it, due to perf. issues & now trying to root.
My setup is Win7, w/ the latest Usb drivers through Sdk & UniversalAdb. I have Usb debugging active on the phone & the device shows at command level with Adb devices & in Fastboot mode**Ive unlocked the bootloader on the phone itself, & then xferred the Twrp.img files different times.
The twrp files were the latest 2 off the site Twrp.me as of 02/15. Its a successful transfer on fastboot, which is good. but when I go to restart, it shows as stock recovery studio_j1_6.0/user/release-keys but not the touch responsive Twrp. ..
I eventually want to use Su or Magisk zip to gain root. The phone remains bootloader unlocked which is good. I've tried the Adb command, adb root, and then went through these steps, -still nothing. Im on the hunt for recent clockwork mod, to try that way, only ones are like '11 or'12.
So, is the stock recovery hard coded. -it doesnt have 2 separate partit-I ran a partit check just in case. I also went to grab the omnirom androidrecovery 6.0 off Github at github.com/omnirom/android_bootable_recovery/tree/android-6.0, but its .zip. And when I apply updates through Sd card update in stock recovery, I get install aborted across the board on any .zips.. Im on the waiting list for Kingroot to add my device. so thats good.
Either way Android SU shows as not rooted once fully on.
Any feedback greatly appreciated.
Related
Hi, I could use a little help. I've flashed a few roms before, but I really got myself into a tough spot this time. I downloaded Slimrom because the one I flashed before that would slow my device down and generally just didn't run as good as I had hoped. I went into TWRP recovery, wiped the caches, flashed the rom and gapps, but it said that the archive/s were corrupt. I have a few backups, but they are all on an external hard drive. I knew I had to get the Android SDK, Java JDK, New ROM, and use adb if I wanted to fix it, but this is where I've been running into a few problems.
I made sure that the drivers for the phone were installed, I kept getting errors though. I looked at the device manager and it shows the yellow triangle and if I try to troubleshoot it says that there are no compatible drivers for my phone. I looked back at the device manager and noticed it connected with the Media Transfer. I can see the device in adb at the bootloader, but not at the recovery. When I push the rom to the phone from the bootloader using adb push ROM.zip /sdcard/ROM.zip. This fails to copy and says there is no directory. Using adb push ROM.zip /sdcard/ it fails and says it is a directory. I've tried more than this, but I can't seem to get it pushed/sideloaded onto my d800 G2.
Thanks in advance for any help or advice. I apologize if I have been doing it wrong the whole time, it's my first time having to use adb.
UPDATE: I got it into download mode and flashed the stock KK update. Thanks anyways
Hey guys! I'd really love a quick response, as I take my classes over the phone.
Basically, a couple weeks ago I flashed AOKP onto my phone. Of course, I made the rookie mistake of feeling safe and deleted my backup of the Stock ROM.
Now, I wiped my whole system thinking that I'd be able to sideload a ROM over ADB with PhilZ Touch 6, yet ADB can't find my device (even with all the current drivers). Strangely enough, my computer is able to recognize my phone with the ADB driver, and I can still use fastboot commands in the bootloader.
But I have no way of installing another ROM! Doesn't PhilZ Touch include a method of mounting my phone as a USB Storage Device?!
Please, anyone, help! You're my only hope!
TWRP Recovery supports USB storage . Flash it via fastboot
Quick note: I'm very new to all this so I don't really know entirely what's going on.
Alright, basically I'm trying to install the Paranoid Android ROM and I've run into a bit of an issue. I've unlocked the bootloader and flashed the ClockworkMod Recovery. The problem I've ran into is that when I go into the CWM recovery and attempt to do anything with ADB it comes up with "error: device not found"
What am I doing wrong?
Sidenote: ADB can find my phone if it's booted up normally, it's only when I boot to the CWM custom recovery that it can't find it...
I think you are doing it wrong way buddy..
Boot in to Bootloader mode not in CWM Recovery, then try with fastboot and check again..
I did boot into bootloader, then went to CWM and tried to push the ROM using ADB but it wasn't recognising my phone.
Doesn't matter now anyway. I got around it by literally just drag and dropping the zip files onto my phone's internal memory when it was booted up normally and connected to my PC. Then I rebooted into the bootloader, flashed CWM and installed from ZIP. That method was far easier than messing around with ADB etc.
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.
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
[email protected] said:
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
Click to expand...
Click to collapse
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
I formatted, installed factory image, installed TWRP, flashed Magisk, confirmed root, flashed NetHunter ZIP, same result
Droidriven said:
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So if anyone else is facing the same issuing of wanting to install this old(ish) software onto this old(ish) hardware, and got stuck in the same place as me, here are the three steps that I had to take to succeed that were not in official documentation:
1)When flashing the factory Android image, make sure that you are using the newest version that is supported by NetHunter. At time of writing, this is not the same as the newest version of Android.
2)Remove the -w option from the installation script
3)Be sure to install a compatible kernel from builds.nethunter.com
Thanks again to @Droidriven for the tip on using Magisk