Database Info

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

[Q] Soft bricked after CWM installation / SOLVED

Hi all,
I have a TF300T with stock 4.2.1 android.
As i also own a nexus 7 with cyanogenmod, i decided to also give it a try on my TF300T
Unfortunately it ended in a endless loop of CWM recovery :crying:
This is what i did :
- i started with this thread http://forum.xda-developers.com/showthread.php?t=2055430
- it reference to another thread that describes how to install CWM recovery - > http://forum.xda-developers.com/showthread.php?t=1668173
I followed all 9 point in the CWM installation guide.
After that i wanted to flash the root zip and recognized that the CWM is not able to mount the sdcard and internal memory.
So i was not able to root the device and also not able to flash any custom rom.
After reading in the forum i was able with "adb reboot fastboot" to boot again into the stock ROM.
- Reading more in the forum i learned that TWRP should have been used . So i tried with fastboot to overwrite the existing recovery , but with no success.
- Reading even more in the forum i saw that there is a way to remove the CWM by restoring the orginal stock ROM with the folloing command.
"fastboot -i 0x0B05 flash staging blob" with blob coming from TW_epad-user-10.6.2.6.zip from asus web page.
After that i can not even reboot to the stock android ROM.
I still have CWM after booting of the device.
I can still open adb shell. But su is not working as i do not have root.
What is the best way now to get back to a working android on my TF300T?
Many thanks in advance for any good hints.
/BR

Is that the firmware that was already on it? I'd try installing 10.6.1.15.3 which is the newest firmware via fastboot. Should erase the recovery. I wouldn't do the 27.3 firmware, not all ROMs support it

as i do not have fastboot anymore , how to flash the stock ROM?
Can this be done with adb?
Or is there a way to get fastboot again?
I currently have endloess boot loop into CWM.
And as i can not access in CWM the sdcard and internal memory i am not able to flash anything.
I just saw this thread here - > http://forum.xda-developers.com/showthread.php?t=2236885
They had similar problems and also no fastboot
Other point is , do i need root access to fix it?
Even with adb i can not push files as the partitions are not mounted.
What about using sideload feature in CWM? will this allow to send a custom rom zip?

I finally got back my fast boot.
I made an hard reset (with hole below sdcard)
After that I could start the tablet with volume down and got back to fastboot
By that I am now able to start again the stock android that was already installed. So as long as I do not shutdown the tablet I at least can use it.
I see quiet a lot of discussions in the forum about soft brick tf300 after 4.2.1 ubdates.
I will now follow these and see if there will be a proper solution for my issue.
Thx
Sent from my Nexus 7 using xda app-developers app

kreutpet said:
I finally got back my fast boot.
I made an hard reset (with hole below sdcard)
After that I could start the tablet with volume down and got back to fastboot
By that I am now able to start again the stock android that was already installed. So as long as I do not shutdown the tablet I at least can use it.
I see quiet a lot of discussions in the forum about soft brick tf300 after 4.2.1 ubdates.
I will now follow these and see if there will be a proper solution for my issue.
Thx
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Found a recovery that actually works with 10.6.1.8 (4.2 bootloader): http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Good to get you back to flashing happy. Not sure if it works with the 10.6.1.27. update though.

Finally have reached my goal...
CyanogenMod 10.1 nightly , trap, rooted....
After Ben back to stock I used this guideline staring from 4.2.1 stock
http://www.android-hilfe.de/root-cu...1-10-6-1-15-3-twrp-recovery-2-5-0-0-root.html
Sent from my Nexus 7 using xda app-developers app

Asus TF300T issues with CWM 6.0.2.3
I bought an Asus TF300T for Christmas 2014. It had JellyBean 4.2.1 on it.
I decided to try to update the device to Lollipop CM12 and admittantly I am a noob when it comes to Android tablets.
So, I installed the ClockworkMod (which installed correctly), but it has my tablet stuck in a loop. It won't mount the /sdcard
and when I open a Command Prompt with Administrator Privileges and attach the usb cable to the device, it won't find it.
I've downloaded the stock rom from Asus for the device and placed it on a 2 GB MicroSD Card that the device will not find or see.
After reading through this thread, I am feeling a bit out of my league on how to recover the device.
Any assistance would be greatly appreciated.

