Been working on updating to JB 4.2 and wound up in a boot loop . Did successfully flash -TF700_421_US_BootRec_Flasher_Signed.zip and was previously unlocked and rooted with 4.1.
The problem now is that TWRP 2.5 is in a resolution that only allows half of the
buttons and options and options to show on the screen. Also re-flashed with -
openrecovery-twrp-2.5.0.0-tf700t.blob and tried with a few 2.4 versions with
same results. This makes it impossible to install any ROM to get out of the boot loop.
Any suggestions?
dengom said:
Been working on updating to JB 4.2 and wound up in a boot loop . Did successfully flash -TF700_421_US_BootRec_Flasher_Signed.zip and was previously unlocked and rooted with 4.1.
The problem now is that TWRP 2.5 is in a resolution that only allows half of the
buttons and options and options to show on the screen. Also re-flashed with -
openrecovery-twrp-2.5.0.0-tf700t.blob and tried with a few 2.4 versions with
same results. This makes it impossible to install any ROM to get out of the boot loop.
Any suggestions?
Click to expand...
Click to collapse
How about try to reflash the 4.2.1 bootloader and twrp using one package zip file? http://forum.xda-developers.com/showthread.php?t=2223492
Thanks for the reply.
That is exactly what I did first with the results mentioned in OP. Will give it another try,
that's why it is a little baffling.
Ok. I've fastbooted the blob from http://forum.xda-developers.com/showthread.php?t=2223492
successfully and am back to TWRP 2.5.0.0 but the resolution problem remains. So I am still boot
looping directly into a recovery I cannot use.
Can I use fastboot to flash the blob from TF700T_US_epaduser_V1061144UpdateLauncher to at least
return to a functional state and try to fix my TWRP problem latter?
dengom said:
Ok. I've fastbooted the blob from http://forum.xda-developers.com/showthread.php?t=2223492
successfully and am back to TWRP 2.5.0.0 but the resolution problem remains. So I am still boot
looping directly into a recovery I cannot use.
Can I use fastboot to flash the blob from TF700T_US_epaduser_V1061144UpdateLauncher to at least
return to a functional state and try to fix my TWRP problem latter?
Click to expand...
Click to collapse
Yeah, it's a good idea, flash back stock firmware to get back stock recovery, root the device then download goomanager from the market then try to install twrp again. I think your recovery bootloader maybe messup(reflash recovery from stock rom should address this issue).
I appreciate your input. Being somewhat new to android need some additional guidance.
Would renaming the stock 4.2 zip file to update.zip and issuing the update command work or is it
more complex?
dengom said:
I appreciate your input. Being somewhat new to android need some additional guidance.
Would renaming the stock 4.2 zip file to update.zip and issuing the update command work or is it
more complex?
Click to expand...
Click to collapse
That's incremental update. You want a full upgrade.
Alright, what wood be the proper way to proceed?
Sorry I need some hand holding.
dengom said:
Alright, what wood be the proper way to proceed?
Sorry I need some hand holding.
Click to expand...
Click to collapse
Alternative Firmware update Method: download full firmware from Asus web site.
1. Unzip the downloaded file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button twice
9. Wait patiently for 10 minutes or so and Done.
Thanks, will give it a try after work.
Also, I should preview my posts b4 submitting for spelling.
Well I think I've found part of the problem. I had to flash a CWM recovery to install the
official 4.2 update successfully. Going into settings I found that my device model has somehow been
change to a TF 300t from the correct TF700t. I believe this may be the cause of my TWRP resolution
problems.
I have no clue how this occurred. But, I do need some suggestions on correcting this.
On a side note booting into recovery now results in a dead robot. I will tackle this once the model reporting is
corrected
dengom said:
Well I think I've found part of the problem. I had to flash a CWM recovery to install the
official 4.2 update successfully. Going into settings I found that my device model has somehow been
change to a TF 300t from the correct TF700t. I believe this may be the cause of my TWRP resolution
problems.
I have no clue how this occurred. But, I do need some suggestions on correcting this.
On a side note booting into recovery now results in a dead robot. I will tackle this once the model reporting is
corrected
Click to expand...
Click to collapse
I suggest you should reflash the full Asus firmware which included the rom and bootloader. Just make sure you download the right version for your tf700 and the correct SKU and you are sure that you have the tf700 right? not the tf300!!
Yes it is definitely a TF700. I will try the re-flash of official 4.2.
Hi, after doing some flashing via Flashfire (xposed and the mod from the only mod thread on the G Flex 2 forums) I had a bootloop. I tried restoring via LG Flash Tool, but I kept getting stuck at 9%. I did a hard reset via button combination, the phone did boot and keeps on working perfectly, a lot better than before, with everything seemingly fully functional.
So I continued my search to find something that's broken and decided I'll try flashing directly from internal through recovery to fix the 9% problem, but I couldn't boot into recovery using the button combination. The combinations for displaying the IMEI and hard reseting still work. I downloaded quick boot and rebooted into recovery, just to be greeted by the red triangle exclamation mark.
I can keep on using it, but it just pisses me off + I probably won't be able to flash Android M when/if it comes out.
So, any suggestions? H950 5.1.1 PR.
TL;DR Phone's ****ed up and recovery's corrupt, halp plox.
Use flashfire to flash recovery.img if you cant find any ask somebody on your device main thread (or you can try cwm with rom manager from playstore)
MarcoPLs said:
Use flashfire to flash recovery.img if you cant find any ask somebody on your device main thread (or you can try cwm with rom manager from playstore)
Click to expand...
Click to collapse
After one year these devices were released, the bootloader is still locked.
Sent from my honor 5X
Yup, exactly like rogconnect said. So, anyone any other ideas? : D (Shameless self bump)
Hello guys
I have a big problem with my TF700t. I have looking similar topics and answers for my problem but didn't find.
Around month ago I wanted to flash new ROM and then in TWRP I ve got "Unable to mount cache". I tryied to make format data but it didn't help. But now I can not event get into bootloader. My device is starting from bootloop on TWRP ( to be specific on flash screen) and stays at it. I can not get into TWRP in any way. Even after battery was down and recharing it - still the same. Also I am not even able to turn device off. But It is recognized in computer but adb not see TF700.
And I am or I was on TWRP 2.8.0.1
Can You have any idea what I could do to fix it ?
Thank You in advance
maciumpek said:
Hello guys
I have a big problem with my TF700t. I have looking similar topics and answers for my problem but didn't find.
Around month ago I wanted to flash new ROM and then in TWRP I ve got "Unable to mount cache". I tryied to make format data but it didn't help. But now I can not event get into bootloader. My device is starting from bootloop on TWRP ( to be specific on flash screen) and stays at it. I can not get into TWRP in any way. Even after battery was down and recharing it - still the same. Also I am not even able to turn device off. But It is recognized in computer but adb not see TF700.
And I am or I was on TWRP 2.8.0.1
Can You have any idea what I could do to fix it ?
Thank You in advance
Click to expand...
Click to collapse
You have to kick your tablet back into the bootloader and you best bet for that is to use bootit.ko that we have thanks to _that.
Follow this: http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495
Yes, that's a guide for the TF300 but this works just fine on the 700 too.
After you are back in the bootloader it's up to you if you follow lj's guide and fastboot flash the Asus stock blob and start from scratch or reflash your recovery and use that to format your cache and data partitions.
If you decide to flash the stock blob you'll have to get the latest firmware for your SKU from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
But you should be able to fix it without that once you have a working recovery and fastboot again.
Hi,
I have similar problem. My Tablet Stuck on blinking TWRP. When i power on my tablet, after asus logo it goes to " 4 Penguins images" then Twrp tlinking "TEAMWIN" logo.
Power + Volume Down buttons do not work. My problem is that my Asus TF700t could not be detected by PC, I have tried on several laptops with windows and linux, i`ve also tried two cables, but nothing - thread: http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page8 is not helping me. Any ideas?
Hi, need some urgent help here.
I was trying to install a custom rom, so I unlocked first the bootloader, then flashed twrp 3.0.2 for Android 5.1 and with it I flashed KangVip rom (porto from honor 6).
Problem was it didn't boot, just black screen.
So I supposed the problem was with the rom so I flashed via fastboot the aosp 6, obviously with same results.
I tried lot of stuff (twrp 2.8.x.x, reinstall stock firmware, restore twrp backup of stock full firmware and so on - I did almost everything I could do) and now I'm with a Huge problem: no huawei logo at start, just a white screen and nothing happen. I have twrp 3.0.2 for 5.1 installed right now but I can't install stock recovery.
Please help me, what do I gotta do?
[emoji30]
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
fazi2015 said:
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
Click to expand...
Click to collapse
Thx for this.
But I have a problem, I can't install stock recovery and if I try to flash the .img files extracted from update.app nothing happens.
Also, I still have that problem with huawei logo disappeared and a blank white screen instead.
Sent from my HUAWEI GRA-L09 using Tapatalk
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Solved, thanks!
Sent from my HUAWEI GRA-L09 using Tapatalk
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
jfer671 said:
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
Click to expand...
Click to collapse
are you have unlock bootloader or not..
fazi2015 said:
are you have unlock bootloader or not..
Click to expand...
Click to collapse
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
jfer671 said:
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
Click to expand...
Click to collapse
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
fazi2015 said:
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
Click to expand...
Click to collapse
Thank you very much....hope that will solve the boot issue and bring this unit back to life
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
jfer671 said:
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
Click to expand...
Click to collapse
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
fazi2015 said:
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
Click to expand...
Click to collapse
Unfortunately, it says the file is no longer available
jfer671 said:
Unfortunately, it says the file is no longer available
Click to expand...
Click to collapse
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
fazi2015 said:
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Click to expand...
Click to collapse
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
jfer671 said:
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
Click to expand...
Click to collapse
I know it's annoying but last time I research more and guide you I was have same problem don't give up....
I send you recovery flash in fastboot no need of usb debugging usb debugging need for adb not for fastboot in fastboot flash recovery by your self download it
https://mega.co.nz/#!GRw0CZjQ!iZllDkA6yJeWk7iEA4vEVA94r2nM_YjAuiS8B9IZdm0
then extract the zip go to resource and hold shift and left click then select open command port here then power off device completely boot into fastboot (bootloader) connect the device to pc and in command port type
fastboot flash recovery twrp_2_7.img
after that type
fastboot reboot and hold the volume- button of device it'll boot into recovery if you success then reply..
I've noticed two things when flashing KK or LP. On KK, the phone does a constant boot loop with Huawei logo (on off on off), but on LP the Huawei logo hangs...it doesn't boot loop. Is this an indication or just a fault with both OS?
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
divvykev said:
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
Click to expand...
Click to collapse
Likely the phone was encrypted
divvykev said:
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Click to expand...
Click to collapse
For me this happened a few times, including when I tried to 'fastboot boot' a wrong image or some latest bluespask Twrps. This is the state when the the phone has hung trying to execute something. The remedy is to hold the power button pressed for something like 10 seconds and the phone will switch off (this is a hardware feature so shlould not fail). After that I go to fastboot normally - press volUp+Power for a few seconds till the fastboot message. Also, make sure that you are not charging, as this seems to have prevented me going to fastboot once.