Database Info

[Q] I am stuck up with my bootloader

I have rooted my nexus one and tried to flash a custom rom. I performed following steps:
1. Rooted as per the instruction. After applying the commands It was ready
2. Installed a custom recovery image with recovery-RA-nexus-v1.7.0.img and it was successful. After rebooting i went in to boot loader mode and took a nandroid backup.
3. Then downloaded a custom rom and placed all radio(radio-4.06.00.12_7), Google App(gapps-hdpi-FRF91-signed), CyanogenMod 6(update-cm-6.0.0-N1-RC2-signed) in to my root of the SD card.
4. Rebooted with recovery mode (holding volume down and power) and selected recovery and it rebooted but got a orange !(symbol) with android and nothing happens.
Please any one help me to how to resolve this. I tried once again installed a custom recovery with the same image. But no luck

Try to reflash CM or restore nandroid backup and then reflash CM

stuck in bootload
dlcsboop said:
I have rooted my nexus one and tried to flash a custom rom. I performed following steps:
1. Rooted as per the instruction. After applying the commands It was ready
2. Installed a custom recovery image with recovery-RA-nexus-v1.7.0.img and it was successful. After rebooting i went in to boot loader mode and took a nandroid backup.
3. Then downloaded a custom rom and placed all radio(radio-4.06.00.12_7), Google App(gapps-hdpi-FRF91-signed), CyanogenMod 6(update-cm-6.0.0-N1-RC2-signed) in to my root of the SD card.
4. Rebooted with recovery mode (holding volume down and power) and selected recovery and it rebooted but got a orange !(symbol) with android and nothing happens.
Please any one help me to how to resolve this. I tried once again installed a custom recovery with the same image. But no luck
Click to expand...
Click to collapse
I have the same problem.
I use nexus 7 toolkit download and install factory 4.2.2 img. but then it stuck in bootloader. I tried reload 4.2.1, back, it still stuck in bootload. My computer sees the device.
How to fix this problem? please help.
Wenson

[Q] HELP stuck on google screen after trying to root with superboot

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.

HELP! possible brick after installing TWRP recovery

After installing openscript recovery TWRP 2.2.1 via goo manager and then realize the recovery could not mount system or install any zip. I then try to revert back to team rogue xm recovery 1.5.0 with sucess by installing the recovery zip in TWRP (although some error due to system unable to mount). Got pretty happy that I'm able to revert back to rogue recovery but now faces this STUCK in automatic rebooting to recovery everytime I've try to reboot. I wipes everything completed 3x and install new rom but can't ever boot pass the recovery. I have yet to revert back to stock via softbrick method and figure I should ask for help first before unroot and unlock to start from scratch. below is an image of when ever I booted my xoom. Thanks for any help.
Oh, I've search first but noon seem to have the same problem as mine.

[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.

can't change to magisk instead of superSU on samsung j111f

I have a samsung j111f rooted with a twrp recovery via flashing superSU zip but when i wanted to change to magisk i couldn't uninstall superSU via full unroot , I managed to do that many times before and rooted it again via twrp, but the problem now is that when i try to do a full unroot it asks me to revert to stock boot image i hit yes then it asks to revert to stock recovery so i hit no because i need it to flash magisk so it fails to full unroot, but when i hit no at recovering boot image it bypass but magisk dont want to flash because i have a modified boot partition; So please would you help me ?
PS : I have an unlocked bootloader witch i got since my first rooting following this : https://forum.xda-developers.com/android/development/root-samsung-galaxy-j1-ace-sm-j111m-f-t3395520
Also i have installed twrp recovery via odin on that unlocked bootloader because it always boot to stock recovery when i try to flash it on stock firmware
Never mind i found the sollution just full unroot without fixing bootloader from supperSU ,booted into twrp recovery flashed stock boot.img then magisk.zip and rebooted that's it got evrything worked
Click to expand...
Click to collapse