Related
I had CM7 installed on my phone, and then i proceeded to update to the beta 2. I downloaded the file, then unpacked it on my phone sdcard then proceeded to reboot in recovery mode and cleared cache , dalvik, factory settings and then updated the zip file. then clear everything again and reboot. Get stuck on dual core logo.
I can still access recovery and mount usb to add files. can anyone tell me how to fix this?
did you make a backup before installing the beta?
It seems like you've never installed a ROM before, so I would advise you to read before you try again.
Try and restore it from the 1.8.3 SBF or restore from the CM7 pre-beta2.zip.
Don't unpack the zip file.
Oh and I feel obligated to ask, but did you install romracer's recovery?
I have Tenfar's recovery. Does it matter?
When you say restore, do you mean going in recovery mode and then apply the beta-update2.zip?
I also beleive my recovery got updated to Clockwork's when I had CM7 beta installed?
I have read another post on here that suggest I should RSD flash the 1.8.3 SDF and just start anew.
Should I do that? I was on 1.8.3 prior to installing CM7 beta
I understand I probably come across as a complete noob, but I did read before I did anything.
And now this happened and I just need help fixing it, you can just say. Yes flash back to 1.8.3 with RSD, I don't need a dot point instruction on how to do that.
Now my recovery is "ClockworkMod Recovery v4.0.1.4" even tough i originally flashed Tenfar's
and my phone is unlocked.
I have tried many times to clear all caches and update the beta zip again and it does not work, I just get stuck on dual core logo again.
Thanks in advance for any help.
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
quicklyspent said:
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
Click to expand...
Click to collapse
Legend, thanks a lot now I can go back to sleep.
I installed romancer's recovery (unlike tenfar's it took like 5 times longer to clear cache and install the rom) but it did work.
thanks for taking the time man.
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Rayan said:
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
No I had wiped dalvik and cache prior and after update.
Either beta 2 doesn't like tenfars recovery or it was an issue with the download . Since I installed romancers recovery before I tried the new download we will never know
Sent from my MB860 using XDA Premium App
Why use tenfar's recovery when you can use CWM real recovery now.
That might help a lot...
im having the same problem but i used romracers recovery in the first place. ive tried everything and i tried to restore my alien backup but the recovery cant find it... did prebeta1 change the directory? im lost.
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Magnetox said:
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Click to expand...
Click to collapse
i tried that before and it didnt work.
edit- i found how to mount phone as usb in recovery. going to try the whole process again. i think my file was corrupt.
edit-- still cant get it to work even after redownloading teh file...
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!
Hello there, I just got my N10 32MB a few weeks ago and after playing with the stock rom for a bit decided to try some custom roms. I've tried CM10.1M3 and Paranoid and a couple others all with the same result. I flash them and they stay on the loading screen forever. I've used the Nexus 10 Toolkit donater version and I'm no stranger to dropping a custom rom on an android device I've been playing with them since the original Motorola Droid. I would have thought the N10 would have been cake to do this on but nothings is working. The ONLY rom it will take is the stock rom 4.22. I was able to successfully re-install it via adb after wiping all the roms off of the device. If anyone has any insight I would really appreciate it.
Go back in recovery, format /system, wipe data/factory reset, reflash ROM, gapps, reboot. Normal steps for flashing a ROM.
And you didn't use ADB to reflash stock images, but fastboot. Damn toolkits...
Sent from my Nexus
I'm no expert , but my first time I got the same result as you, what saved my bacon
Was that I done a backup first.
If I were to guess what my problem was
Maybe a corrupt donwload
And then make sure you do these steps
In recovery (cwm,tcwm)
Wipe -> Factory reset -> Cache and Davilk cache
Then go in
Install -> ROM -> Gapps
I take no responsibilities in case it bricks yours... but this as work for me.
Plus YouTube makes it really easy to do...if you need a videos tut's...
Sent from my Nexus 10 using xda app-developers app
Thanks for both the replies. Yes, I've done all this formatted system wiped both cache redownloaded the files tried sending them to the device from different PC's. You're right I didn't flash the rom via adb it was fastboot, I ened up having to sideload something via adb in tcwm maybe it was when I returned it to stock unrooted and relocked it to start all the way from square 1. I'm really at a loss I've let it sit at the boot screen for as long as 30 min and nothing starts up. It only seems to want to run stock 4.22.
ironhelix said:
I'm no expert , but my first time I got the same result as you, what saved my bacon
Was that I done a backup first.
If I were to guess what my problem was
Maybe a corrupt donwload
And then make sure you do these steps
In recovery (cwm,tcwm)
Wipe -> Factory reset -> Cache and Davilk cache
Then go in
Install -> ROM -> Gapps
I take no responsibilities in case it bricks yours... but this as work for me.
Plus YouTube makes it really easy to do...if you need a videos tut's...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Make sure your boot loader is unlocked. I remember having this issue on my Skyrocket awhile back. It would hang on the custom ROM installs.
cowabunga said:
Make sure your boot loader is unlocked. I remember having this issue on my Skyrocket awhile back. It would hang on the custom ROM installs.
Click to expand...
Click to collapse
It is...I even relocked it and unlocked it again as well as unrooted and rooted again to make sure.
Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.
Anyone? Please?
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.
What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.
My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium
Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium
Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.
Hi All
I am in the process of flashing Cyanogenmod 11 onto my TF300T however I am in a world of hurt. First I updated to the latest TWRP (2.6.3 -4.2). When i boot up into TWRP it is asking me for a password which I do not know. If I press Cancel i cannot see any contents of /sdcard. Also if I insert a microSD card, again cannot see any contents. TWRP is telling me there is no operating system installed and if i reboot it just comes straight back into TWRP.
I apologise if this question has already been asked but I just cant figure this one out.
What bootloader version do you have? What helped me was to reboot into the boot loader (using volume down+power, has three options RCK, cold-boot linux, Wipe data [dont ever ever ever wipe data]) and select cold-boot linux (the android guy in the middle) and it would boot back into my ROM. If you cant get in that way, you are going to have to use ADB on your computer and use the "adb reboot-fastboot" command. If you get in, back up your files, because you're at the event horizon of losing all your data. If your bootloader is 10.6.1.8 youre going to need to flash the latest asus stock firmware from their website.
Sent from my TF300T using XDA Premium 4 mobile app
Lyshco said:
Hi All
I am in the process of flashing Cyanogenmod 11 onto my TF300T however I am in a world of hurt. First I updated to the latest TWRP (2.6.3 -4.2). When i boot up into TWRP it is asking me for a password which I do not know. If I press Cancel i cannot see any contents of /sdcard. Also if I insert a microSD card, again cannot see any contents. TWRP is telling me there is no operating system installed and if i reboot it just comes straight back into TWRP.
I apologise if this question has already been asked but I just cant figure this one out.
Click to expand...
Click to collapse
u should back to twrp 2.5, or u should use scanno twrp.
Tunameltsalad said:
What bootloader version do you have? What helped me was to reboot into the boot loader (using volume down+power, has three options RCK, cold-boot linux, Wipe data [dont ever ever ever wipe data]) and select cold-boot linux (the android guy in the middle) and it would boot back into my ROM. If you cant get in that way, you are going to have to use ADB on your computer and use the "adb reboot-fastboot" command. If you get in, back up your files, because you're at the event horizon of losing all your data. If your bootloader is 10.6.1.8 youre going to need to flash the latest asus stock firmware from their website.
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am using bootloader 10.6.1.3. When I cold boot linux it just continually boots up into TWRP.
Whenever I try to run an ADB command i get "error: device not found". I have installed the android SDK, tried to install the USB drivers but no luck (possible windows 8 issue?).
It doesnt matter if I lose all data on it, i dont keep anything really important on it.
I have rolled back to 2.5.0 TWRP and it still asks me for a password.
I've switched over to my Mac now and have been able to push the CM-11 ROM into the sdcard directory. However when I attempt to flash it, it fails immediately with the log saying.
E:Unable to mount '/system'
E:Unable to mount '/cache'
Lyshco said:
I've switched over to my Mac now and have been able to push the CM-11 ROM into the sdcard directory. However when I attempt to flash it, it fails immediately with the log saying.
E:Unable to mount '/system'
E:Unable to mount '/cache'
Click to expand...
Click to collapse
I had something similar, tried many things but nothing worked so i ended up flashing stock ROM again with fastboot.
If you need help on how to do that just let me know.
rtfm
and more serious:
cm11=android4.4=new PITs(like with 4.1 to 4.2)
solution:
flash scsnnos twrp 2.6.3.0 from his omni thread and it works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
screeny added
Sent from my TF300T using XDA Premium 4 mobile app
Buster99 said:
rtfm
and more serious:
cm11=android4.4=new PITs(like with 4.1 to 4.2)
solution:
flash scsnnos twrp 2.6.3.0 from his omni thread and it works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok this morning I have tried the following:
1. Flashed Scanno's TWRP from the OMNI thread using this command:
> fastboot -i 0x0B05 flash recovery recovery.img
2. Booted up into TWRP, again /sdcard is empty.
3. Pushed the OMNI ROM onto /sdcard using:
> adb push omni-4.4.2-20131218-tf300t-HOMEMADE.zip /sdcard/
4. Went to Install and selected the zip then it immediately fails saying:
Unable to mount '/system'
Am I missing something here? From above i see that i flash 'recovery'. Do I need to flash 'system' with fastboot?
no, but maybe your PITs are corrupt. do you still have an older nandroid backup you could try to restore first?
oh just read that twrp asks for password. is that still the case?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Yep it's still asking me for a password.
What are PITs?
I'm not sure if I have a backup. When in TWRP if I go to restore it can't find any. It's like the whole tablet is wiped. Does this have something to do with not having the ability to mount anything?
Sent from my HTC_PN071 using Tapatalk
Ok, Buster99 I followed your instructions over at this thread and am now back up and running with stock.
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
For me to go to KitKat, can I just flash the OMNI ROM now?
EDIT: Nevermind, I am all back up and running, thanks so much for the help, i was getting a bit worried that I had bricked it!
HELP
So I just tried getting cm11 on my tf300t, i installed TWRP 2.5 and rooted my device, everything went well. I then did a factory reset and wiped cashe. I tried installing then cm11 zip file with no success. I get the message that it failed. And now im on a device with no ROM to boot into and no working ROM to flash on the device.
Since there is a SD card slot on the device, would it be possible to put another ROM on there and then flashing that?
Please help me!
ollemolle said:
So I just tried getting cm11 on my tf300t, i installed TWRP 2.5 and rooted my device, everything went well. I then did a factory reset and wiped cashe. I tried installing then cm11 zip file with no success. I get the message that it failed. And now im on a device with no ROM to boot into and no working ROM to flash on the device.
Since there is a SD card slot on the device, would it be possible to put another ROM on there and then flashing that?
Please help me!
Click to expand...
Click to collapse
in order to install CM11, you need a special TWRP modded for KK: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
You can copy a CM11 nightly and the TWRP onto a SD card and flash from there, or use fastboot.
cmendonc2 said:
in order to install CM11, you need a special TWRP modded for KK: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
You can copy a CM11 nightly and the TWRP onto a SD card and flash from there, or use fastboot.
Click to expand...
Click to collapse
Hello, i have a similar problem, i wanted to install CM11 on my TF300T, i downloaded the latest version of TWRP from their site for the tablet, installed via Fastboot and everything seems to be ok, when i try to flash it (via CM OTA) it ask me for the password and it didn´t mount any data, but when i reboot the tablet it just keep loading twrp and i can't get to fastboot nor adb nor APX, so i have no idea on how to restore or boot back to the OS, or i just bricked the device?
thanks
josush said:
Hello, i have a similar problem, i wanted to install CM11 on my TF300T, i downloaded the latest version of TWRP from their site for the tablet, installed via Fastboot and everything seems to be ok, when i try to flash it (via CM OTA) it ask me for the password and it didn´t mount any data, but when i reboot the tablet it just keep loading twrp and i can't get to fastboot nor adb nor APX, so i have no idea on how to restore or boot back to the OS, or i just bricked the device?
thanks
Click to expand...
Click to collapse
What stock bootloader are you on?
cmendonc2 said:
What stock bootloader are you on?
Click to expand...
Click to collapse
i'm not really sure about the number but it was the latest one from ASUS, i was on the official 4.2.1 ROM when i moved to CM10 a few months ago
josush said:
i'm not really sure about the number but it was the latest one from ASUS, i was on the official 4.2.1 ROM when i moved to CM10 a few months ago
Click to expand...
Click to collapse
When you restart you tablet, and hold the vol down key while rebooting it will give you a bootloader number: 10.6.x.x.x
cmendonc2 said:
When you restart you tablet, and hold the vol down key while rebooting it will give you a bootloader number: 10.6.x.x.x
Click to expand...
Click to collapse
that's the point, it doesn't do anything, is like i'm not holding or pressing it, it just show the ASUS Logo screen and in the top left it says that the bootloader is unlocked as usual, i don't think is a wardware problem because it was working the last time it booted on Android
josush said:
that's the point, it doesn't do anything, is like i'm not holding or pressing it, it just show the ASUS Logo screen and in the top left it says that the bootloader is unlocked as usual, i don't think is a wardware problem because it was working the last time it booted on Android
Click to expand...
Click to collapse
Once it goes to recovery, adb will be accessible. Then follow Buster's recovery method.