Related
please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
You can revert to the ICS bootloader with the .30 firmware following instructions below only using .30 firmware instead of the JB Firmware.
Thanks goes to saltxyz for this find.
I think we've taken this thread about as far as it can go information wise. Please join me in my new thread here: http://forum.xda-developers.com/showthread.php?t=1886877
Thank you everyone for taking the plunge with me, the Thanks, guidance, and making this a newsworthy thread!
You can download my custom kernel here or below: https://www.dropbox.com/sh/ay9iolwcfbxu0wm/_vpRpSQ6nK/kernel.zip
STOP
1. I am not responsible for any issues this may cause your device and won't be held for any soft-bricks, hard-bricks, boot loops, exploding pets or Resonance Cascades.
2. Go ahead and download ADB/Fastboot to make your life easier: http://developer.android.com/sdk/index.html
What Works/Doesn't Work
What Works:
Almost everything!
What Doesn't Work:
Changing Brightness Settings without the use of a Third-Party App
Resolution (DPI is set to 160 by default and changing it through an App or directly with build.prop makes no changes) - FIXED
You WILL lose Root and Custom Recovery with these methods
Drivers
I used the ASUS Android USB Drivers from the following post for ABD/Fastboot: http://forum.xda-developers.com/showthread.php?t=1706588
Installation
Method 1 for Locked/Unlocked Bootloader with Stock Recovery and/or Root
1. Power off your tablet
2. Download the latest TF300T firmware (XX_epaduser_10_4_2_9_UpdateLauncher.zip) from Asus site based on your SKU location (eg. ww, US, etc): http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad TF300T&p=20&s=16
3. Right click and extract the downloaded .ZIP file (XX_epaduser_10_4_2_9_UpdateLauncher.zip) onto your desktop
4. Rename the extracted .ZIP to "EP201_768_SDUPDATE" (without the " ") and copy it to your MicroSD card
5. Insert the MicroSD card in your tablet
6. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
7. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
8. At this point the device will go in recovery and should start updating your firmware
Method 2 for Unlocked Bootloader with Custom Recovery and/or Root
1. Power off your tablet
2. Download the latest TF300T firmware (XX_epaduser_10_4_2_9_UpdateLauncher.zip) from Asus site based on your SKU location (eg. ww, US, etc): http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad TF300T&p=20&s=16
3. Right click and extract the downloaded .ZIP file (XX_epaduser_10_4_2_9_UpdateLauncher.zip) onto your desktop
4. Copy the extracted .ZIP (XX_epad-user-10.4.2.9.zip) to your MicroSD card
5. Insert the MicroSD card in your tablet
6. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
7. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
8. From your recovery menu press Install and select the .ZIP file (XX_epad-user-10.4.2.9.zip)
9. Wait until the install process ends and then restart your device
Method 3 Advanced using Fastboot
1. Power off your tablet
2. Download the latest TF300T firmware (XX_epaduser_10_4_2_9_UpdateLauncher.zip) from Asus site based on your SKU location (eg. ww, US, etc): http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad TF300T&p=20&s=16
3. Right click and extract the downloaded .ZIP file (XX_epaduser_10_4_2_9_UpdateLauncher.zip) onto your desktop
4. Right click and extract the new .ZIP file (XX_epad-user-10.4.2.9.zip) onto your desktop; you should now have the blob binary and META-INF folder on your desktop
5. Copy the blob binary to your platform-tools folder (C:\Program Files\Android\android-sdk\platform-tools or C:\Program Files (x86)\Android\android-sdk\platform-tools)
6. Plug tablet into your computer
7. Boot your tablet into Fastboot by pressing and holding Volume Down AND Power for 5 seconds
8. A message will inform you that you have 5 seconds to enter Recovery; press Volume Down twice to select Fastboot and then Volume Up before the 5 seconds expire
9. Open a command prompt and cd into your platform-tools folder; or press right-Shift on your keyboard and right-click the platform-tools folder and click "Open command window here"
10. Enter the following command in the command prompt: "fastboot -i 0x0B05 flash system blob" (without the " ")
11. Once the previous command completes enter: "fastboot -i 0x0B05 reboot" (without the " ")
RECOMMENDED but Optional Steps:
If you are using Stock Recovery it is advised to Factory Data Reset or Wipe Data both BEFORE and AFTER the Firmware Upgrade
If you are using Custom Recovery it is advised to wipe ALL partitions
Unlocking the Bootloader
You can use the ASUS Unlock Tool from the ASUS Support site to unlock your bootloader. Despite ASUS saying it's for ICS it works fine on JB. Detailed instructions to come.
Recovery (TWRP) **Requires Unlocked Bootloader**
1. Turn your tablet off
2. Download the latest TWRP blob: http://teamw.in/project/twrp2/105
3. Rename the blob binary (openrecovery-twrp-X.X.X.X-tf700t.blob) to "twrp.blob" (without the " ")
4. Copy the twrp.blob binary to your platform-tools folder (C:\Program Files\Android\android-sdk\platform-tools or C:\Program Files (x86)\Android\android-sdk\platform-tools)
5. Plug tablet into your computer
6. Boot your tablet into Fastboot by pressing and holding Volume Down AND Power for 5 seconds
7. A message will inform you that you have 5 seconds to enter Recovery; press Volume Down twice to select Fastboot and then Volume Up before the 5 seconds expire
8. Open a command prompt and cd into your platform-tools folder; or press right-Shift on your keyboard and right-click the platform-tools folder and click "Open command window here"
9. Enter the following command in the command prompt: "fastboot -i 0x0B05 flash recovery twrp.blob" (without the " ")
10. Once the previous command completes enter: "fastboot -i 0x0B05 reboot" (without the " ")
Root **Requires Unlocked Bootloader AND Custom Recovery**
1. Download the latest Custom Recovery installable SuperSU .ZIP (CWM-SuperSU-vX.XX.zip): http://forum.xda-developers.com/showthread.php?t=1538053
2. Plug tablet into your computer
3. Copy the SuperSU .ZIP (CWM-SuperSU-vX.XX.zip) to Internal Storage
4. Turn your tablet off
5. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
6. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
7. From your recovery menu press Install and select the SuperSU .ZIP (CWM-SuperSU-vX.XX.zip)
8. Wait until the install process ends and then restart your device
9. Now your tablet should be rooted
F.A.Q.
JB seems to be laggy. Any suggestions?
Yes, Wipe!! Even if you've performed a Factory Data Reset or Wipe Data I HIGHLY recommend unlocking your bootloader, installing a Custom Recovery, wiping EVERYTHING and installing the firmware again; preferably using Method 3.
Is there any way to change the Brightness settings?
Yes, through Third Party Apps. The most popular seem to be Lux and Custom Brightness Settings
Are we "SOL" having the TF300 Bootloader when the Tf700 JB Firmware comes out?
Personally I'm not too worried about the bootloader.
Either the official JB for TF700 will have the same bootloader as for the TF300, or it will be a newer version that we'll be able to flash.
The bootloader doesn't seem to be looking for a device check or else the 300 loader wouldn't have installed on the 700.
It really only seems to be doing a sig check for OLDER firmwares, not NEWER.
Why don't we have an Official TF700 JB Firmware yet?
I don't know, ask ASUS. I'm as flabbergasted as you are. We've only found two issues so far!!
UPDATE UPDATE: Kernel configs are also amazingly identical. Most new options available in the JB 3.X kernel aren't even set. Only things that stick out are that CONFIG_SENSORS_ISL29028 (Light Sensor driver) went from yes to not set. Also I keep seeing NFC code EVERYWHERE which is disabled in JB stuff. Does the TF700 have NFC or is ASUS pulling from one base? <-(Hmmm...) CONFIG_NTFS_FS has also been set to yes in JB so we should check out NTFS formatted SDCARDs. Also fun fact; CONFIG_ISO9660_FS (CD/DVD Filesystems) was set to yes in the ICS kernel. LOL. Everything we need is there, somethings just stopping it. It's funny looking through the code you can tell it was written by two different teams as most times configs contain the same info, only in a different order. Makes it hard to compare code though; jerks. No wonder it's not officially out yet.
UPDATE: I just finished comparing /system between the TF300 JB blob and the TF700 ICS blob. 98% of the config files are similar or are only off by a line or two. Issues with screen resolution and brightness seem to be stemming from kernel. I'm gonna see if I can rip the ICS kernel out and transplant it in JB or recompile the TF300 kernel using the config from ICS. They jumped from 2.6.X to 3.X so who knows...
Is there a reason you need to name it recovery.zip? I just named it 300jb.zip, been installing for almost 30 mins here!
Unlocked bootloader, custom recovery and complete wipe.
Sent from my GT-I9300 using xda premium
fordwolden said:
Is there a reason you need to name it recovery.zip? I just named it 300jb.zip, been installing for almost 30 mins here!
Unlocked bootloader, custom recovery and complete wipe.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Nope, just going off what most people named it.
To get root back, its failrly easy.
1. Install TWRP using fastboot. Just check their site for the how to do. Make sure you have fastboot and the drivers on your PC
2. Download SuperSU-CWM pack from the SuperSU topic on XDA.
3. put the SuperSU pack on your SDcard internal or external.
4. Flash that pack.
5. Boot up and open up SuperSU.
6. Update binary and done
Maybe nice to note what is broke if you use this flashing methode.
- Brightness controll is broken. Its on full all the time
- Everything is a little bigger then usual, Or I am a little blind
For the rest I added the tweaks to the build.prob from the tips topic and I am running super smooth.
And I just downloaded that update for the TF300 from the asus site. Extracted it so I got the update zip thingy. Placed that on my SDcard. Wiped all and just installed. Did not rename a thing. And it worked just fine.
Then I did the steps from above and thats it.
Rooted and unlocked with TWRP running JB Me is very happy
Has anyone tested if the lag still exists with a bluetooth headset while viewing a video?
anyone know what causes a data transfer failure with the error "too many links" when using fastboot to flash?
i was able to get the boot blob to flash, but when i try flashing the system blob it crashes with that error. btw i'm flashing things separately because i don't want to have my bootloader updated.
urrlyx said:
anyone know what causes a data transfer failure with the error "too many links" when using fastboot to flash?
i was able to get the boot blob to flash, but when i try flashing the system blob it crashes with that error. btw i'm flashing things separately because i don't want to have my bootloader updated.
Click to expand...
Click to collapse
I think you answered your own question.
lafester said:
I think you answered your own question.
Click to expand...
Click to collapse
Actually I didn't, or I wouldn't have asked it. If the answer is "you can't flash this system blob with the old bootloader", then saying so would be an appropriate response.
Also, since it could be caused by something else like an inability of fastboot to flash extracted system blobs without the header file, or maybe corruption in the blob caused by using a windows binary of blobunpack, I feel my question is quite valid.
edit: I ended up doing more research and it appears that even if I did get the system blob flashed, it probably wouldn't boot without the updated bootloader due to the 3.x kernel. Even the custom JB roms for the 300 make you update the bootloader on that tablet first.
So, I'm going to put this on the backburner until there's an official bootloader update for the 700 or until someone already on the new 300 bootloader successfully flashes back to the current one.
rdejager said:
For the rest I added the tweaks to the build.prob from the tips topic and I am running super smooth.
Rooted and unlocked with TWRP running JB Me is very happy
Click to expand...
Click to collapse
I added the build.props tweaks and it bricked my tablet at ASUS bootsplash? which ones did you add? can you upload your build.prop?
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Keion said:
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Click to expand...
Click to collapse
I thought somebody said they flashed a custom jb rom from the tf300
Edit found who said it...
http://forum.xda-developers.com/showthread.php?p=31214220
Sent from my SPH-D710 using Tapatalk 2
Keion said:
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Click to expand...
Click to collapse
One guy said it flashed ok, another said no.
Sent from my EVO using xda premium
I'm pretty sure you need to be on the new bootloader for the stock rom / stock-based roms to work. I've been reading through the tf300 forums and so far I haven't found any posts about anyone being able to revert back to the ICS bootloader. One guy suggested this is due to signature checking, different permissions, and possibly an altogether different partition table.
urrlyx said:
One guy suggested this is due to signature checking, different permissions, and possibly an altogether different partition table.
Click to expand...
Click to collapse
AFAIK, the bootloader can't alter the partition table on Tegra units. In fact, the bootloader is itself a partition. Only way to change the partition table is with nvflash.
Hopefully the TF700 JB Update would be able to flash over the TF300 JB Bootloader, otherwise we will stuck at this "not so perfect"-build for a very long time!
I miss the DPI changing I'm not blind and everything is so ****ing big on the screen.
Guys, did someone else see that the Battery is going low pretty much faster?
Keion said:
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Click to expand...
Click to collapse
If you change the updater-script (attached in zip) with the one in this ROM: http://forum.xda-developers.com/showthread.php?t=1854212
in the subfolder: Asu-JellyBean-HyDRO-R1.zip\META-INF\com\google\android\
You can Install it on your TF700T
I'm running it right now, but I will go back to stock JB because ASUS Settings bring a force close.
All other things are still the same, backlight doesn't work, anything else is fine.
Hopefully someone sees something helpful from this and can make a safe stock tf700 update.
Seems devs here work as hard as asus does.
Thanks guys for all you do
Sent from my ASUS Transformer Pad TF700T using xda premium
kabauterman said:
Hopefully the TF700 JB Update would be able to flash over the TF300 JB Bootloader, otherwise we will stuck at this "not so perfect"-build for a very long time!
I miss the DPI changing I'm not blind and everything is so ****ing big on the screen.
Guys, did someone else see that the Battery is going low pretty much faster?
Click to expand...
Click to collapse
Personally I'm not too worried about the bootloader. Either the official JB for TF700 will have the same bootloader as for the TF300, or it will be a newer version that we'll be able to flash.
The bootloader doesn't seem to be looking for a device check or else the 300 loader wouldn't have installed on the 700. It really only seems to be doing a sig check for OLDER firmwares, not NEWER.
Sorry Mods if this is the wrong section was just 2 many threads with people having problems was easier then tryign to reply to them all.
Directions
After doing this Your Phone This Will BeFactory Reset
1) Download The backup i made here Sorry this has a Custom Boot animation rest is stock.
Extract it to a folder on your SDcard dont just copy it there.
Im going to Assume everyone at this point has ADB and Fastboot installed if not follow the instructions here then come back
2) Download TWRP recovery to your PC
Download Stock Recovery for later use.
Powerdown Phone
Press and hold (Power button + Camera Button) at the menu use volume down until you get to AP Fastboot Press Volume up to select it
Hook Phone to pc via usb cable
Open a command prompt from within your SDK/Platform-tools folder
install trwp
Code:
fastboot flash recovery TWRP_Recovery_Filename_you_downloaded.img
Unhook Phone from PC when Finished Flashing should only take 1 minute or less.
Hit power - device turns off. Hold vol up + power, then release power. When you see it turn on, release vol up. You should now be in TWRP!
Now first thing Press Backup and make a backup of your current setup to SDcard.
3) Now somehow move the Backup you downloaded and Extracted in step one to your TWRP backup folder on your SDcard
will be something like
Make a new folder for BACKUP_NAME dont overwrite the backup you made
Code:
TWRP/BACKUPS/SERIALNUM/RESTORE_MY_PHONE/files_here
4) Power off Phone
Reboot into Recovery (Power Button + Volume Up) Choose Restore button this time choose Restore and Choose the Recovery the you downloaded.
When done flashing your back up Choose reboot from the option choose Bootloader.
Hook Phone to pc via usb cable
Open a command prompt from within your SDK/Platform-tools folder
install Stock recovery
Code:
fastboot flash recovery Stock recovery.img
Unhook Phone from USB after Flashing and press Power Button and phone will reboot.
If all went as planned you will boot up to a factory reset phone thats ready to download and install the OTA with no problems
and sorry the backup has a Custom boot animation i forgot to remove
-Bryan
Worked as expected. Thank you.
This would be good for recovering from a soft brick as well, maybe this could be our first official sticky?
-Saint
Thank you so much for your help!
Rangerbry said:
Sorry Mods if this is the wrong section was just 2 many threads with people having problems was easier then tryign to reply to them all.
Directions
After doing this Your Phone This Will BeFactory Reset
1) Download The backup i made here Sorry this has a Custom Boot animation rest is stock.
Extract it to a folder on your SDcard dont just copy it there.
Im going to Assume everyone at this point has ADB and Fastboot installed if not follow the instructions here then come back
2) Download TWRP recovery to your PC
Download Stock Recovery for later use.
Powerdown Phone
Press and hold (Power button + Camera Button) at the menu use volume down until you get to AP Fastboot Press Volume up to select it
Hook Phone to pc via usb cable
Open a command prompt from within your SDK/Platform-tools folder
install trwp
Code:
fastboot flash recovery TWRP_Recovery_Filename_you_downloaded.img
Unhook Phone from PC when Finished Flashing should only take 1 minute or less.
Hit power - device turns off. Hold vol up + power, then release power. When you see it turn on, release vol up. You should now be in TWRP!
Now first thing Press Backup and make a backup of your current setup to SDcard.
3) Now somehow move the Backup you downloaded and Extracted in step one to your TWRP backup folder on your SDcard
will be something like
Make a new folder for BACKUP_NAME dont overwrite the backup you made
Code:
TWRP/BACKUPS/SERIALNUM/RESTORE_MY_PHONE/files_here
4) Power off Phone
Reboot into Recovery (Power Button + Volume Up) Choose Restore button this time choose Restore and Choose the Recovery the you downloaded.
When done flashing your back up Choose reboot from the option choose Bootloader.
Hook Phone to pc via usb cable
Open a command prompt from within your SDK/Platform-tools folder
install Stock recovery
Code:
fastboot flash recovery Stock recovery.img
Unhook Phone from USB after Flashing and press Power Button and phone will reboot.
If all went as planned you will boot up to a factory reset phone thats ready to download and install the OTA with no problems
and sorry the backup has a Custom boot animation i forgot to remove
-Bryan
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR YOUR HELP!
c2gemineyes
No Dice
Rangerbry said:
Sorry Mods if this is the wrong section was just 2 many threads with people having problems was easier then tryign to reply to them all.
Directions
After doing this Your Phone This Will BeFactory Reset
1) Download The backup i made here Sorry this has a Custom Boot animation rest is stock.
Extract it to a folder on your SDcard dont just copy it there.
Im going to Assume everyone at this point has ADB and Fastboot installed if not follow the instructions here then come back
2) Download TWRP recovery to your PC
Download Stock Recovery for later use.
Powerdown Phone
Press and hold (Power button + Camera Button) at the menu use volume down until you get to AP Fastboot Press Volume up to select it
Hook Phone to pc via usb cable
Open a command prompt from within your SDK/Platform-tools folder
install trwp
Code:
fastboot flash recovery TWRP_Recovery_Filename_you_downloaded.img
Unhook Phone from PC when Finished Flashing should only take 1 minute or less.
Hit power - device turns off. Hold vol up + power, then release power. When you see it turn on, release vol up. You should now be in TWRP!
Now first thing Press Backup and make a backup of your current setup to SDcard.
3) Now somehow move the Backup you downloaded and Extracted in step one to your TWRP backup folder on your SDcard
will be something like
Make a new folder for BACKUP_NAME dont overwrite the backup you made
Code:
TWRP/BACKUPS/SERIALNUM/RESTORE_MY_PHONE/files_here
4) Power off Phone
Reboot into Recovery (Power Button + Volume Up) Choose Restore button this time choose Restore and Choose the Recovery the you downloaded.
When done flashing your back up Choose reboot from the option choose Bootloader.
Hook Phone to pc via usb cable
Open a command prompt from within your SDK/Platform-tools folder
install Stock recovery
Code:
fastboot flash recovery Stock recovery.img
Unhook Phone from USB after Flashing and press Power Button and phone will reboot.
If all went as planned you will boot up to a factory reset phone thats ready to download and install the OTA with no problems
and sorry the backup has a Custom boot animation i forgot to remove
-Bryan
Click to expand...
Click to collapse
I got this to restore my phone to stock no problem. I followed this post to a T twice and upon updating my phone goes ape$hit every time.
So frustrated with Motorola right now.
patrickm823 said:
I got this to restore my phone to stock no problem. I followed this post to a T twice and upon updating my phone goes ape$hit every time.
So frustrated with Motorola right now.
Click to expand...
Click to collapse
So... Don't update? I'm still on the original firmware, I don't see any benefit to updating.
Are you taking the update with any toggle mods, root (I.e. Superuser.apk installed), deodexed framework, battery 1% mods, power menu mod, custom boot logo, animation, etc? I never had problems taking the update with stock rom/recovery, unrooted, with no mods installed. I used this guide to restore stock when I was softbricked and bootlooping and the update worked after restoring stock recovery.
Sent from my XT897 using xda app-developers app
screen comes like for a millisecond and then this " starting services" logo doesn't go at all...it just continues forever
any help would be appreciate .
Rangerbry said:
...
Hook Phone to pc via usb cable
Open a command prompt from within your SDK/Platform-tools folder
install Stock recovery
Code:
fastboot flash recovery Stock recovery.img
Unhook Phone from USB after Flashing and press Power Button and phone will reboot.
If all went as planned you will boot up to a factory reset phone thats ready to download and install the OTA with no problems
and sorry the backup has a Custom boot animation i forgot to remove
-Bryan
Click to expand...
Click to collapse
Hello everyone,
everything works fine until I tried to flash recovery stock. This errormassage is shown in my terminal:
C:\Users\xxx\Desktop\Dokumente\Apps\unsortiert\adt-bundle-windows-x86_64\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery Stock recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'Stock': No error
any ideas?
kaot5 said:
Hello everyone,
everything works fine until I tried to flash recovery stock. This errormassage is shown in my terminal:
C:\Users\xxx\Desktop\Dokumente\Apps\unsortiert\adt-bundle-windows-x86_64\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery Stock recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'Stock': No error
any ideas?
Click to expand...
Click to collapse
Hm... I thought the line should be
Code:
fastboot flash recovery recovery.img
Obviously replace recovery.img with your filename.
arrrghhh said:
Hm... I thought the line should be
Code:
fastboot flash recovery recovery.img
Obviously replace recovery.img with your filename.
Click to expand...
Click to collapse
My filename is recovery.img. Is the storage limited? Previouse I had CWM now installed TWRP without deinstall, could this be a problem?
kaot5 said:
My filename is recovery.img. Is the storage limited? Previouse I had CWM now installed TWRP without deinstall, could this be a problem?
Click to expand...
Click to collapse
What is this, I don't even...
Please try with the command I provided.
arrrghhh said:
What is this, I don't even...
Please try with the command I provided.
Click to expand...
Click to collapse
I'll try it tomorrow morning. I've forget my phone at work. This means in about 10hours. Many thanks in advance
kaot5 said:
I'll try it tomorrow morning. I've forget my phone at work. This means in about 10hours. Many thanks in advance
Click to expand...
Click to collapse
This command works Thx
Rangerbry said:
Sorry Mods if this is the wrong section was just 2 many threads with people having problems was easier then tryign to reply to them all.
Directions
After doing this Your Phone This Will BeFactory Reset
1) Download The backup i madeSorry this has a Custom Boot animation rest is stock.
Extract it to a folder on your SDcard dont just copy it there.
Im going to Assume everyone at this point has ADB and Fastboot installed if not follow the instructions then come back
...
Click to expand...
Click to collapse
Thank you! Fixed soft brick after a bad system.img flash.
Still wont update. i get a dead android logo after about 30 seconds into the update, then reboots to "The software update failed!"
this is a bit outdated now that we have working RSD Lite files follow the instructions here and use the supplied files for your carrier Sprint or cspire.
[05-08-2013] Photon Q FXZ
-Bryan
Thank you
Nice share and will appy soon
I'm running on ics and wait for 4.3
I mean jelly bean ruin my battery life, so I very very hope photon q will get the ota update for 4.3
Rangerbry said:
this is a bit outdated now that we have working RSD Lite files follow the instructions here and use the supplied files for your carrier Sprint or cspire.
[05-08-2013] Photon Q FXZ
Click to expand...
Click to collapse
Hi. I'm trying to figure this out, but the link for stock recovery you posted is dead.
So I want to clarify what you wrote above... are you saying to follow the instructions here (first post in this thread) but use the recovery.img from one of the zip files in that other link (i.e. asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip)?
Do I need to use "RSD Lite" for something? You didn't mention it in your instructions, but it's mentioned a lot in that other thread...
enigma9o7 said:
Hi. I'm trying to figure this out, but the link for stock recovery you posted is dead.
So I want to clarify what you wrote above... are you saying to follow the instructions here (first post in this thread) but use the recovery.img from one of the zip files in that other link (i.e. asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip)?
Do I need to use "RSD Lite" for something? You didn't mention it in your instructions, but it's mentioned a lot in that other thread...
Click to expand...
Click to collapse
You can use the RSD Lite file to return to stock the method in this thread was back before we had working RSD files
I'd like to know how to update my TWRP from v 2.4.4.0 to a later version. This version doesn't seem to allow flashing of an img file on external sd card. I have tried without success on 2 computers to get windows to recognise this android, so I'm hoping there is another way. Eventually I'd like to install Katkiss,Gapps and SU on this android. At present it has no rom.
Secondly, I tried to install Cromi X and all goes well up until I reboot and it continually spools on the opening screen so I don't know what that is about but hoping with a later TWRP I may be able to set the partitioning better which may or may not be part of the cause.
Reboot recovery twrp.
Go to install.
Click on install image.
Search downloaded recovery.
Select recovery.
And install.
Done
sent from moto g2014 with cm13
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
Ot use flashify app.
It requires root.
sent from moto g2014 with cm13
There is no 'install image' on v2.4.4.0 and that version of TWRP does not seem to recognise .img files on the external sd card. On a later version of TWRP your solution would work.
If you want to flash the recovery in recovery it has to be inside a flashable zip (except for the latest versions).
You can use the Kang TWRP 2.8.x from post 2 here: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
You can flash Katkiss with it no problem, and it supports the dock SD which the official TWRP does not do.
Somewhere there's also a thread where some dude keeps posting TWRP 3.x in a flashable zip, but I can't think of where right now.
That CROMi-X does not boot can have a number of reasons:
You did not format data before flashing the rom
You are on an outdated bootloader
Something is physically wrong with your emmc.
Your problem to get the tablet recognized in Windows is almost certainly a driver problem an you should get that fixed. At minimum it sucks not to have fastboot access to the tablet. And it easily could be lethal. For the tablet - not for you
Could also be a problem with a cheap knock-off replacement USB cable. If you are not using the original Asus cable that's worth investigating. And if you are using the original it may become worn. Mine is starting to allow a connection only in certain positions... Age....
Make sure the device drivers are installed and try the Google Universal Naked drivers. Minimal ADB and fastboot is an excellent tool that shimp208 still keeps current after all this time, and if none of those work try the 15 second adb installer if you are on Win 7 or earlier (just google it).
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
This is not the same device you helped me with earlier...it now purrs beautifully.... this is a new challenge.
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
Thought you looked familiar..... :cyclops:
Time to re-read this I think http://forum.xda-developers.com/showthread.php?t=2688891
Boot into the bootloader and read the small script. The last bootloader for this tablet is 10.6.1.14.10.
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
plato2 said:
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
Click to expand...
Click to collapse
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
berndblb said:
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
Click to expand...
Click to collapse
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
plato2 said:
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
Click to expand...
Click to collapse
If you downloaded from the second link, the flashable zip, you will see a zip file, not an img file.
Just hit Install, select the zip and swipe the button. Reboot when the flash is finished
All good so far. Up to the wiping data bit before converting to f2fs but this guide is missing, not sure why. I recall it was only a short set of instructions: Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tran...p-2-8-t3073471. Can you recall that part? thanks
Got it, found it or rather another post of yours here: tf700/help/how-to-update-twrp-withoput-adb-t3437702/post68163144#post68163144 so did that and successfully installed Katkis, Gapps pico and SU....another beautiful TF700T purring...many thanks yet again...
Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath
sampathnayak09 said:
Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath
Click to expand...
Click to collapse
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
How to return back to Stock Recovery & Install Stock Rom.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
@DigiGoon
@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img
@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
mahadikrs said:
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.
Click to expand...
Click to collapse
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.
muradulislam said:
@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.
Click to expand...
Click to collapse
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.
sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs
mahadikrs said:
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.
Click to expand...
Click to collapse
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.
muradulislam said:
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.
Click to expand...
Click to collapse
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0
DigiGoon said:
@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi,
I did flash the stock recovery, but my phone keeps rebooting and doesn't get into recovery mode.
I am sure it has sufficient battery charge. (Close to 90%).
Is there a way to do a clean install on Android phones? Like the way we install Windows OS on computers. Format hard disks, create partitions and then install a fresh OS?
Thanks
mahadikrs said:
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0
Click to expand...
Click to collapse
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?
sampathnayak09 said:
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?
Click to expand...
Click to collapse
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.
mahadikrs said:
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.
Click to expand...
Click to collapse
Thank you for providing the links. Let me try installing these.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
goldfinv said:
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs
Click to expand...
Click to collapse
Phone has 75% + charge as shown in TWRP recovery.
sampathnayak09 said:
Phone has 75% + charge as shown in TWRP recovery.
Click to expand...
Click to collapse
Maybe try flashing one of the custom EMUI ROMs via TWRP?
Sent from my H60-L04 using XDA Labs
@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
sampathnayak09 said:
@[email protected]@goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Give it a couple of tries. Users have suggested that it usually gets stuck somewhere but trying for 2,3 times gets the job done.
Sent from my PLK-L01 using XDA Labs
sampathnayak09 said:
@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Let me know which Rom version is your phone running now & which version you are trying to migrate to.
Also if 3 button Force update is not working then you can try the project menu option.
But first let me know what state your phone is currently in.