Database Info

[Q] [q] ???help bricked maybe????

Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.

jekovenatinsley said:
Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
Click to expand...
Click to collapse
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.

Hey man try this, it works for me (Same situation but i'm 17 xD)
1) Download this http://www.mediafire.com/?5diezc69u1b16f8
2)Extract the "recovery1" folder in C:\ drive
3)Plug the tablet to PC and turn it on while pressing VOL- and POWER, then go to the fastboot mode (is the USB symbol)
4)Download from here ( http://support.asus.com/Download.asp...300T&p=20&s=16 ) the WW of US instead of the version of the tablet you have got, the extract the blob file in the "recovery1" folder
5)Open CMD, type cd c:\recovery1 then press enter
6)Type dir to see if all the files are in the folder
7)type this command fastboot -i 0x0B05 flash system blob
8)After is done, type fastboot -i 0x0B05 reboot
9)Enjoy!
If you can't do any of this steps, post here and I will help you

Fixed It!
ZerOMKD said:
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Click to expand...
Click to collapse
Hey actually like 10 mins after I posted I was able to install Clean Rom.
I formated every partition except sd card in v6.0.1.2 cwm recovery as well as factory reset and wipe dalvik.
Actually I like cwm recovery better and it does support microsd cards now. This is the jb/touch bootloader.
Thanks for the Help anyways.

.
Same problem, when i try to flash JB Hydro 3.6... i stuck into bootloop... i flash the official asus update and it works... But when i try to flash the hydro rom it doesn't work.... Why?

I guess you have the new JellyBean Bootloader... because of that you can only flash ROM's which are made for it...

.
I know... i update from jb ota to hydro... but when i flash the 3.6 i got bootloop... and now i can flash this rom...

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

[HELP] return to stock

So I've been running rooted stock for a while and decided to try out blisspop. After a few days I decided to return to stock, partly because I read about the 3.1.1 update coming out. I downloaded the 3.1 full OTA, flashed it with TWRP and all was fine. Things started to get wonky when I got home the other night and decided to update the controller( I hadn't done it after the 3.1 update rolled out). The controller wouldn't update and the tablet kept freezing up. Then the download for the 3.1.1 update showed up and of course I didn't flash it because I wasn't stock. Then I started getting google play services errors and I couldn't do a thing so I did a factory reset. During the setup process it keeps freezing up during 'Checking connection'. I can forget the network, go through the setup and get to the home screen but then I have no icons. I can restart the tablet and the the default icons appear where I can then connect to my wifi network but I can't add a google account(keep getting google services errors)(I enter my email address to add the account, hit 'next' and it freezes up). The weird things is this even happens when I reboot to bootloader and
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
and then
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
This is of course after downloading the recovery image(3.1 found here http://forum.xda-developers.com/shield-tablet/general/stock-recovery-images-ota-library-guides-t2988881) and verifying the md5 so I know everything is good. The really wierd thing is, I have none of these problems if I get back into the bootloader, flash TWRP, reboot into recovery and then flash bliss, gapps, and reboot.
Does this make sense to anyone?
Any help would be appreciated
Thanks

Update: I went through the same process and flashed the stock 2.2.2 recovery image. Same results, I cannot add a google account but I can connect to my wifi network. Right now it's downloading the 3.1.1 update, so we'll see in a bit.

deleted

All is good. I still have no idea what I screwed up.
After using the fastboot erase commands, and then flashing TWRP, I noticed some messages in twrp about not being able to mount /system, /data, etc. So who knows? So I tried to flash blisspop again and I ended up in a loop booting into twrp again and again.
So I erased everything again, flashed twrp, booted to recovery and formatted internal storage. I flashed the full 3.1.1 OTA, rebooted and my world is beautiful again(no google play services errors).
Hopefully these posts help someone, if some sense can be made of them.
Sent from my SHIELD Tablet using Tapatalk

Man this helped me out tremendously!!! I think just the steps to manually erase each partition (if thats what they're called) is what ended up helping me. I had to do it twice for it to work properly but it worked! And I'm pretty sure I tried everything the past few days. I wasn't having the same problem as you. My tablet was stuck on the nvidia boot screen after trying to flash stock recovery. Thought I bricked my device for a couple days. Thanks for posting!

unable to flash any update with twrp..need help.. with each ota file the error comes-- " package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K... this device has nvidia/omni_shieldtablet/shieldtablet:6.0.1/MOB30D/ "

manish.kumar86 said:
unable to flash any update with twrp..need help.. with each ota file the error comes-- " package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K... this device has nvidia/omni_shieldtablet/shieldtablet:6.0.1/MOB30D/ "
Click to expand...
Click to collapse
Please try to ask in only one place, it's confusing to those who try to help you when the same question is in the different posts
Sent from my SHIELD Tablet K1 using Tapatalk

I know but no solution from anywhere.. now i have even stuck in worse situation. Tries flashing all three version of stock image--
SHIELD TABLET K1 open source and binary driver release for OTA 1.2.0
SHIELD TABLET K1 open source and binary driver release for OTA 1.1.1
SHIELD TABLET K1 open source and binary driver release for preinstalled factory image
but not able to boot into recovery and also its not booting for hours.. i feel i cant revert from android 6.0.1 to any one of the stock image given by nvidia mentioned above..
Even tried experimental twrp and any other twrp i can find for shield k1, but its not going into recovery..
any help wd be great..
Exile1975 said:
Please try to ask in only one place, it's confusing to those who try to help you when the same question is in the different posts
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse

where is this battery.dtb file? its not in the folder i downloaded from nvidia and i cant find it anywhere

oilerseberle14 said:
where is this battery.dtb file? its not in the folder i downloaded from nvidia and i cant find it anywhere
Click to expand...
Click to collapse
Me neither

ADB Not Listing Device, no OS or Recovery Installed

Earlier today I did a factory reset through the OS on my shield tablet and when it rebooted it showed the NVIDIA logo but just a black screen after that. I tried to get into CWM and try to flash an new rom but there is not recovery image.
I then tried to flash a new recovery image through ADB fast boot but ADB wont find my deceive. So is my device bricked or how can I make adb find my device?

/COLOR]
de_BearKing said:
Earlier today I did a factory reset through the OS on my shield tablet and when it rebooted it showed the NVIDIA logo but just a black screen after that. I tried to get into CWM and try to flash an new rom but there is not recovery image.
I then tried to flash a new recovery image through ADB fast boot but ADB wont find my deceive. So is my device bricked or how can I make adb find my device?
Click to expand...
Click to collapse
You can't flash factory images via ADB. It has to be using Fastboot, from the bootloader in a custom recovery. If you can get to the bootloader, try that.
You might find Shield RAM v1.1 helpful. Just swap out the OTA included in the app's folder, with the one you wanna use.

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