I have unlocked my bootloader via htcdev.
I have flashed CWM, CWMT and TWRP. I could never get TWRP to boot, but I can get CWM and CWMT to boot.
Once in recovery, I go to choose zip to install and I can only browse a few locations such as /0, /audio /Android /video. There are maybe like 6 folders in total. I cannot browse to sdcard or mount sdcard. How can I get my SuperSU zip into one of these folders?
Or....why is it only mounting /system?
I even tried fastboot flash boot recovery.img (DON'T TRY THIS AT HOME FOLKS) so I would boot st8 into recovery and it still mounts the same folders.
msimindlessmsi2 said:
I have unlocked my bootloader via htcdev.
I have flashed CWM, CWMT and TWRP. I could never get TWRP to boot, but I can get CWM and CWMT to boot.
Once in recovery, I go to choose zip to install and I can only browse a few locations such as /0, /audio /Android /video. There are maybe like 6 folders in total. I cannot browse to sdcard or mount sdcard. How can I get my SuperSU zip into one of these folders?
Or....why is it only mounting /system?
I even tried fastboot flash boot recovery.img (DON'T TRY THIS AT HOME FOLKS) so I would boot st8 into recovery and it still mounts the same folders.
Click to expand...
Click to collapse
I had to flash TWRP twice before it took. Don't know why. I also had some issues with rooting so I let TWRP do it for. Figured since they released their new version first for the ONE it should work and it did. All you have to do is go to reset once you get into TWRP and it will ask if you want to root. Pretty nifty if you ask me
LOL guess what I just realized?! I have the Sprint version, which has a different TWRP version and forum LOLZ!
Related
Running 2.3.3, build number is CL 49208, using a Mac. Unlocked bootloader with fastboot. Used recovery-RA-passion-v2.2.1. Put the su-2.3.6.1 on my phone. Finally got it to reboot in recovery. Installed CM7.0.3. Oh, and I bought this phone in China (it's legit). Also, I used info from lots of sources before I finally found a recent post here that suggested the su zip file. One of those things I put in my sdcard is Radio_20100203_2_Signed_PASSION.img. Don't know if that helps. I couldn't find a more updated radio image.
The plan is to install CM7 so I can run openvpn.
It stops and cycles through the CM7 load screen -- turquoise android on a skateboard with an arrow circling around. Goes no further.
What did I miss? How do I fix it? Thanks.
Sounds like your in a bootloop.
Did you flash GAPPS also?
Here's more infos for radio, ect...
http://forum.xda-developers.com/showthread.php?t=744605
Has happened to me before. I removed the SD card and scanned it for errors on my PC. Worked after that. HTH.
Sent from my Nexus One using XDA App
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
cat3rpill3r said:
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
Click to expand...
Click to collapse
They make an adapter for micro sd card t ofit a USB port.
You can try new radio but If it's bootlooping I think your problem is elsewhere.
Did you check MD5SUM of the ROM before flashing?
Fortunately, my neighbor has a plethora of microsd adapters.
I did not check the sum. I read a few suggestions about doing that, but I couldn't figure out how, so I just trusted that what I had was fine. Lesson learned.
Let me get this straight: I need to put the GAPPS image on the sdcard AND flash the GAPPS image from fastboot? If I do update the radio image, do I need to reinstall CM7?
Put cm7 rom and gapps on sd card,
boot into recovery and flash rom then gapps, reboot.
Its highly recommends you do radio via fastboot.
To check md5sum, you can use one of the many free app from market.
Ok, ran checksum in fastboot. Not really sure what I'm looking for, so I'll just post what happened. In every case except gapps and su, the numbers returned were the same on the sdcard as in the tools file on my mac. Gapps and su are only on the sdcard.
For the CM7 zip, it returned: MD5(pathtofile)= 98d06d6a58c7de87d40269bfe0ae0e7b
For the RA img: 3def709ab1c9e051a92a1c8b1504a36a
For the Radio img: 310d85c4998163818f7dcdef730c2a12
For the gapps zip: 2f6a93654d1cfe191ff709b360ad60fc
For the su zip: b23147cb55eba3ae32a996a913fa54ea
I'm too new to the forum to post the link where I'm getting my instructions.
The CM7 version is update-cm-7.0.3-N1-signed, the RA is recovery-RA-passion-v2.2.1, the radio img is Radio_20100203_2_Signed_PASSION (the updated radio link you posted had removed the radio img because of some sort of violation), and gapps zip is gapps-passion-ERE36B-2-signed.
Still having the bootloop problem. I tried to find the most updated versions of everything I could. Is there a compatibility issue somewhere?
Another thought:
Do I need to flash the su zip from my sdcard in recovery? I don't know what that will do, so I haven't tried it yet.
There are a couple of files that Amon-RA suggests I delete in order to prevent calling the stock recovery:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Any idea how I can check for and delete these using fastboot via mac terminal?
You can't delete them from fastboot. Use fastboot to boot off the new recovery and delete them in there through adb.
Code:
fastboot boot recovery "c:\location\to\recovery.img"
Can you be more specific? I use fastboot to flash the recovery image, and when I'm in recovery on the phone, I use adb from my computer? Or I can access a command line in the phone?
Well, you use fastboot to flash the recovery. Then you use the command I posted below so you can boot directly into that recovery. Once in there, you use adb on the computer to go into the phone, mount the system partition (which can be done under the mounts and storage menu in recovery) and then find those files and remove them.
But you really only need to delete those files if you want to stay running stock Android. If you have a custom recovery on the phone, that is all you need to install CM, and CM doesn't contain the files that revert the recovery back to stock.
Just got it to work. It was, in fact, a compatibility issue. The gapps zip was for a different version. I found a different zip (for Gingerbread) at: http://goo-inside.me/gapps. If you have Gingerbread, choose a zip with gb in the name.
I downloaded the new 2.1 TWRP and installed it using CWM I discovered that on the moboot menu it still reads CWM but boots TWRP. I would like to keep both on the tablet for now. Any ideas on how to install CWM and have both TWRP and CWM show up on the mobbot menu? Thanks.
buffalo_guy said:
I downloaded the new 2.1 TWRP and installed it using CWM I discovered that on the moboot menu it still reads CWM but boots TWRP. I would like to keep both on the tablet for now. Any ideas on how to install CWM and have both TWRP and CWM show up on the mobbot menu? Thanks.
Click to expand...
Click to collapse
Fastboot CWM again.
I did it last night and now I am stuck with both. I wanted only CWM but I can't get rid of TWRP. When I hit reboot to recovery, I go to TWRP but I can choose CWM from Moboot.
Sent from my Galaxy Nexus using xda app-developers app
Solved with another method
SOLVED: I since have learned that TWRP replaces CWM and as a convenience to the user and renames TWRP so it appears as CWM for purposes of going into recovery. There were a number of solutions to add back CWM. The one I used requires a file manager with root access. I extracted the CWM image from the zip file and copied it into the boot directory and renamed it uimage.CWM2. I reset the permissions to match the the other moboot images found in boot. Once the tablet is restarted moboot inventories the images found in boot and adds them to the menu. For the time being I now have both TWRP and CWM. The only caution is to make sure you have enough room in the boot directory. You can also remove entries from the moboot menu by deleting image files. Proceed with caution and always backup before proceeding.
I'm trying to follow this to root my stock ROM on my HTC One (Sprint):
http://forum.xda-developers.com/showthread.php?t=2173870
I unlocked my boot loader and I can boot into TWRP recovery. My problem is, I cannot find the Superuser-3.2-RC3-arm-signed.zip file when I'm in TWRP recovery. I downloaded that file from http://androidsu.com/superuser/ from my phone and I can see it in the Download folder but when I'm int TWRP recovery, I see a totally different list of subfolders under /sdcard:
audio
GPU
mms
TWRP
video
weather
In the YouTube video, after clicking on Install in TWRP recovery, the Download folder shows up but not in my phone. And when I connect my phone to my PC (Windows Vista Home Premium), I don't see any of the directories above under /sdcard but I see the Download and the Superuser-3.2-RC3-arm-signed.zip file.
I can't seem to find a solution.
From that link, on page 25, Radikaal posted a similar problem but no one has responded:
Im getting "different" sdcards when connected to computer and when in recovery, so when i connect to computer i can put in files but they won't show in recovery, only files that i put in like 2-3 days ago. Anyone got an idea why this is happening and how to fix it?
I also tried CWM (Classic and Touch) and CWM2 but all of them seem to just shut down my phone when I try to boot in recovery. At least TWRP can boot in recovery.
I've backed up all my app and data with Titanium Backup Pro which requires root so I really need to root my phone so I can restore all my apps and data from my old EVO 4G to my new HTC One.
Any suggestions would be appreciated.
I figured out what I was doing wrong - I was using the wrong TWRP recovery file. Apparently, there is a separate file for HTC One on Sprint USA (which is what I have).
The file I was using before was openrecovery-twrp-2.5.0.0-m7.img but the one for Sprint USA is openrecovery-twrp-2.5.0.0-m7wls.img (note the extra 'wls'). Once I flashed the correct recovery file and booted into recovery, it listed my Download folder and I was able to install the SuperUser image successfully. My stock ROM is now rooted.
To see if you device/carrier combination also requires a different recovery file:
Go to teamw.in/project/twrp2
Click on "Get TWRP for your device" (in the upper right corner)
Enter your phone model
For HTC One Sprint USA, the download link is:
teamw.in/project/twrp2/171
Then click on the link called "Download the newest .img file from here". Even though that link is under the "Download - ADB / Terminal method" section, you can use the same file for the Fastboot method.
Hi guys, I've been using TWRP for a long time, but this one is a bit of a head-scratcher for me. I'm running stock Android MMB29S on my N6, unlocked bootloader, and unrooted. I decided to install TWRP 2.8.7.1 and then root it with Beta supersu 2.66. The fastboot flashing of TWRP went fine the first time, and I opted to leave TWRP read-only. But I didn't install supersu right afterwards. Rather, I rebooted into system first, and downloaded supersu. When I attempted to reboot into recovery again to flash supersu, I'm finding out that stock recovery has overwritten TWRP. Ok, no problem, I re-flashed TWRP, but this time I allowed it to modify the system (instead of read-only). Now, I'm unable to see anything under /sdcard or any of the other folders when I go to flash the zip. Under the "Mount" Menu, I see that only "cache" is checked. Didn't want to mess with anything there.
Rebooting into system now gives me the "Your device is corrupted..." spiel, which I'm not concerned about, but I really do need to be able to see files in TWRP. Would re-installing TWRP be an option or even a different version of it?
mount system. if its still empty after that, use twrp to locate the right place in the filesystem. yes, like a file explorer app twrp can act
The solution to my problem was actually as simple as just removing the lockscreen passcode. I was wondering why TWRP was asking for that in the first place. Once I removed the lockscreen PIN and went back into TWRP I was able to see all the files. Happily rooted now. :good:
Dear friends I need help!
I've tried to flash my tablet but I've got an error message while flashing Katkiss 6.0
What I did:
downloaded Rom.(md5sum is OK)
my bootloader is ww_epad-11.4.1.17-20140711
recovery CWM v6.0.5.0
previous rom zoombi pop
/format data
wipe data factory reset
install zip from sd card. (from internal storage or micro sd card)
And I have got the following error (in attachement)
Please help, my tablet boot only recovery now.
Thanks in advance for the help
trying to boot in fastboot mode when children let me try that...
Edit: fastboot ok.
I placed the the files
KatKiss-6.0_TF701T_033.zip
open_gapps-arm-6.0-pico-20170120.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
In
C:\Program Files (x86)\Minimal ADB and Fastboot
ok I don't know how to proceed now.
Seems I cannot change the recovery from CMW to TWRP,
My bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30
So how can I do?
I there a way to upgrade the bootloader to be able to install TWRP?
Or should I Flash the custom rom from fastboot?
My TF701 in not booting anymore.... only bootloader and recovery CMW
the positive thing is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
15C3E10090400000011FA8580 fastboot
Please help
I have been able to flash CROMI X (unfortunately with strong battery drain) so CMW is able to flash but for some reasons not Katkiss 6.0.
I have been told that my problem is not ROM related... So it is recovery related?
What is the better option to get katkiss on my tablet? Flash the recovery to get TWRP even if my bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30????
There is a technical reason about this warning?
Edit: I found this on an old post:
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
Click to expand...
Click to collapse
Would this method work to get the latest stock rom from Asus?
Got your PM and will try to find some time at work today. Hang in there and don't do anything to make it worse
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
berndblb said:
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
Click to expand...
Click to collapse
Thanks a lot to take time to help me.
Will try that tonight and I'll let you know the result.
Thanks a lot!
It was just like you said.
I had to format to ext3 and ext4 because I had errors.
Battery seems to be very good. Just the screen display is very white, needs color saturation and contrast I guess...
Thanks again you save my tablet.
Now that's what I like to read! :cyclops: