Related
Ok so i need help. Take into account i'm a noob at this. I've recently rooted and boot loader unlocked my Desire S. All was going well until i proceeded to install a new rom. I fancied cyanogenmod so i downloaded it via rom toolbox and then using rom manager tried to flash CWM which seemed to work, then when i tried to boot into recovery a red triangle would appear and then when i held the volume down and power buttons together the menu would come up and i would select install from sd card and it would say error, then boot up as normal. Now this was yesterday and in all my frustration and tiredness i played around a bit and tried everything i could to sort the problem out but as expected, that did not help, as i now have an even bigger problem. Every time i try to go into recovery mode (via rom manager and fastboot) it freezes on the HTC screen with a white background. It also does this when i try and restore factory so i'm really stuck. Have i bricked my phone? It still works as normal if i take the battery out and turn it on, it boots normally and functions normally. Any help will be very much appreciated thanks.
As your hboot is unlocked, you have to use the fastboot command in order to flash a new recovery. Rom Manager can't replace your recovery.
yaonos said:
As your hboot is unlocked, you have to use the fastboot command in order to flash a new recovery. Rom Manager can't replace your recovery.
Click to expand...
Click to collapse
Just tried this, in cmd it says "c:\FASTBOOT>fastboot flash recovery CWM.img
sending 'recovery' (3115 KB)...
OKAY [ 0.993s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.996s"
Yes, you need adb and fastboot tools installed first, there is a thread in the guides section of the INDEX that well tell you how to do this, see link on my sig
Sywepd form my DsereiS
ben_pyett said:
Yes, you need adb and fastboot tools installed first, there is a thread in the guides section of the INDEX that well tell you how to do this, see link on my sig
Sywepd form my DsereiS
Click to expand...
Click to collapse
I followed your guide and it all seemed to be working, i tried flashing it using fastboot again and the same error message came up, so i moved the .img file to the android-tools folder and still the error message came up, not sure what i'm doing wrong
you shouldn't remove the battery under any circumstances.....
Use fastboot command to attempt to reboot the device or try three button sequence of volume up & volume down then power button
What does your boot loader screen look like, versions etc?
Sywepd form my DsereiS
ben_pyett said:
you shouldn't remove the battery under any circumstances.....
Use fastboot command to attempt to reboot the device or try three button sequence of volume up & volume down then power button
What does your boot loader screen look like, versions etc?
Sywepd form my DsereiS
Click to expand...
Click to collapse
i managed to use 4EXT and installed cyanogenmod, it's currently repeating the loading screen with the arrow and the android animation on the skateboard is this normal for the first time booting up?
First boot could take five to ten minutes.
If your htcdev unlocked then you'll need to separately flash the new kernel (boot.img) through fast boot
Sywepd form my DsereiS
I've managed to get it all working and I flashed gapps, now every video and even my camera does not play properly it's very choppy even though the sounds works fine. Is this a flash problem?
Sent from my HTC Desire S using xda app-developers app
Chrizz77 said:
I've managed to get it all working and I flashed gapps, now every video and even my camera does not play properly it's very choppy even though the sounds works fine. Is this a flash problem?
Click to expand...
Click to collapse
What version of CyanogenMod and what version of Gapps?
SimonTS said:
What version of CyanogenMod and what version of Gapps?
Click to expand...
Click to collapse
7.1.0 and im not sure about Gapps but the download is 'gapps-gb-20110828-signed.zip'
Chrizz77 said:
7.1.0 and im not sure about Gapps but the download is 'gapps-gb-20110828-signed.zip'
Click to expand...
Click to collapse
It's the right version of Gapps. I presume that you did a full wipe, cache etc before flashing?
There is a stable v7.2.0 available from here - thanks to Nexx.
Also, if you like CM7 as a base, you might be well advised to try out Reaper ROM by Lowveld. It's what I've been using as my daily for months and I've never had a single problem with it. So fast, smooth and stable.
SimonTS said:
It's the right version of Gapps. I presume that you did a full wipe, cache etc before flashing?
There is a stable v7.2.0 available from here - thanks to Nexx.
Also, if you like CM7 as a base, you might be well advised to try out Reaper ROM by Lowveld. It's what I've been using as my daily for months and I've never had a single problem with it. So fast, smooth and stable.
Click to expand...
Click to collapse
I'm now running 7.2.0 and the video playback still doesnt work Is there any other known reason that could be the cause?
Update: I'm now running Reaper V3.0 and there is still a video problem
fullwipe, wipe catch, wipe everything....then take a deep breath, flash everything, dont miss a thing..^^
I am on ICS 4.0.3... 9.4.5.30 I am rooted, unlocked and have TWRP. I can't find anything consistent online to get this thing to JB so I can install the latest Clean Rom. And I can no download anything from Asus' website... It just DOESN'T work! Nothing there to DOWNLOAD........
"*Remember you must be on the JellyBean bootloader for CROMi 3.xx"
It seems like there are no consistent way to do this, if anyone has a way please help.....
Thanks
darkreaper476 said:
I am on ICS 4.0.3... 9.4.5.30 I am rooted, unlocked and have TWRP. I can't find anything consistent online to get this thing to JB so I can install the latest Clean Rom. And I can no download anything from Asus' website... It just DOESN'T work! Nothing there to DOWNLOAD........
"*Remember you must be on the JellyBean bootloader for CROMi 3.xx"
It seems like there are no consistent way to do this, if anyone has a way please help.....
Thanks
Click to expand...
Click to collapse
First make sure you have TWRP version 2.3.1.0 or 2.3.3.0 recovery, if you have the old version it will brick your device when you wipe data. Next you need to download the latest Asus full firmware from Asus site. Go here http://www.service.asus.com/ then click on download, then type in search box tf700 hit search, then pick tf700, then pick O/s is Android, click on firmware and find the correct SKU for your region like US for United State, under neath you see a icon of a floppy disk called "Global" click on it to download. Asus site is slow to nagivate so be patient. Once you download the zip file, first unzip it to another zip file, then copy to your sdcard, then boot into twrp (the recommended version), then flash this zip, once done, you will lose TWRP because this is a full firmware with JB bootloader. You need to fastboot back TWRP, then use twrp to flash Cleanrom. That's it!! Just ask if still need help.
Well I finally got the asus website to download the file for me.. Chrome issue I guess..
I then got lucky when I flashed it because I have No Clue what version of twrp I have.. lol I just flashed it with goo manager so I am amusing latest. This is my first experience with these asus products.... sorry for the ignorance. (only moto and samsung devices in the past)
It says right on the NV flash page to not use it with post 9.4.5.30....
"'THIS ONLY WORKS IF YOU HAVE A PRE 9.4.5.30 BOOTLOADER"
That is what I had, now I have 10.4.4.25... um 9 is < 10 right?....
Even though I used OTA root keeper I lost root too, I guess I have to start over from here.....?
Thanks!
darkreaper476 said:
Well I finally got the asus website to download the file for me.. Chrome issue I guess..
I then got lucky when I flashed it because I have No Clue what version of twrp I have.. lol I just flashed it with goo manager so I am amusing latest. This is my first experience with these asus products.... sorry for the ignorance. (only moto and samsung devices in the past)
It says right on the NV flash page to not use it with post 9.4.5.30....
"'THIS ONLY WORKS IF YOU HAVE A PRE 9.4.5.30 BOOTLOADER"
That is what I had, now I have 10.4.4.25... um 9 is < 10 right?....
Even though I used OTA root keeper I lost root too, I guess I have to start over from here.....?
Thanks!
Click to expand...
Click to collapse
No, you unlocked right? read my instruction you need to reflash twrp then you can flash custom rom. You can follow instruction from here http://forum.xda-developers.com/showthread.php?t=1938129 start with section 2, make sure you download the latest twrp (2.3.3.0 goomanager won't help you here).
I am unlocked. I will have to use the fastboot method to get twrp again right? Is there another way? My computer has been having issues with ADT, since you can't just get the good ol SDK anymore....
I'll try anyway..
darkreaper476 said:
I am unlocked. I will have to use the fastboot method to get twrp again right? Is there another way? My computer has been having issues with ADT, since you can't just get the good ol SDK anymore....
I'll try anyway..
Click to expand...
Click to collapse
Eventually you will need to use fastboot/adb, so I suggest to get it working. Once it's working it only take a few seconds to flash twrp. In the future when Asus release another firmware with a different bootloader, you will need to do the same again.
buhohitr said:
Eventually you will need to use fastboot/adb, so I suggest to get it working. Once it's working it only take a few seconds to flash twrp. In the future when Asus release another firmware with a different bootloader, you will need to do the same again.
Click to expand...
Click to collapse
OK so I ran the fastboot command to install twrp
sending 'recovery' (7618 KB)...
OKAY [ 2.842s]
writing 'recovery'...
OKAY [ 6.945s]
finished. total time: 9.789s
But my tab seems stuck. It shows the fastboot screen with a bar that is highlighted about 60% of the way. Do I reboot my self? I would hate to brick this thing...
darkreaper476 said:
OK so I ran the fastboot command to install twrp
sending 'recovery' (7618 KB)...
OKAY [ 2.842s]
writing 'recovery'...
OKAY [ 6.945s]
finished. total time: 9.789s
But my tab seems stuck. It shows the fastboot screen with a bar that is highlighted about 60% of the way. Do I reboot my self? I would hate to brick this thing...
Click to expand...
Click to collapse
do fashboot reboot command to reboot. BTW, you flash the 2.3.1.0 or 2.3.3.0 version of TWRP right? if not may brick your device if you try to wipe. Once boot into twrp, please check the version.
buhohitr said:
do fashboot reboot command to reboot. BTW, you flash the 2.3.1.0 or 2.3.3.0 version of TWRP right? if not may brick your device if you try to wipe. Once boot into twrp, please check the version.
Click to expand...
Click to collapse
Yes I did "openrecovery-twrp-2.3.3.0-tf700t.blob".
Thank you!! now I need to figure out how to re-root.. I found a how to for CWM..
Edit:
I found this:
http://forum.xda-developers.com/showthread.php?t=1929712
This is why these forums drive me nuts. No one seems to put what version of android any of this if for....
Edit2:
comments say it works for JB. Going for it.. lol
Edit3: Worked, time for Clean Rom then ubuntu. LOL
Thanks for all your help, and for not being a typical XDA a$$.
You could have just updated to the 10.4.4.25 bootloader in post 2 of the cromi thread from twrp.
Lately, many people, including myself, have been at a disadvantage of not having an official RUU for JellyBean so that stock environment can be achieved. Although sometimes, OTA's are available which can do the job. Hence this Tutorial. Also this saves the effort to do S-OFF/SuperCID which often brings along more problems.
This Tutorial, in principle, can be applied to both S4 and S3 variants.
All thanks to @xander1993 at the VilleC2 Development Section who created the original thread Here. Though somewhat unclear and related to VilleC2, I thought of making a thorough guide for Ville with some minor changes.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For T-MOBILE UK Users: (UK people with other operators e.g Three, Vodafone etc can also try the Jellybean Nandroid backup IF their firmware is upgraded to that of Jellybean)
ICS Users: Those stuck on ICS custom ROMs and can't get stock, Use This RUU to get to stock ICS and then update to Jellybean via System Updates Check. Thanks to @ppm48
Jellybean Users:Those stuck on Jellybean custom ROMs wanting to get stock, I have a Stock Jellybean 4.1.1 Nandroid backup for you guys Here Since there isn't any OTA.zip for T-Mobile UK for Jellybean. You can just flash this Nandroid right away without using this tutorial. Again, Thanks to @ppm48 for this. Also, if you have bootloops after restoring this backup, flash a Jellybean Sense boot.img.
Additionally refer to this post by @mkoev , should prove a lot helpful. Then you can follow the tutorial.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For OPTUS Users with CID OPTUS001: (All thanks to @salac)
Get the modified OTA.zip Here. by @salac
salac said:
Follow the instructions from step 12.
Step 14. Flashing the firmware.zip worked the second try for me
Step 22. I did flash the boot.img to make sure it will work since I don't think I had the original one.
Good Luck
Click to expand...
Click to collapse
Optus users please follow @salac 's post above to flash the OTA.zip
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pre-requisites:
1. Notepad++
2. 7-Zip (Recommended)
3. ADB+Fastboot (Get it Here)
4. HTC drivers (Standalone OR HTC Sync Manager Drivers)
5. Unlock_code.bin from HTCDev to unlock bootloader.
6. Any OS (Custom/Stock) present on the phone. (I have not tested it for phones without any OS, you may try it at your own risk and post results here) Not Needed anymore.
Common Steps:
In this guide, I will ask you to go to fastboot/adb so you should know how you would do that. (All fastboot/adb commands are to be given via Command Prompt from PC)
To execute Fastboot Commands:
- Go to fastboot folder on your PC
- Go to fastboot via bootloader on your phone
- Connect the Phone to PC and on the Phone it should say Fastboot - USB Mode
- Now in the fastboot folder on your PC, Hold Shift + Right-Click and click Open Command Window Here
- Now you can enter commands given in the guide for fastboot.
To execute ADB Commands:
- Same procedure except that you don't need to go to fasboot on your phone. You can execute adb commands while in Android OS/desktop.
To boot into Bootloader:
- While the phone is turned off, Press Volume Down + Power Button simultaneously.
OR
- If you are in Android OS, use the following adb command to boot into bootloader:
Code:
adb reboot bootloader
OR
- If you want to reboot into bootloader from fastboot:
Code:
fastboot reboot-bootloader
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Caution for SuperCID users: Please click the CROSS button on your Browser Tab, as flashing this is not intended for you. Either don't flash the OTA.zip, which will brick your phone if you do, OR change your CID to original one. e.g. H3G__001, BM___001, ORANG001
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Procedure:
- ** - ** - ** - Make Nandroid Backups before you do anything, remember you are doing this at your own risk - ** - ** - ** -
1. Download a OTA.zip – Most likely from Here. (You can rename the OTA file which usually has a long name to simply OTA.zip for ease)
2. Extract firmware.zip from OTA.zip. Then extract boot.img from firmware.zip. For now, copy Boot.img to ADB+Fastboot Folder..
3. Now to match the CID of your phone. You can get the CID of your phone via CID Getter from Play Store. Once opened, at the top will be your CID in Red color.
Alternatively, You can also get CID of your phone via Fastboot. Command for that is:
Code:
fastboot getvar cid
and it should display your CID.
4. Inside firmware.zip, look for android-info.txt. Supported CIDs should be mentioned inside this file. If it matches with that of your phone, Proceed otherwise stop and don't put yourself into more problems. (CID Match Exception: This 4th step may not be applicable to you if & only if you are to skip steps 11 to 16, if this is the case, you may flash OTA.zip skipping steps 11 to 16; Read step 10 for more info and then come back here)
5. We need to remove some code lines from inside the OTA.zip. For this, Open the OTA.zip with 7-zip (Right-click ---> 7-zip ---> Open Archive).
6. Head over to META-INF\com\google\android and find a file named updater-script. Drag it out of the archive to the folder/desktop where you can edit it. You should make an extra copy of this file.
7. Once you drag it out, delete the original updater-script inside the archive. It will recompress OTA.zip.
8. Edit with Notepad++ the extracted updater-script file. Find these lines (in the beginning of the file) and delete them altogether:
Code:
[COLOR="Purple"]assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"BM___001") == "t");[/COLOR]
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4011000") == "t");,
assert(check_mid("simple", "PJ4011000") == "t");
);
You should delete these lines up to exact semi-colon ; at the end. (the purple lines with different CIDs can be different from those mentioned here, so no need to panic, just delete them)
9. Once edited, Copy this edited updater-script into the OTA.zip archive at the same location from which it was removed. It will recompress OTA.zip. You may now transfer OTA.zip to your SD-Card on your phone.
10. If you previously updated to JellyBean via OTA (Or if you have the exact or newer firmware on your phone than that present inside OTA.zip), skip steps 11 to 16. For example, if you have HBOOT Version 2.15.0000/2.13.0000 or above, it means you have already upgraded to Jellybean firmware so no need for Steps 11 to 16.
In case, if you are to proceed to step 11, that is if you are to flash firmware.zip, make sure to match CID as mentioned in step 4 to avoid any bricks. This is especially useful for those who have ICS and want to get stock JB or those on JB but want complete stock HBOOT, recovery etc.
11. Place firmware.zip extracted from OTA.zip inside ADB + Fastboot Folder.
12. Lock the bootloader, if unlocked. For this, go to fastboot on your phone and give the command:
Code:
fastboot oem lock
The phone reboots after this.
13. While in Android OS/Desktop, fire up Command window on PC to give the following ADB command to boot into OEM Update Mode.
Code:
adb reboot oem-78
OR (if you can't access OS to execute adb)
From Fastboot:
Code:
fastboot oem rebootRUU
You should be seeing HTC logo.
14. While in OEM Update Mode, give the following fastboot command to flash firmware:
Code:
fastboot flash zip firmware.zip
If it fails with error and doesn't show any Green Progressbar, keep trying the above command. Usually works after a few tries.
********** DO NOT REBOOT MANUALLY UNTIL IT FINISHES FLASHING FIRMWARE OR YOU'LL BRICK YOUR PHONE *************
15. Once firmware is updated, reboot into bootloader. Go into fastboot.
16. Place Unlock_code.bin inside ADB + Fastboot Folder. Use the following fastboot command to unlock your bootloader again. (This will wipe your phone except for SD, so you must make a backup before doing this)
Code:
[COLOR="Blue"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
17. Download a recovery. Preferred Recovery is TWRP 2.3.3.0 and I have not tested this guide with any other version. Put the recovery in the ADB + Fastboot folder.
18. Now go into bootloader again. This time to flash the recovery anew.
Code:
fastboot flash recovery recovery.img
19. Now go to the recovery via bootloader. Wipe data/factory reset, cache, dalvik.
20. Restore the Nandroid backup you had made earlier.
21. Now Flash the OTA.zip which is on your SD-Card. It should flash fine.
22. Go to fastboot via bootloader. We are now going to flash kernel with the following command, boot.img you had earlier copied to ADB+Fastboot folder.
Code:
fastboot flash boot boot.img
23. Reboot to the OS and you should see complete stock JB OS.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Please Rate the thread and Hit the Thanks button if this tutorial helped you!
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Well, When I edited OTA.zip, it was the same size before/after. But maybe OS X uses different compression values.
I think you should go ahead with it and try it.
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
.......................
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Can you use Winzip/Winrar? Might want to check with those two..
mortek said:
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
Click to expand...
Click to collapse
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
khan.orak said:
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
Click to expand...
Click to collapse
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
mortek said:
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
Click to expand...
Click to collapse
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
khan.orak said:
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
Click to expand...
Click to collapse
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
mortek said:
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
Click to expand...
Click to collapse
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
khan.orak said:
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
Click to expand...
Click to collapse
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
mortek said:
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
Click to expand...
Click to collapse
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
khan.orak said:
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
Click to expand...
Click to collapse
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
sending 'zip' (400 KB)...
OKAY [ 0.226s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.735s
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
mortek said:
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
...........
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
Click to expand...
Click to collapse
I suspect hardware failure.
Sent from my HTC One S using Tapatalk 4 Beta
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
booenson said:
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
Click to expand...
Click to collapse
What recovery did you use? And did you edit updater script using notepad++?
Edit: Yup, after searching, Error Status 6 appears when you edit the UPDATER-SCRIPT using wordpad/windows editor which messes all that is inside it. Use Notepad++
khan.orak said:
What recovery did you use? And did you edit updater script using notepad++?
Click to expand...
Click to collapse
TWRP 2.4.1.0. No, I used notepad, but after googling and reading the differences between notepad++ and notepad, I will have to re edit with notepad++. Will try again tomorrow when I have more time, I still need to use this phone for work and can't have it bricked lol
Tried this again, flash went through and then flashed the boot.img included with the OTA zip, and my phones stuck at the "htc one" loading screen
Edit: relocked, flashed the stock recovery, thought it was still stuck at the loading screen so I unlocked it then went to install TWRP again to restore my nandroid, and it decided to finally boot. I guess I just needed to give it more time, currently back on 4.1.1, time to send this thing in under warranty so I can get my 3G/HSPA+ fixed. Thanks!
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
asdfasdfvful said:
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think yes. You can check if you CID is supported. It is inside the OTA.zip\firmware.zip, a file named android-info.txt and the supported CIDs will be there.
Edit: You should first check your CID. Download CID GETTER from Play Store. Shows CID in red on top.
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
RBraverman said:
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
Click to expand...
Click to collapse
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
cmendonc2 said:
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
Click to expand...
Click to collapse
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
RBraverman said:
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
Click to expand...
Click to collapse
Hope you get getter
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
cmendonc2 said:
Hope you get getter
Click to expand...
Click to collapse
Thank you, slowly on the mend.
cmendonc2 said:
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
Click to expand...
Click to collapse
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
So I need 3 things: newest F/W (have), Latest TWRP(don't have - yet but looking, 2.7 I believe), latest way to root(don't know) - Correct?
Again where is that thanks button!!!!!
RBraverman said:
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
Again where is that thanks button!!!!!
Click to expand...
Click to collapse
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
cmendonc2 said:
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
Click to expand...
Click to collapse
NOW it's there!
Okay upping to stock F/W, looking for TWRP (openrecovery-twrp-2.6.3.0-tf300tg-JB.img) then how do I root this
RBraverman said:
NOW it's there!
Okay upping to stock F/W, looking for TWRP - how do I root this
Click to expand...
Click to collapse
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
cmendonc2 said:
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
Click to expand...
Click to collapse
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
RBraverman said:
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much mroe optimized for older devices, and you should see a performance upgrade.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Click to expand...
Click to collapse
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much more optimized for older devices, and you should see a performance upgrade.
Click to expand...
Click to collapse
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
RBraverman said:
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
Click to expand...
Click to collapse
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
cmendonc2 said:
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
Click to expand...
Click to collapse
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Just rebooted, and it's 4.2.1, but everything I had - most of what I had, is still there!?! And the run?
RBraverman said:
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Click to expand...
Click to collapse
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
cmendonc2 said:
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
Click to expand...
Click to collapse
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
RBraverman said:
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
Click to expand...
Click to collapse
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
cmendonc2 said:
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
Click to expand...
Click to collapse
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
RBraverman said:
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
Click to expand...
Click to collapse
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
cmendonc2 said:
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
Click to expand...
Click to collapse
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
RBraverman said:
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
Click to expand...
Click to collapse
I'm not sure what you are talking about with "fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img". As long as TWRP is working you shouldn't have to use fastboot anymore.
The new bootloader that you upgraded to only has 3 icons when you press vol-down and power. Fastboot now connects automatically if you turn on your tablet with the USB plugged in and pressing the key combo. To access TWRP, selecting RCK is the correct choice. As always, never select the Wipe Data in the bootloader menu or you will brick.
Before flashing new ROMs, you should only have to do the "swipe to factory reset" option in the TWRP recovery. If you update your ROM with a newer version of that specific ROM, you only have to Wipe Cache and Dalvik Cache.
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh