Related
I tried using superboot to root my nexus s, but ended up with having a stuck google screen upon reboot.
Is there anyway I can recover my phone to the original state. I can get into the boot screen by pressing up volume and the power button and I have downloaded an original rom; however, I don't know how to upload this rom
into the phone.
I unlocked the bootloader, and have the android SDK installed. I do have a response when I use the command "fastboot devices"
Is there any possible way to save my phone? Please help, Thanks in advance
is there a recovery image saved under the recovery option?
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
ri ch said:
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
Click to expand...
Click to collapse
You have to flash CWM using fastboot, not adb.
fastboot flash recovery recovery.img
Once you have the custom recovery flashed you can flash superuser in CWM to get root back or just flash one of the custom ROMs that include superuser.
Yes, I did exactly that.
I really have no idea what I'm doing so I'm extremely grateful for people who do.
Thanks
I am in the same boat as these other chaps. After installing the 2.3.6 OTA update I tried to root with Superboot and now my Nexus S just sits on the Google screen with the open padlock.
I've tried installing CWM recovery, as well as the boot.recovery.img that comes with Superboot, and it seems to install successfully. After rebooting my phone still sits on the Google screen, however.
Am I doing something wrong here (I'd previously rooted with few problems)?
EDIT: I should mention that after flashing the .img I'm trying to boot into recovery - at this point it just sits on the Google screen.
EDIT 2: Never mind, I sorted it. I tried using a different recovery.img (from this thread) and I was then able to get into recovery and restore a backup.
Hello,
I installed a custom ROM on my samsung infuse some months ago.
I wanted to install a new one and in the process, I bricked my phone.
I used ODIN3 v1.7 software to unbrick my phone but now I am not able to install the CWM recovery.
I tried following things:
1. Used ROM Manger app to install CWM recovery but no success. It does
not pass the SAMSUNG screen
2. Deleted the file /system/bin/recovery and then started the process but
no success. It does not pass the SAMSUNG screen
3. Copied the CWM recovery onto /sdcard and tried to install it but it
errors out with some permission issue.
Please let me know how do I fix this problem?
Try this it has always got me out of this type of situation.
http://forum.xda-developers.com/showthread.php?t=1116251
Thank you very much for the help.
I have tried this but did not help me.
I will try it again and see if I am able to flash ClockworkMod Recovery.
This is what I did:
I unbricked my phone using the link.
http://forum.xda-developers.com/show....php?t=1116251
Then, I rooted my phone using SuperOneClick.
Then, using the ROM manager, I downloaded the CWM recovery.
While I was trying to install it, I got "Signature invalid" error.
Hence, I 3e modded my phone by deleting the recovery file /system/bin and copying the recovery file from the following location into /system/bin
http://forum.xda-developers.com/showthread.php?t=909213
Now, when I tried to reboot my phone and enter into 3e recovery, the phone starts and it does not pass after SAMSUNG black screen.
Am I doing some wrong?
http://www.youtube.com/watch?v=Y09p-J_g_Rg&feature=youtube_gdata_player do these
Sent from my SGH-I997 using xda premium
Here goes:
I have a TF101 WW with root and CWM. I recently had a bootloop problem, which I managed to fix with roach's version of CWM. Then the next update from Asus came out (9.2.1.24), which failed to install, apparently because CWM is in the way.
I then waited for the downloadable update to be available on Asus' website, I temporarily unrooted with OTA Rootkeeper and installed the zip through CWM.
Upon reboot, everything seemed fine, version checked out, until I tried rerooting with Rootkeeper. Rootkeeper apparently lost its protected backup of su and couldn't reroot.
So I tried rebooting to CWM to install Superuser-3.0.7-efghi-signed.zip and get my root back, only to see the dead android logo with a red warning sign.
Next I tried connecting through adb, which has always worked before... until now.
When I insert the usb in my pc, I don't even get the usual 'new device' sound and the adb devices list remains empty. Same in apx mode.
Any ideas? My device works just fine, except for apps that require root, booting into recovery and connecting through adb. I really would like these things fixed if possible...
[email protected] said:
Here goes:
I have a TF101 WW with root and CWM. I recently had a bootloop problem, which I managed to fix with roach's version of CWM. Then the next update from Asus came out (9.2.1.24), which failed to install, apparently because CWM is in the way.
I then waited for the downloadable update to be available on Asus' website, I temporarily unrooted with OTA Rootkeeper and installed the zip through CWM.
Upon reboot, everything seemed fine, version checked out, until I tried rerooting with Rootkeeper. Rootkeeper apparently lost its protected backup of su and couldn't reroot.
So I tried rebooting to CWM to install Superuser-3.0.7-efghi-signed.zip and get my root back, only to see the dead android logo with a red warning sign.
Next I tried connecting through adb, which has always worked before... until now.
When I insert the usb in my pc, I don't even get the usual 'new device' sound and the adb devices list remains empty. Same in apx mode.
Any ideas? My device works just fine, except for apps that require root, booting into recovery and connecting through adb. I really would like these things fixed if possible...
Click to expand...
Click to collapse
OTA Rootkeeper only work when you let it OTA update. When you flashed the firmware from Asus, you unrooted and restore stock recovery, that's why you see the Android with red ! mark.
See if you can get into system/bin if there's a su there try and copy it to system/xbin and see what happen (hopefully you still have partial root).
No such luck. Su is gone from both bin and xbin.
So I gather I can't boot to recovery because it has been restored to stock recovery. Bummer.
Some additional questions [semi-noob alert]:
If updating through OTA doesn't work with CWM, and updating through CWM removes root and CWM, how am I supposed to update?
If restoring to stock and unrooting is that simple, why does Wolf go through so much trouble?
Why did I lose usb-connectivity?
If adb doesn't work, is there a way to reroot my Transformer?
For future cases, once I am rooted again, is it possible to put a copy of su on an external microsd, give it the right permissions and stuff, and keep that as a backup to re-acquire root in similar cases? Or can su only work on /system?
I know it's a lot of questions, I'd be happy with answers to any one of them
-you update by waiting for a cwm flashable zip from one of the dev.
-wolfs thread has nothing to do with unrooting, his is downgrading to a rootable version or striaght pushing a recovery to flash su binary plus su zip
-some peoples report loosing usb when updating to ics, try going into system settings, storage, usb pc connection and see if mtp is check off
-for adb try another driver
sorry for all lower case, some reason shift button not working on my mac any more.
Yeah, sorry your going to have to re-root
On the bright side, you can use NvFlash now if you're inclined too xD
[email protected] said:
No such luck. Su is gone from both bin and xbin.
So I gather I can't boot to recovery because it has been restored to stock recovery. Bummer.
Some additional questions [semi-noob alert]:
[
For future cases, once I am rooted again, is it possible to put a copy of su on an external microsd, give it the right permissions and stuff, and keep that as a backup to re-acquire root in similar cases? Or can su only work on /system?
I know it's a lot of questions, I'd be happy with answers to any one of them
Click to expand...
Click to collapse
No, because microsd is mounted with nosuid.
You must place the backup on a filesystem which is mounted without nosuid.
Thx for the replies. Now I understand how I got into this situation. Still don't know how to get out of it, though
Key to the solution seems to be to get adb working.
I enabled usb debugging on the tablet, checked MTP off in storage settings and removed and reinstalled asus sync. I tried connecting both with asus sync running and with asus sync disabled on the pc. I made sure to shut off the splashtop streamer service.
I tried this on my usual pc (where adb used to work before update) and on a seperate laptop.
I took pretty good care of my connection cable so far, so I strongly suspect it is still in working order.
Result is nothing at all. No notification sound upon connecting, no tray popup discovering new hardware, no device in asus sync, no devices in adb, no usb debugging icon on transformer.
(EDIT: I lied. Result is that the transformer screen turns on upon insertion and removal of the usb plug in the pc.)
Anything else I can try?
@baseballfanz: what exactly do you mean by 'for adb try another driver'. Where can I find alternate drivers?
EDIT: I dual-boot W7 and Ubuntu, how do I go about trying to connect with adb from Ubuntu?
Hi.
I assume you're running windows.
Kill the process "asusUPCTLoader.exe" and try adb again.
If you need to reroot, flash CWM with nvflash, then flash SU from cwm.
Wheelie has been released and allows for SBK2 (b70+) devices to use nvflash.
http://forum.xda-developers.com/showthread.php?t=1676845
You will need a linux virtual machine/livecd though.
Ubuntu doesn't need drivers, just download the android-sdk and put it somewhere, it'll have executable adb in it.
whitekidney said:
Hi.
I assume you're running windows.
Kill the process "asusUPCTLoader.exe" and try adb again.
Click to expand...
Click to collapse
no luck, same thing. Also, I tried reinstalling the android-sdk platform-tools to get the latest and greatest adb, but no dice.
Tried getting adb to work in Ubuntu also, but no luck.
whitekidney said:
If you need to reroot, flash CWM with nvflash, then flash SU from cwm.
Wheelie has been released and allows for SBK2 (b70+) devices to use nvflash.
http://forum.xda-developers.com/showthread.php?t=1676845
You will need a linux virtual machine/livecd though.
Click to expand...
Click to collapse
Ok, I went to that Wheelie site, looked at the instructions and didn't understand anything about it. What exactly is nvflash? Do I need adb for that or (as I understand it) is it more low-level and doesn't require drivers and such?
Obviously that link is for users who have a basic knowledge of what nvflash is, what it can do and how to do it.
Both nvflash and wheelie require access to the usb device with Vendor ID 0×955 and Product ID 0×7820. If you are unable to set this up yourself, it’s recommend to run the tools with “sudo” or as the root user.
All usage requires booting your tablet into APX mode by connecting it to USB, turning it off and turn it back on while holding Volume Up!
Included scripts (full reflash)
SBKv1
./reflash_sbkv1.sh
SBKv2
./reflash_sbkv2.sh
In order to use this, you will need to download a full update from ASUS for your SKU and unpack the “blob” file from within the zip using the provided blobunpack tool. We recommend sticking to 100% stock blobs for this step and then root afterwards!
Click to expand...
Click to collapse
Vendor-id? Product-id? SBKv1 or v2? Help!
Before trying NvFlash, uninstall any ADB related or asus-sync stuff, and try my PERI root tool (In my signature) It might help you out getting recovery adb and root back.
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the stock ROM?
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.