Can't get my new tf700t to root or install recovery.

Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?

benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....

LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.

benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?

benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891

benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.

That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?

benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!

Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!

[Q] HELP!!! Got stuck in cwm on ZTE blade III

Im a bit noob for these things, two days ago I bought this phone ZTE blade III, I heard this phone will work like a charm with kitkat 4.4 so I wanted to upgrade android to 4.4, I think I followed all steps to install it but I failed to install this update and got stuck in CWM mode. I tried to restore files, system, etc. wiped all data, then restored again, tried to install other ROMs but Im still stuck in CWM mode. Please help me.

Alexi_Zavetnik said:
Im a bit noob for these things, two days ago I bought this phone ZTE blade III, I heard this phone will work like a charm with kitkat 4.4 so I wanted to upgrade android to 4.4, I think I followed all steps to install it but I failed to install this update and got stuck in CWM mode. I tried to restore files, system, etc. wiped all data, then restored again, tried to install other ROMs but Im still stuck in CWM mode. Please help me.
Click to expand...
Click to collapse
Okay, first of all I would recommend restoring stock ROM but DON'T restore in CWM as their are issues unless its a Nandroid backup, In the stock ROM file you will find the stock recover (recovery.img) flash that via fastboot the same way you would flash CWM, after this you can restore your stock ROM using the update.zip file

TechMinerUK said:
Okay, first of all I would recommend restoring stock ROM but DON'T restore in CWM as their are issues unless its a Nandroid backup, In the stock ROM file you will find the stock recover (recovery.img) flash that via fastboot the same way you would flash CWM, after this you can restore your stock ROM using the update.zip file
Click to expand...
Click to collapse
Can you explain me what to do step by step, please.

Alexi_Zavetnik said:
Can you explain me what to do step by step, please.
Click to expand...
Click to collapse
Make sure you have a stock ROM for your ZTE Blade and have coppied the recovery.img file from it
Coppy the Stock ROM to your SD
Then set your phone into fastboot mode which can be achived by holding down the volume up and power button
Now your in fastboot so go and download the ZTE Blade fastboot drivers which you should have since you flashed CWM
Check in Fastboot CMD that your device is listed and type: fastboot flash recovery recovery.img (Which can be extracted from the rom)
Now return your phone to recovery as you would in CWM
In stocm recovery flash the update.zip (Stock ROM)
Hopefully all should be well and good

TechMinerUK said:
Make sure you have a stock ROM for your ZTE Blade and have coppied the recovery.img file from it
Coppy the Stock ROM to your SD
Then set your phone into fastboot mode which can be achived by holding down the volume up and power button
Now your in fastboot so go and download the ZTE Blade fastboot drivers which you should have since you flashed CWM
Check in Fastboot CMD that your device is listed and type: fastboot flash recovery recovery.img (Which can be extracted from the rom)
Now return your phone to recovery as you would in CWM
In stocm recovery flash the update.zip (Stock ROM)
Hopefully all should be well and good
Click to expand...
Click to collapse
Heres what I got, downloaded stock ROM from ZTE website and whenever I try to install it it says signature verificitation failed. Before I do what you said, can you send me trusted working stock ROM for this phone, Serbia, VIP(mobile network) version?

Alexi_Zavetnik said:
Heres what I got, downloaded stock ROM from ZTE website and whenever I try to install it it says signature verificitation failed. Before I do what you said, can you send me trusted working stock ROM for this phone, Serbia, VIP(mobile network) version?
Click to expand...
Click to collapse
Sorry, I forgot to ask if it was carrier locked
If you need really in depth instructions they've created some great ones here that probably know a bit more about that specific device than I do
http://www.modaco.com/topic/361786-zte-blade-iii-stock-roms/
They also have your carrier ROM here, for some reason I couldn't copy the link but the site is in depth and easy to follow

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