Related
So today, I was upgrading from modaco 2.7 to 2.7.1,
after the upgrade (using recover mode and the signed zip file (core chinese)), I did a system wipe and reboot the device with the USB still plugged in my PC, and everything seems to be normal until my pc's tray notification pops up with the "unknown device found" message - i thought it was a little bit odd, so then I waited for the hero to boot up completely - it reboots after showing the HTC logo once, and then it boots normally to the setup wizard (select language, etc);
I then followed the normal procedure of typing all the wifi, flickr, gmail stuff in, and when i got into Rosie, it shows a notification icon on the hero saying "SD Card removed". I can't access the SD card, nor my pc can recognize the hero. I ejected the SDCard and re-insert it but it's not detected either. HTC Sync on the device does not give a notification nor the mass storage notification shows up either.
I tried rebooting into recovery mode, (Hero 1.2.3) and i can see the menus just fine; however, when i try to mount SD card as usb, or flash update.zip or any zip, or fix ext3, or clear dalvik-cache or wipe the sdcard's ext partition, it keeps giving me errors saying
error: run 'whateverprogram' in terminal
when i try to set 'USB Mass storage on', it says "Error enabling USB mass storage! Run ums_enable manually from console.
I then try to login the device using adb shell through window's command prompt, it says device not found as well.
giving up, i tried to reboot teh device into fastboot mode, the PC recognizes the USB device just fine. it's really odd.
Anyway I can do a recovery on this to make these device work again?
p.s. when i try to choose zip file in recovery mode, it says
Code:
"E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
Can't mount sdcard, aborting".
after every reboot (shutdown, start), the setup wizard shows up again as if I have not written anything on my device after any setup.
I can't download anything to run on the Hero as it requires the SD card. I can't flash any recovery images either as again it requires the SD card.
Any ideas??? I'm left with a half-brick now
Update1: using ConnectBot I can login my own device using root,
it shows the following when i run df -h:
Code:
/dev/block/mtdblock3 1700M 157.3M 12.7M 93% /system
/dev/block/mtdblock5 165.8MB 12.8M 152.9M 8% /data
/dev/block/mtdblock4 130.0M 1.2M 128.8M 1% /cache
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Al936 said:
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Click to expand...
Click to collapse
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
kazuni said:
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
Click to expand...
Click to collapse
Update2: the only way that my pc can detect my device as "My HTC" is when i boot it into fastboot mode; unfortuantely there are no way for me to update the device in this mode, so i can't do anything to modify the rom, or to check it using dropbear or any shell client. =\
C:\Documents and Settings\user>fastboot devices
HT97RL900725 fastboot
it sees it just fine.
I wonder if the goldcard method + fastboot update will work or not; let me give it a shot and try to flash it back to 405.5 first ;\
update3: can't. fastboot update is still locked for any rom type.
damn man. its freaking. i am not going to update to 2.7.1 untill this issue is resolved.
still no go.
im left with a half-bricked device that:
1) clean wiped, normal boot, cannot detect SD card nor the Hero is detectable by XP.
2) clean wiped, recovery mode, can't run any of the script except :
Reboot System Now
Wipe data/factory reset
Fix apk uid mismatches
Fix rotate
3) can't download anythign from browser as it needs to save onto sd card.
4) android market doesn't have flashrec so i can't reinstall the recovery image.
wget ftp://myhost/system.img /data/
flash_image system /data/system.img
hope this works
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
packetlss said:
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
Click to expand...
Click to collapse
can't. It doesn't even boot into normal mode, nor boot loop. it just holds at the HERO logo.
I think I have the same problem, i can charge my phone but trying to mount my phone to either my pc or mac it just won't be picked up
tried using RUU with a goldcard, no go. remote not allowed (fastboot flash system system_rel.img, nor fastboot boot boot.img or fastboot flash boot boot.img. no go. sigh.)
now i have a brick :\
wonder if there is any way to go into fastboot mode and flash ANY part of the blocks (device, recovery, or system, if at all).
Some progress: using hboot mode, i placed HEROIMG.zip into the sdcard and it loads successfully. it works! and im now rolled back to official 2.7.405.5; however, the USB and the sd card is still dead ;\
I guess I'll be bringing it back to HTC to see if they would do anything about it (fortunately It's now back to stock recovery and 2.74.405.5)
I managed to do the same thing, i'm hoping the tmobile will replace my phone
hi all,
I am having the same issue... what I don't understand is: it has to be a software problem, because, from what I've read, everyone of us have been installing radio and firmware updates to the htc hero, and since some of these updates the USB and sdcard mounting is not properly working... I believe it's not possible to break a USB port just by installing software...
so there should be a way to fix this other than sending the phones back... If anyone has any suggestion I can try it on my phone
cheers : )
I know it's weird! Funny thing is, official updates includes radio + recovery + pretty much every part of the rom is being re-flashed (including hboot, from what i understand); how ever, ONLY in hboot mode, the device is recognized properly as "Android USB" by windows.
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
dennis333 said:
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
Click to expand...
Click to collapse
I tried this but it didn't seem to work for me, so I just put the official rom update and sent the phone back to my network saying that it was broken, now i've gotta wait for another 2-3 weeks to get my phone back , but i'm hoping they'll give me a new phone as i did kinda drop it and there two scuff marks on it
hello dennis333,
today I tried going from 2.8 to the HTC generic ROM you told, and then to 2.5. no results.
I also installed the official HTC / Orange Rom update, which I have now. It has improved a bit because now when I plug the USB cable the PC detects something, but it does'nt work... it says 'unknown device' (tried this on two computers)
when I boot to fastboot ( BACK + POWER BTN ) my computer detects Hero ok (My Htc)
I really don't know what else to try...
I saw another post from someone who had the exact same problem and got it fixed by installing SPL and ROM from fastboot menu
http://forum.xda-developers.com/showthread.php?t=556038
I tried it too, but when trying to use the SPL zip file he says I get an error ( I guess it's because he has a T-Mobile and I have an Orange Hero)
[update]: I finally got the SPL to flash correctly and then installed a modaco 2.8 ROM, but I still cannot connect the Htc Hero to the PC via USB.
regards
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
Hi guys, I know this is the worst question and nobody likes it when a noob is struggling... I have a gnex and for some stupid reason I booted into recovery (clockworkmod 6) and formatted everything, I can plug in the phone to PC but it does not allow me to browse the device and copy files to it so that I can flash another ROM. I have installed Gnex toolkit and tried pushing files that way, and it says that it works, but if I select "choose file from SD card" to flash then it just says no files were found. I am stuck now, no idea what to do. Any assistance would be greatly appreciated!?
Obviously the phone does not have a SD Card so all the solutions I could find on Google is useless for me...
do not use toolkit!
you have 3 options by order:
1- push custom rom manually (see my sig. gnex tips) be sure that you have cwm 6.0.2.3 or 6.0.3.1 :good:
2- flash stock images via fastboot (see efrant sticky thread) :good:
3- flash stock images via odin (see my sig.)
P.S. next time use search button. there are plenty of threads with the same request
sounds like you didn't install the correct drivers, reinstall the correct drivers and your device should be recongnized when you plug it into the computer and try to transfer over files, just use google to find what you need the info is all out there and you should be able to find it very quickly instead of posting questions and waiting for answers
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
kevs888 said:
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
Click to expand...
Click to collapse
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
graphdarnell said:
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
Click to expand...
Click to collapse
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
Fastboot page
graphdarnell said:
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
Click to expand...
Click to collapse
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
kevs888 said:
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
Click to expand...
Click to collapse
If you're comfortable using the ToolKit, you don't need an OTG cable. Connect your tab to PC, fire up ToolKit, complete all the prelim BS, then flash the bootloader from TK. Do not use TWRP for this. To do this, open the ToolKit folder in drive C:, locate the folder therein for zips, place the zip files (4.05 bootloader; TWRP; or custom roms) in there, and start to install. I am talking off the top of my head. But give me a few minutes to check the Kit again, and I'll give specific instructions. Bear with me, as I'm on Linux at the moment and therefore cannot start ToolKit (which is in Windows).
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
graphdarnell said:
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
Click to expand...
Click to collapse
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
kevs888 said:
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
Click to expand...
Click to collapse
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
graphdarnell said:
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
Click to expand...
Click to collapse
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
kevs888 said:
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
Click to expand...
Click to collapse
I'm glad you got it working again. Sorry you had to make a trip to the store. You should've waited for KT to switch the tab to TWRP 2711 for you. But it was not a waste of time anyway.
Hey lads!
I am trying to root my HTC One M8, so I can get a finer options for sounds (and other advantages, aswell). I found this post https://forum.xda-developers.com/htc-one-m8/help/how-to-root-htc-one-m8-android-6-0-t3420748 about rooting an M8 with android 6.0. I'm writing this post, because I don't want to screw it up, so it seemed better to ask for help, before I do something stupid and brick my phone. I tried searching the forum, but after opening like 10 tabs, I lost my way. (I am using Windows 10, legit)
So, this is what I did:
1) Downloaded the Android Studio.
2) Via the studio, I downloaded the 6.0 platform.
3) And here is my first block: tried to install ADB, via Universal Naked Driver: I downloaded the ZIP, unpacked it, and while my phone was connected, tried to update its driver via the Device Manager. I got a message that it's up to date, and even tho I picked the 'I have disk' option, it wouldn't do anything. Now, I downloaded MiniADB v_1031, and when I ran the cmd from here, I could see my device with adb devicelist. I also installed HTC Sync, and used the driver installer from adbdriver.com, and it showed that I have the needed driver.
4) From the folder where I have unpacked miniadb, was able to run adb devicelist, and adb bootloader reboot aswell. But from that point, even tho I enabled developer options in my phone, and USB debugging aswell, my PC can't see the phone, only if I reboot to normal mode. When I am in fastboot USB, adb devices just says 'list of devices' and a blank line under it.
5) Tried to unlock the bootloader, and I got my identifier token. I am good to go then, I have every driver what I need for continuing from here?
5)b) Edit: Seems like I managed to unlock the bootloader.
---------
So if I understand it well:
From now on:
---------
6) Download the EU version of TWRP 3.0 from here (I am from the EU)
7) Use the cmd 'fastboot flash recovery twrp.img'
8) The site mention a key-combo to prevent the phone to go back to basic recovery, do I need this?
9) Do a backup via TWRP (is it going to be a simple option in the recovery? How big SD card do I need? Atm, I have 12 Gb one, gonna buy a 128 one in like 1-2 month)
10) Copy the SU.zip to my SD card and use a flash option in the recovery?
Sorry for any dumb question, I'm kinda scared bricking my phone, but at the same time, I would like to get the advantages of rooting.
So anyway, did I miss out on any step, screwed up anywhere, or smth like this?
Any help is much appreciated!
My comments to your steps/questions:
4 and 5) adb and fastboot are two different, but related interfaces. Don't feel bad, it's a common mistake to mix up the two (adb and fastboot). You'll really only need fastboot for rooting the phone. The step to "adb reboot bootloader" in the TWRP install instructions can alternately be done without that command, using the button combo to get to bootloader. But I think you must have figured that out by now, if you managed to unlock the bootloader.
In summary,
adb: needs USB debugging on in phone settings, only works when phone is booted in OS or alternately when booted into TWRP (last part obviously doesn't help, if you haven't installed TWRP yet).
fastboot: only works in bootloader-fastboot mode (will not work in OS or TWRP), does not need USB debugging on in phone settings.
6) The options are for download mirror locations (US vs. Europe - literally just where the download's server location is located), and do not specifically refer to different TWRP versions. The same TWRP version works for both US and Euro M8 models. What you downloaded is fine, so my comment is just FYI.
8) No, you shouldn't need this. I believe this comment refers to newer devices, and not specifically to the M8. I literally think the TWRP team has copy/pasted this statement to instructions for every device on their website, whether it applies or not.
9) Yes, this is a clear option once booted into TWRP recovery. Literally, on the TWRP main screen, you will see a big button labeled BACKUP. Tap it, and select system (ROM or OS) and boot.img, and also backup data if you like. The backup of system and boot.img will take around 2 GB. The backup of your user data might be much more, depending on your apps, etc. Although, if you just unlocked the bootloader, the phone should have been wiped, so you may not have much (if any) user data to backup.
10) While SuperSU 2.76 (mentioned in the thread you linked) should work fine, I would suggest using the latest stable version 2.79 from here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Just put it on the phone, boot into TWRP, select INSTALL, select SuperSU 2.79.
---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------
Rivyan said:
Sorry for any dumb question, I'm kinda scared bricking my phone, but at the same time, I would like to get the advantages of rooting.
Click to expand...
Click to collapse
Don't worry, you won't brick the phone (permanent damage) by unlocking the bootloader, custom recovery, root, etc.
Anything you do is recoverable/reversible, even if something goes wrong (especially if you make a TWRP backup of your current stock ROM before rooting).