I had flashed the fastboot files and upgraded from 3.2 to 4.0 on my Xyboard and gained root access again. I started messing around with the build.prop and ended up in a bootloop. I flashed the fastboot files again and restored the system back to 3.2. Now I cannot gain root access. I have used countless programs, wiped the cache, reflashed to no avail. I tried using ADB to change permissions but it wouldn't let me. I tried unlocking the oem bootloader with nothing. I have spent countless hours researching and need help. Can some tell me how to get back into root?
Sent from my MZ617 using xda app-developers app
Related
Hello,
I am having trouble getting my xoom to boot into the OS. The xoom boots to "reading ODM fuse: 1" and gets stuck. I have been a xoom owner since launch and have unlocked, rooted, flashed roms for a while now and am fairly comfortable with the rooting process. About a week ago I used SBF to return my xoom to its factory default settings so I can pass it on to my daughter. The process completed successfully, however, when the xoom rebooted it got stuck with the following message on the screen.
LTE modem is OFF
Cold-booting Linux
Reading ODM fuse: 1
I no longer get the M logo. I can still access fastboot. I am able to flash recoveries through fastboot however when I reboot the device I get the same message. I tried the following to see if I could resolve the problem but it did not work.
Completed the below steps through fastboot.
Flashed Tiamat's CWM Recovery (Older and newer version)
Flashed TWRP Recovery
Flashed boot.img
Flashed system.img
Erased boot, system, recovery, cache
Flashed boot and recovery after erasing them first.
And for some people who may wonder if I have tried booting directly into recovery, Yes I have. I get the following message when I try to get into recovery and the system freezes.
Entering Android Recovery Mode
Reading ODM fuse: 1
Xoom information:
Original Xoom 3G upgraded to 4G by Motorola
Last flashed ROM was EOS Jelly Bean nightly.
Flashed SBF from Motorolas Developement site and have not been able to boot into the OS since.
Any help would be greatly appreciated.
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
http://developer.motorola.com/products/software/
I suggest you find the correct ROM and follow the procedures in that website. Flash back all the original files then your XOOM should boot up.
Thanks for the reply. But oI tried that already but still no luck.
Sent from my EVO 4G LTE using xda app-developers app
You sure? If you can flash it in using fastboot, and it says successful then it should work. Those files are suppose to downgrade you back to honeycomb and restore everything back to factory default. It be like the day you got your XOOM.
Yes I am positive. I but I did just go ahead and do it again just now, still no success. Every step completes successfully but the end result is the same. Stuck at 5hat same place.
Sent from my EVO 4G LTE using xda app-developers app
Hey all. I have reached a defect in my research and I could use some help.
I have a Wifi Xoom that I fried the mother board on. Not sure how, just woke up one morn and it wouldn't turn on anymore.
So I replaced that MOBO with another that was listed as soft bricked (It was cheep so I figured why not try).
Anyway with the new board installed I can boot to the Motorola Logo, I can load fastboot, recovery and RSD. The device appears as it should on my pc and I can fastboot flash.
I replaced the system image, the recovery image, The userdata image and the boot image. using fastboot. I also cleared cache, from fastboot and recovery as well as deleting all user data from recovery (Factory Reset).
I also re-installed the whole system using an RSD Image which went successfully as well.
Now I know its actual flashing because I flashed a different recovery to test and that worked, but for some reason im stuck in a boot loop at the Motorola Logo. I can still access all features (fastboot, recovery and RSD) but it will not boot past the Moto Logo.
I have tried installing the 4.1.1 and 4.1.2 updates through recovery which both installed their updated boot loaders and for a moment I thought I had success when I saw the xoom boot image with the flashing squares, but then that froze and it rebooted never to be seen again.
So my question is, is this a hard brick and I should just stop trying or does anyone have any other suggestions?
Also I am not using a Moto cable, but it tells me that I am successfully flashing, and as I stated I am seeing the recovery flash correctly, Does this make a difference being that I have successful flashes for other partitions? Is the Boot partition special? It tells me I'm flashing, but is it lying to me?
Everything I read thus far indicates that if you can access fastboot and recovery that its not hard bricked, but what exactly does a hard brick look like?
Thanks All any insight is appreciated.
Hey all, i made my own Motorola usb cable and tried to reflash again with no success. I'm still boot looping.
Sent from my SCH-I535 using xda premium
I have and tried with an official Motorola cable now as well without success. ideas?
Sent from my SCH-I535 using xda premium
Try reflashing the official imgs (provided from motodev site) with fastboot and after locking your bootloader. Try booting up, if nothing changes, sorry but I doesn't know how to fix then. Hope it works...
Sent from my MZ601 using XDA HD Premium using 1/8of my brain, the other 7/8 is thinking in my love Isadora
Yea I tried that, no worries, but do you know what does a hard brick look like? I have searched and found no real description, all anyone says is if you can get to fast boot is more than likely not.
Sent from my SCH-I535 using xda premium
OK , I know its been a while but I just started playing with this again.
OK so I got the idea that it might be a permissions issue. so I wiped everything again and re-installed again. Following this I tried to fix permissions in TWRP which failed. I installed CWM and ran fix permission which was successful. after that I was able to boot the tablet to android and install an account.
However now it is rebooting with some frequency and periodically it will get stuck at the moto screen again.
At this point if I perform a data wipe and clear cache I can get the tablet to boot again but I still have this issue.
Also If I fix permissions again from either recovery or rom manager it sends me back to the being stuck at the moto screen and I have to start again.
Thoughts?
Recently i bought this device, i was able to root it using kingroot, yesterday i tried installing the xposed framework, since i didn't have custom recovery i saw a tutorial in youtube explaining how to install the framework without the need of custom recovery (it was a huge mistake), using a combo of busybox and the terminal emulator, the result was a bootloop, i am able to enter the factory recovery but even after wiping the data/cache to factory settings its still stuck on the bootloop. Since i dont have custom recovery i am kinda stuck and without pc at the moment its starting to seem like a lost case, the factory recovery as the option to enable adb, i found a tutorial online but i don't understand anything about batch files and it all seems kinda confusing to me. In the past i was able to unbrick my old phones using stock roms, using odin if i recall right, but since the device is fairly new i am unable to find a stock rom. My questions are,
can i use odin again using a 5.1.1 lollipop normal (rom)?
Is there an easier to follow tutorial on how to use the adb fuction?
Is there a way to instal cwm even in bootloop without the use of adb? Since wiping dalvik cache and fix permissions should fix the problem.
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.
so yesterday, I decided to root my tablet. Everything was working nicely after I rooted and downloaded clockwork mod. The whole problem started when I used an app called quick boot, and I booted into recovery mode. As it was rebooting, it asked for permissions(I accepted obviously), and I haven't been able to get past the logo screen ever since. I tried wiping everything, but it still doesn't work. Any solution to this?
Reflash stock firmware with odin should probably work.
I managed to fix it by using the adb sideload thing in twrp.