Related
Hi Guys,
This is my first post and its only in desperation.
I have a HTC Desire. I upgraded to 2.3.3. After reading how unrevoked doesn't work on this, I created a Goldcard and managed (all on my own) to turn the phone to s /off.
Now Im stuck, many threads explain the process in different ways (as most of them related to pre 2.3.3). So do I load a custom rom onto the Goldcard and flash from there? Also, do I need to install a rollback program first or after?
Really sorry for starting a new thread, but you will see by my profile, Ive been at this for two days .
[Takes cover for flaming session]
im no expert, indeed i have only rooted only a few days ago. I was lucky to have a unlocked phone.
I guess to help the more expert in here is maybe if you detail what now shows on the Bootscreen, eg VOL Down + Power button.
Have you now got a custom Recovery installed, the common one is Clockwork Recovery?
I believe, that Revolutionary.io is able to handle 2.3.3... anyway it what i used to Root, and it installed CWR and from recovery i was able to point it to the ROM zip file and it all installed fine.
Now i didnt need a goldcard so i cant really say if there some additional steps involved first.
u need revolutionary to make s-off, then u can root it flashing the super user zip from the documentation, u don't need the goldcard, it will also install a custom recovery
official revolutionary site: http://revolutionary.io
official revolutionary doc: http://unrevoked.com/rootwiki/doku.php/public/revolutionary
complete guide: http://wiki.rootzwiki.com/index.php/HTC_Desire
don't worry about it, we are all here to help so let me explain some things.
A goldcard is a tool that allows you to use an unbranded RUU on a branded phone, effectively de branding it, as the RUU (Rom Update Utility) ignores the CID (Customer ID) of the device.
To flash different ROM's, you will need to flash something called "recovery", there are many versions, each arguably, or questionably better than the next. In order to flash recovery, you need to download a recovery image.
Download the above file, rename it to "recovery.img" for simplicity, and put it in your C:\
now the flashing process, there are many tools and utilities you can use, but for now, let's just use command prompt as it does not require you to install anything, just as long as you get the commands right. (you'll also need the file I attached [fastboot.exe], just unzip it into your C:\)
Ok, once you've done the steps stated above, turn your phone off. With it off, PRESS AND HOLD the RETURN/BACK key on your phone, and while still holding it, press the POWER key. This will boot you into "fastboot" mode.
Plug your phone in via USB to your PC.
Open command prompt (start menu, accessories, command prompt)
type the following:
Code:
cd\
fastboot flash recovery recovery.img
Congratulations, you have now flashed recovery. This now allows you to flash ROM's.
Put whatever ROM you would like on your SD-CARD, I recommend CyanogenMod (for No Sense) or MIUI (For something completely different) or RCMixS for Sense (sense 2.1) (all comes with preference)
To boot into recovery, boot into bootloader, (while powered off, press and hold VOLUME DOWN, and POWER), use the volume keys to navigate, and the power key to select. Navigate to RECOVERY and hit power.
When you are booted into recovery, before flashing a new rom IT IS VERY IMPORTANT TO BACK UP!!. You can do this in the "backup and restore" menu.
Once you are backed up, go to "mounts and storage" and use "format [partition]" option, to format boot, system, and userdata.
Then, go to "flash zip from sdcard", and find the ROM you have chosen, and wait for it to finish flashing.
Good luck to you
Wow guys, cant thank you enough
I actually had a small amount of brain oozing out of my ears at one point Thanks for the custom info, like I said, the tuts are excellent, but being new, they are a bit irrelevant if you half way through the process. Trust me to upgrade to an 'unrootable' system a week before I decide to root it
I will remove my flame-proofing now
Thanks again
PP
@bortak
Thats only when he have s-off...If i not wrong he have the stock 2.3.3 with no root an s-on
EDIT: nevermind..i didn't read the post properly..
Hi guys
Im getting an error on fastboot :
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
Click to expand...
Click to collapse
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP
palm_pilot said:
Hi guys
Im getting an error on fastboot :
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP
Click to expand...
Click to collapse
Okay, put "fastboot.exe" in c:\android-sdk\platform-tools\
and then before issuing fastboot commands, type:
Code:
cd c:\android-sdk\platform-tools\
this *should* fix it for you
Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
error: cannot load 'recovery-clockwork-2.5.0.7-bravo.img'
Click to expand...
Click to collapse
Any ideas fellas?
PP
Maybe download 'recovery-clockwork-2.5.0.7-bravo.img' and then select that from unrevoked ?
palm_pilot said:
Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
Any ideas fellas?
PP
Click to expand...
Click to collapse
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error
BigMrB said:
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error
Click to expand...
Click to collapse
Hi
Im using :
\cd (enter)
Then :
android-sdk\platform-tools\fastboot flash recovery recovery.img
I have revolution installed, can I flash from within this ie. loading the image to the SD and running from within the phone itself?
ATB
PP
cd C:/android-sdk/platform-tools/
fastboot flash recovery recovery.img
(providing you changed the name of your recovery to recovery.img)
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
So, there is actually a WORKING CWM 6.0.28 recovery, with an installer that runs from a root shell.
All features work for me. I'm able to mount my internal SD as USB, do a CWM backup, navigate through menus, etc
I didn't create it, but since it is verified working on this tablet, and I had such a difficult time finding a working CWM for this device, I thought I'd post the link and which file to grab.
Thread: CWM 6.0.2.8 for Allwinner A10 & A13 Tablets - v2a
http://forum.xda-developers.com/showthread.php?t=2189640
Download the file:
cwm6028-a10-10part-v2.zip
This is a 10 partition AllWinner A10 device, so that's the zip file we want.
NOTE: This "guide" assumes you know how to copy files via ADB, use basic Linux commands, and
Manual Install Method (Known Working):
Extract the files, copy the two .sh files and the recovery.img file to the device using ADB (probably /data/local would be a good spot). Make the .sh files executable (chmod 777 *.sh), and run install-recovery.sh
It will install the recovery for you. Takes about 10 seconds or so.
The reboot-recovery.sh script reboots to recovery. Go figure This device has an interesting way of rebooting. Check out the guts of the script for the command if you're interested. BTW, don't use any 3rd party utilities that reboot the system. It will probably end up in a factory reset of your device. I did that by accident... more than once.
Automatic Install Method (Might Work, Worth A Shot):
I'm not sure if the stock recovery will flash the ZIP file, but I would give it a shot before trying the above method. If it does let you install it, then it's a MUCH quicker way
Other Information:
Boot to recovery manually by powering the device off (holding the power button for 10 seconds). Then holding Volume Down & Power until it powers on, then release the Power button while still pressing the Volume Down button until the recovery boots.
Sorry for the scattered post. I'm just happy to have a working CWM and wanted to share it.
I can confirm that the stock recovery is able to install cwm6028-a10-10part-v2.zip from external memory. Quick & painless.:good:
AyDee said:
I can confirm that the stock recovery is able to install cwm6028-a10-10part-v2.zip from external memory. Quick & painless.:good:
Click to expand...
Click to collapse
unfortunately, this didn't work for me. I'm not sure what hardware version i have but the lot number is 120915-10205815
HELP
I have the mach speed trio and i accidentally screwed it up the only thing that happens when i turn it on is the android in the box icon appears, i rooted using the root toolbox and the run me .bat file on a windows pc. normal mode activated and it completed successfully now the only thing appearing on the screen when i power on is the logo, this happened after factory resetting it in cwm after the zip file in the guide to installing choco ics on it and cwm, the only thing that was on it then was the bootloader. is there any way for me to fix this, it is very urgent please pm me is you have specifics, it is the mach speed trio model stealth pro with ics 4.0.4 running on it before this happened and also when i tried to put the stock rom on it, it wouldn't let me.
Hey XDA Members
I know there has already been similar posts to mine on XDA as I've worn out the search button on google trying to find a solution to my problem, with no avail. So I thought I would leave a description of my own situation and see if a more tech-savvy individual could kindly help me out...
So yesterday I decided it would be a good idea to unlock my bootloader & root my device simply because I wanted to remove all the bloatware which HTC 'generously' crammed into the One X. Unlocking the bootloader was simple enough following the instructions provided. However, rooting my handset was not so effortless. The root was ineffective & I got stuck with yet another unwanted app called SuperSU! (An error message regarding missing binary codes appeared every time I tried to open the application) I tried uninstalling via both settings & google play before finally factory resetting my phone. None of these methods worked
At this point it suddenly dawned on me someone so unenlightened in the art of software development or anything android related shouldn't being toying with stuff he can't afford to break! But I figured it was too late to turn back now and continued in my moment of intellectual darkness...
In my bewildered state I accidentally 'wiped system' using CWM and now I have no iOS. My HTC will only boot until the 'quietly brilliant' slogan appear's & no further. When I connect my phone to my computer via USB I can not access the removable storage device, a removable disk appears but when clicked I am prompted to 'insert removable disk'. I am lead to believe from reading related threads that if I had access to my phones storage then installing a new iOS would be relatively straight forward. Also trying to mount in CWM just retrieves an error message reading 'CWM unable to open ums lunfile (no such directory exists)'. Where do I go from here?
Any help would be much appreciated :fingers-crossed:
Flash a newer recovery, try the latest Philz touch recovery then you should be able to mount sdcard and flash a rom
Hope it helps
if tthe above suggestion doesnt work, try this
http://www.hackmyandroid.com/comprehensive-guide-on-unbricking-the-htc-one-x/4216
I recommend you flash the latest TWRP recovery since it gives you access to the phones sdcard, if your staying stock/near stock OS you can check http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html download the Download stock odexed 4.18.401.3, and just flash it in recovery or you can download w.e custom OS you like and flash it the same
Hope it helps
Thank you both for your replies :good:
m.jordan, I tried to flash TWRP onto my device (3 different versions in fact) but once entering recovery mode I was prompted to 'swipe screen to unlock' which wasn't possible because I can only use the volume controls and the power button. After that I downloaded the latest version of CWM which enables me to both use the control buttons & touch screen. I downloaded the 'stock odexed 4.18.401.3' although I have no way of flashing on my device...
I tried the method in the link you kindly provided and followed each instruction carefully. After re-unlocking my bootloader (does it matter whether the device is locked or unlocked when mounting USB storage in recovery mode?) & flashing CWM I downloaded the odexed 4.18.401.3 extracted boot.img & flashed that too. On the website you shared it then prompted me to 'mount usb storage' & my device should now be showing as 'clockworkmod' so I would be able to place the odexed 4.18.401.3.zip into the folder and then flash my handset. Unfortunately I still have no removable disks showing on my PC
My HTC One X does not have removable storage (I suppose you already knew that) & I havn't been able to get my PC to read a removable disk since the day I wiped the system.
If only I could get my computer to show an 'adb device' I'm sure this would be so much easier! I don't suppose you would know anything about that? when I use cmd prompt 'adb device' most of the time it just returns:
adb out of date. killing...
daemon started sucessfully
list of attached devices
Nothing ever shows under attached devices
Nogotaclue, my next step it to try Philz recovery & see where that takes me, i'll let you know how that goes (Although I fear it will just have the same outcome as the rest & not be able to read an sdcard)
Thanks again
well it seems if you could follow the steps on that link, then your pc is recognizing the device so there is hope. If TWRP isnt working then cool. On either the CWM or Philz there is an option called adb sideload rom, if you can't access your SD card you can always sideload and install the rom using either One_X_All-In-One_Kit or WinDroid Universal HTC Toolkit v1.1, made them available here https://www.dropbox.com/sh/fv9fun4x2c4dk2l/AABhNHvlpPUvDXUWYK5PJNhpa?dl=0
Once in recovery I believe its under the install option, you have the option to install rom from sdcard and sideload rom, just select sideload. once thats done, open either the all in one or windroid with your device connected to your pc (i recommend the all in one), select the option to sideload, and cross your fingers that it works
ProdiJay said:
Thank you both for your replies :good:
m.jordan, I tried to flash TWRP onto my device (3 different versions in fact) but once entering recovery mode I was prompted to 'swipe screen to unlock' which wasn't possible because I can only use the volume controls and the power button. After that I downloaded the latest version of CWM which enables me to both use the control buttons & touch screen. I downloaded the 'stock odexed 4.18.401.3' although I have no way of flashing on my device...
I tried the method in the link you kindly provided and followed each instruction carefully. After re-unlocking my bootloader (does it matter whether the device is locked or unlocked when mounting USB storage in recovery mode?) & flashing CWM I downloaded the odexed 4.18.401.3 extracted boot.img & flashed that too. On the website you shared it then prompted me to 'mount usb storage' & my device should now be showing as 'clockworkmod' so I would be able to place the odexed 4.18.401.3.zip into the folder and then flash my handset. Unfortunately I still have no removable disks showing on my PC
My HTC One X does not have removable storage (I suppose you already knew that) & I havn't been able to get my PC to read a removable disk since the day I wiped the system.
If only I could get my computer to show an 'adb device' I'm sure this would be so much easier! I don't suppose you would know anything about that? when I use cmd prompt 'adb device' most of the time it just returns:
adb out of date. killing...
daemon started sucessfully
list of attached devices
Nothing ever shows under attached devices
Nogotaclue, my next step it to try Philz recovery & see where that takes me, i'll let you know how that goes (Although I fear it will just have the same outcome as the rest & not be able to read an sdcard)
Thanks again
Click to expand...
Click to collapse
Man flash Philz 5.15.9 mount your sd card and you are ready to go only in this version sd card mount work no TWRP no CWM exactly Philz 5.15.9
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.