Related
I rooted, and loaded cm9 rom. I prefer stock rom but when I restored my backup there was no wifi (apparently a common issue). Anyway, I am looking for a way to get back to stock rom. I downloaded firmware from Asus but dont know if that is what I need or what to do with it. I am using the twrp recovery
Thanks for any help
All you have to do is download the full Asus ZIP from my thread and flash in CMW and it will restore your fully stock ROM without recovery
http://forum.xda-developers.com/showthread.php?t=1680570
ok thanks now to figure out how to get cwm into my tablet-- right now trying to install sdk
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
this worked
Terminal Emulator Method
Install Android Terminal Emulator on your tablet.
Download the ClockworkMod Recovery image file directly to your tablet, preferably in the root of the /sdcard directory. Take note of where the file is saved. Rename the file to cwm-touch.blob.
Launch Android Terminal Emulator on your tablet.
Enter the commands below. If you did not save/move/copy the image file to the /sdcard directory, you need to replace /sdcardin the second command below with the correct directory where you saved the recovery image file to.
su
dd if=/sdcard/cwm-touch.blob of=/dev/block/mmcblk0p4
Reboot your tablet. The blob file will be automatically installed as your tablet reboots.
voodoo_dr said:
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
Click to expand...
Click to collapse
You can uninstall Eclipse. It has nothing to do with Android or flashing anything. It's an Integrated Development Environment, which is kind of like a word processor for programmers. The only relation it has to Android is that it supports the Java programming language, so a lot of Android developers use it. If you're not going to be writing apps or messing with Android source code, it's probably best if you uninstall Eclipse, just because you won't use it, and it's taking up storage space.
Also, what were you expecting to happen when you put the tablet in fastboot mode? It just opens up a serial connection with a host (in this case, your computer) and allows the host to access the tablet via fastboot (sounds confusing, I know; it's not particularly fast, and doesn't have much to do with booting anything; it's like ADB but for low-level [hardware] flashing) and run commands. The tablet itself does nothing except display the message that it's in fastboot mode. Once the tablet says that, you run fastboot on the computer.
thanks for the reply. Now I have a brick---tried to install stock rom and hangs on asus with the wheel going round and round. It deleted my cwm so now no recovery on tablet. When I go into fastboot, it doesnt seem to recognize my tablet adb devices--nothing comes up
In my device manager I see no adp drivers- the only driver which keeps installing when I plug in the tablet and go to fastmode is the asus bootloader interface so I cant do anything with the tablet--- no recognition of device with adb devices command Help please
If you're in fastboot, ADB won't recognize the tablet. You need to use the fastboot commands with fastboot.
What to do:
-download the CWM blob on your computer
-put the CWM blob in the directory on your computer with the fastboot program
-boot the tablet into fastboot, and flash CWM
-boot into CWM, and restore the nandroid backup you should have made.
Alternately, if you didn't make a nandroid backup, you can boot into recovery, push the Asus stock ROM to /sdcard on your tablet via ADB (I'm assuming ADB works in the stock recovery), then reboot into recovery, and it should flash the update automatically. This will erase ALL your data, including /sdcard.
is cwm blob recovery.img?
I'm not sure if flashing .img files works with this tablet, but you could try. If it doesn't work, go to the place you got the recovery (as long as it's not from ROM Manager, and you're positive it's not the TF201's recovery), and there should be a file that ends in .blob. That's the one you need.
then I just place it in the same directory and click on fastboot? or is there more to it? seems to be having trouble with drivers mtp driver not installing???
I don't use Windows, so I don't know about the drivers. There's a thread in the development section with all the Windows drivers you need, though.
You put the blob in the directory where fastboot is. You open the command line (open Run, and type "cmd" [no quotes]) and run the fastboot command from there.
got it thanks cwm is back
Hi everyone,
First post (brilliant video!).
My tablet:
Asus Transformer Pad TF300 (rooted)
CWM 5.8.2
My problem:
- We decided to give our Transformer to my gf's dad for his birthday. I tried to backup using a later version of CWM (6 something) but it didn't work. I downgraded to 5.8.2 and it worked fine. I then did a factory reset (which I realise now was not the way to go).
- CMW bootloop : restored my backup, successful - still bootloop.
- Have spent the last 4 hours figuring out ADB and managed to push both a new recovery (rogue) and the latest ASUS firmware to the SDCARD. Despite it confirming the transfer from the cmd line I could not see the zip files in the directories. I tried several times to several different directories. On the last try before the SD card decided to go on vacation I did see one of the files in the root directory.
- Now, no matter what I do, I get a "can't mount /SDCARD" error. Trying to erase/format/factory reset the pad results in errors when trying to access DATA and SDCARD.
- I've located and tried several different scripts from different threads that supposedly create a fake SDCARD directory but nothing has worked
http://forum.xda-developers.com/showthread.php?t=1679274&highlight=encrypted&page=3
- I've also tried to run the install package remotely from ADB but the mounting problem reoccurs
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
It appears that many people have encountered similar problems but none of the recommendations have been successful for me so far.
There also seems to be a strange anomaly with the adb shell timing out before I can finish the command. Is this a cable issue?
I'd be super grateful to anyone that can help me sort this out.
Cheers
Sam
Anyone?
I should mention that I had installed Super SU / Super User on the tablet... if that makes any difference.
I woke up this morning and booted the tablet to get this:
E:can't mount /cache/recover/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
Error mounting /cache!
In addition to all the previous problems.
Super!
Nobody? Anybody?! Please help!
Hi,
If you have fastboot mode, try to inject twrp (the last 2.2.x.x or something like that) ...
--> read the way to do that on the http://teamw.in/project/twrp2/97
With last TWRP you can mount sd card (first download & extract stock rom .zip and put it on root of your sdcard)
After that, flash stock rom with TWRP ...
Choose fastboot method...be careful (there is 2 versions : JB or ICS)
SOFT BRICK fixable!!! although root repair not yet covered...
I seemed to have a simular problem on my tf300t.
tried to install a CM 9.1.0 (stable)
Stuck at asus cold boot screen.
Solution i found+
*download Fastboot and an adb.shell brigde if you dont already have it.
*place the downloaded systemware (AVALIBLE ON THE ASUS SUPPORT WEBSITE) you wish to install in the same folder you have fastboot. (example-US_epad_10.4.3.13.blob)[432.3MB]
*Boot tablet into CWM [NOTE: I used CWM-Touch. 6.0.3.1 or something along those lines] (TWRP- im unsure if the process is the same).
-from advanced settings at the bottom, wipe dalvik cache.
-no need to wipe your user data cache, but wipe other data cache.
-reboot to bootloader and select fastboot option. (3rd one with pic of usb) DO NOT PLUG IT IN YET.
*Back on your WIN pc open your windows explorer, find the folder containing the Fastboot.exe and hold shift and right click at the same time for an admin operations menu. You should see an option "Open Command Prompt Here". Click it to begin a Fastboot session.
*NOW CONNECT YOUR TABLET!!!
*TYPE THE FOLLOWING AS SHOWN! DO NOT DIVERT OR YOU SCREW UP-
fastboot -i 0x0B05 flash system blob
***NOTE THAT THIS METHOD WILL TAKE QUITE SOME TIME AND YOUR COMPUTER MAY EVEN LOOK LIKE ITS FROZEN...STOP! JUST LET IT DO WHAT YOU ASKED IT TO...THIS IS QUITE A LARGE TASK AND WILL TAKE TIME. MY PC IS AN OLD DELL E300 dem. I KICK THE PROCESS ATLEAST A DOZEN TIMES BEFORE I JUST LEFT IT ALOOOOONNNE and it worked...although i cant seem to figure out how to delete the old su binary i install so i could re-root it....ANYONE GOT ANSWER? PLEASE HELP. EMAIL IS ALWAYS UP.
IF THESE INSTRUCTIONS ARE UNCLEAR, OR YOU DONT UNDERSTAND SOMETHING, MESSAGE ME...
AND IF THIS HELPED YOU...SHARE THE LOVE-GIMME A THANKS!
I've looked all over, but cannot find anything on the problem I am having.
I go through the steps to load the current factory image onto my nexus s 4g through terminal on my mac, but for some reason it doesn't load everything. Here's what it says in terminal about the items that can't load:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
And here's what my folder looks like where I'm loading everything from:
I guess I can't post a picture from an outside source, so I'll just type in what my folder looks like:
boot.img
bootloader-crespo4g-d720spric1.img
flash-all.bat
flash-all.sh
flash-base.sh
image-sojus-jro03r
image-sojus-jro03r.zip
radio-crespo4g-d720sprilf2.img
there are files in the unzipped folder (image-sojus-jro03r) named:
android-info.txt
recovery.img
system.img
userdata.img
These seem to be some of the files that are missing, but even when i drag them over to the main folder, they still don't load. maybe something to do with the fact that they are .sig's?
I drag the flash-all.sh file into terminal and it loads and writes everything except for these .sig's, which I truthfully don't know what they are. Now I can't get into the correct recovery mode, it just shows some weird blue-lettered options that are different then the normal recovery options. That is why I think the fact that these .sig files are not loading is the problem.
I also booted up the new operating system and signed on, but for some reason none of my apps can download.
Sorry for my noobness, but I'm sure I'm missing one easy step that will fix my problems.
Does anyone know what I'm going through?
Any help is much appreciated.
Alright. I've searched the web and found a few different things. It seems that it's common for those .sig files to not load. Also, i loaded the factory image again and was able to download my apps.
I also now foolishly realize that to get a good version of recovery, I need to root my phone. I'm in terminal now, and for some reason adb is not showing my phone in adb devices. This wasn't a problem when I loaded the factory image, but now it's a problem when I'm trying to do this: http://forum.xda-developers.com/showthread.php?t=1129759
step 5 is a problem, but hey, I can turn off the phone and go into fastboot mode myself. I guess step 7 is the next problem I'm dealing with. Here's what I get in terminal when I do step 7 manually (I put a *#* where my name is just so everyone knows):
MacBook:~ *#*$ /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img
-bash: /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img: Permission denied
Does anyone know what I'm dealing with this time around?
You probably need to enable adb in Settings --> Developer Options. If it's an issue with adb while in recovery, i'm pretty sure the stock recovery (which will be overwritten on every boot from a stock ROM) doesn't allow it. What you need to do is flash a new recovery in fastboot (not in recovery).
Commands (while in fastboot mode):
/path/to/fastboot devices <-- this will tell you if your phone is connected properly
/path/to/fastboot flash recovery /path/to/recovery.img <-- this will flash the new recovery
You'll need to type in the path to fastboot unless you have it in somewhere like /bin or a more convenient environmentally recognised location. The command you typed there is the same as trying to open the .img file as a script, you want to tell fastboot to flash the file to the phone and not open it with the computer.
Edit: Also, once you root, you probably want to delete /system/etc/install-recovery.sh. That file replaces any custom recovery with stock each time you boot.
Thanks Harbb.
That's what I ended up doing, using fastboot. it worked perfectly. I did try to find the /system/etc/install-recovery.sh file in root explorer, but could not find it. don't know where it is.
Everything is rooted and restored on my custom rom to where I was previously using titanium backup.
Here's the tutorial I was using: http://forum.xda-developers.com/showthread.php?t=1129759
with this video being a walkthrough of the previous tutorial: http://www.youtube.com/watch?v=sP9ZDWmbLVM
I was actually using the recovery img in the android folder that I downloaded from the tutorial, and not the one he told me to download, which was my problem in the end. Here's the link to the download page where I should have downloaded it from: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+4.0.0.2
Thanks again Harbb, much appreciated.
No worries buddy, glad you got it sorted.
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Long story, short:
For some reasons, seems like the WIPE command from TWRP and CWM recovery screw the partitions.
No partitions or microSD card can be mounted.
The tablet is now booting only in recovery mode or in fastboot mode (the screen with three icons - RTK, Android and WIPE) instead of Android.
IMPORTANT:
If your tablet reboot in fastboot mode DONT WIPE IT AGAIN! Just skip step 4.
First of all, MAKE SURE YOR BATTERY IS CHARGED!
Recharge your tablet for at least two hours.During the flashing process the tablet doesn`t charge.
Use the original Asus USB cable that came with the tablet or a high quality replacement cable. Cheap cables can and will cause problems.
Use a laptop or desktop with known good USB ports. If you have problems, try a diferent computer, some USB chips can cause troubles.
Disable the antivirus or screensaver, sleep etc...
1.Download these files:
from ASUS website: http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300TG/#support
Drivers&Tools, on the OS tab select Android
click on Utilities and download latest version of ASUS PC Sync (you will need this for drivers)
click on Firmware and download the lastest available (you will need this for BLOB file)
Minimal ADB and Fastboot: http://d-h.st/gbx
install ASUS PC Sync and Minimal ADB and Fastboot (on fastboot installer check the box that make a shortcut to desktop)
unzip the firmware file downloaded from ASUS site
you will get a second zip file, unzip this one too
the folder unzipped from the second one contain a file called blob
copy or move the folder to the root of your drive C: or D: or whatever drive letter you have
2.Installing drivers:
connect your tablet to PC
you will get a message about Windows couldnt find driver bla...bla, ignore it and keep your tablet plugged
IMPORTANT: even if you previously installed ASUS PC Sync or other drivers and Windows recognize your tablet, you still need to change the driver.
right-click on My Computer-Properties and click Device Manager
find the Asus Android device - should be with an exclamation mark on it (the driver is not installed sign)
right-click on it and choose:
Update Driver Software..., Browse my computer for driver software, Let me pick from a list of device drivers on my computer, Have disk, Browse
go to C:\Program Files or Program Files (x86), ASUS, ASUS Android USB Drivers, Android and select android_winusb.inf
Asus Android Composite ADB interface will appear in the list of device drivers - don`t hit next yet!
uncheck Show Compatible Hardware and select Asus Android Bootloader Interface from the list, now hit next
3.ADB mode:
open Minimal ADB and Fastboot from desktop - from this point, keep it open
type: adb devices - and you should see some numbers under the List of device attached - thats your tablet
if you can`t see the tablet, try this command: adb start-server
4.Booting to "fastboot":
there are two ways to do this:
a) from adb window type: adb reboot bootloader
or
b) reset and hold vol-down (didn`t work for me, but maybe will work for someone else)
the three icons will appear on screen - NOW YOU ARE IN FASTBOOT MODE
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
the credits for this part goes to buster99. He is the one who figured out the right commands for formatting partitions and flashing back the OS
here is his post: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
here we go, one at the time in adb window:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system x:\your blob folder\blob (here you enter the path to your blob file, must end with blob, to point at the file)
fastboot -i 0x0B05 reboot
THE FLASH SYSTEM COMMAND WILL TAKE SOME TIME
be pacient and wait until the progress bar is 100% full on the tablet and you get the command prompt back in the adb window.
After reboot, the Android is back on.
Cheers and good luck!!
A big thank you alexhosu,
several months ago that my tablet was blocked, but I still kept hope
a solution would be found. I'm really happy for you and thank you again for sharing.
Long live XDA
me too
Thanks from me too; was enjoying 5.0 (timduru) on my TF300 when I went to upgrade and idiotically managed to get into a TWRP bootloop(interrupted a format of \data and then used 'wipe' from the boot screen by mistake...)
Your solution has saved my tablet
Am now carefully reinstalling Katkiss
Thanks
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again
Followed the instructions.. Worked well, but getting error 963 when installing/updating anything in Play Store. Seems to be related to storage permissions. Some users are suggesting using format instead of erase. What's the difference? Could that help.
I did factory reset, reflashed and used fix permissions in TWRP but no luck...
alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Click to expand...
Click to collapse
Big thanks from me.
I killed my tablet with an accidental restore to factory defaults while in cm12, an got stuck in an endless bootloader boot loop.
my tablet came back too life at the end of section 4 after adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3.
although getting adb to talk to the tablet was a fluke.
I just kept trying to send "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" while the tablet was loading (boot looping)
6 months of believing my tablet was dead, after letting CM12 do its own update thing, and now, thanks to the above instructions, I'm back online and its working with the stock rom.
Thank you so much for this. No idea why I couldn't find these instructions before, then I just gave up, back in business now!
Thanks a lot for your guide, this is what helped me fortunately unbrick my device, i was stuck in a boot loop with a broken recovery
Another tablet saved. Know your work is appreciated.
i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.
ajeevlal said:
i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.
Click to expand...
Click to collapse
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.
Act32.97 said:
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.
Click to expand...
Click to collapse
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.
ajeevlal said:
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.
Click to expand...
Click to collapse
I would try moving the blob to the root of the C drive and try the 7th command "fastboot -i 0x0B05 flash system C:\blob" just to make sure sometime of file permission type issue isn't happening on the pc side. Other than that the only kind of issue I think it could be would have to be the connection with the drivers, although if erasing the partition's works fine, I don't really see what could be going on.
I followed all the steps and delete, but when loading the file update.blob I get this error:
C: \ Users \ mikel> C: \ Users \ mikel \ Android \ android-sdk \ platform-tools \ fastboot flash system update.blob
error: can not load 'update.blob'
Can someone help me out?
TF300T KissKat
Theziggy said:
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again
Click to expand...
Click to collapse
Hey, I know that I'm a couple years late on this. But, I was just given a Asus Transformer TF300T, and attempted to install the Kisskat custom rom. I unlocked the device with little issues. Rooted with little issues. But when it came to flashing the rom. I get his error saying that "no MD5 file found" and holds it there for a couple of minutes. Then gives me the failed install. My only option is to boot into recovery and restore the stock JB 4.2. If you could point me in the right direction, I would greatly appreciate it. I've searched the forum for someone with a similar issue, and couldn't find it. I hope that I'm not alone on this one. It would kill me to be stuck with the stock rom.
Hi i made a format data from TWRP recovery, and now i am in a recovery loop and got error of mount partitions, i can access to recovery and the screen with 3 icons, but when i plug to my pc it shows as uknown usb, i install the drivers but dosent reconose as a fastboot device, in minimal adb when i write fastboot devices the result is empty pleace help me.
Muito obrigado!
I know this must seem odd, being such an old thread and all but, after several years adding apps and changing ROMs on my wife's TF300T (my gift!) only these past weeks I had the need to search for help, after installing nougatella 7.1, which I did with success, only to stumble on endless logo loops and loading processes without conclusion. Don't get me wrong, the ROM looks great and it wasn't that hard to install but, after two weeks or so, gave me this problem and after correcting it and installing again the ROM, I got in trouble again...
After some five hours googling and trying different stuff, I finally found this thread and twenty minutes ago (around 2:AM) my ASUS returned to its (Jellybean) life!
Alexhosu, thank you so very much for such a detailed, yet easy to follow guide and, if you happen to come to Portugal on vacation and visit Setúbal, I'll have a bottle of Moscatel waiting for you!
Many thanks to Droidbound (who got me off the hook the first time the tablet went nuts!), and also Kevinthefixer, Gtanner00 and some other very inteligent, patient and thoughtful people, and all the guys who shared their difficulties and in a way helped me find the people with the fix.
For anyone interested in trying this method, I would say that it's paramount that you should stick exactly with what is asked and should pay real atention to what is the correct ROM update to download and use. If anyone needs help with translation to Portuguese, just say so.
Again, thank you so much for this!
JMonteiro
alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
Click to expand...
Click to collapse
Thanks for your help :good: and I'm sorry for my basic English, but here is another tablet saved. Your instructions were clear and my tablet is working.
I hope this information helps, based in the next link (user sszyman): https://forum.xda-developers.com/showthread.php?t=2275035&page=9
in which he recommends using the following commands too:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p2
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p8
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p1
With these commands and "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" I was able to solve my Bootloop problem.
Honestly I don't know which of the commands worked, I used all several times.
Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon
Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a