Hello,
My One SV:
Android 4.2.2 Stock
Moonshine S-Off
HtcDev Unlocked
Custom recovery (TWRP 2.7)
Rooted
When my battery goes to 0% and the phone shuts down, when I plug the USB cable, the phone shows the battery charging sign and then starts in recovery mode, BUT the touchscreen doesn't work, the volume buttons don't work, only the power button works. I always have to wait a few minutes for it to charge up (showing in TWRP 3%+, otherwise it will not power on), remove the battery and the USB cable, put the battery in and power it on, then plug in the USB cable to continue charging.
I have to mention that this was happening also when it was:
Android 4.1.2 Saturn III something mod
S-On
HtcDev Unlocked
Custom recovery (clockworkmod)
Rooted
I've bought this phone second-hand, so I don't know how it behaved when was fully stock.
Thanks,
Sebastian.
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Modding.MyMind said:
The TWRP build you are using doesn't have the proper offmode charging binary. There is a TWRP version which has been built for your device that shall solve this problem for you but I unfortunately do not have the link since it is based on the international K2 variants and I am on a US version.
Another method would be to unpack the TWRP recovery, and unpack your stock 4.2.2 based recovery. Swap the kernel binary from stock recovery over to custom recovery. Then, decompress the ramdisk for both. Swap out the binaries inside the ramdisk as well.
Take note on what arguments you must use to rebuild your stock 4.2.2 based recovery because you must rebuild TWRP using those same arguments. If you do it correctly then this should also resolve your issue.
If you know how to build TWRP from source then I would update the source to reflect more so on 4.2.2. That would be the preferred method if necessary.
Click to expand...
Click to collapse
Well, mine is k2_u. Does that change anything?
fbpw131 said:
Well, mine is k2_u. Does that change anything?
Click to expand...
Click to collapse
Nope
Modding.MyMind said:
Nope
Click to expand...
Click to collapse
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
fbpw131 said:
I've misunderstood, my bad.
Well, I've unpacked my TWRP image, it shows a lot of files, however, if I unpack my "recovery.img" stock recovery, it's "ramdisk" folder it's empty.
Bummer
Click to expand...
Click to collapse
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
fbpw131 said:
So.. before I started installing ubuntu in dualboot with my windows, I checked old.splatterhand's posts, and as always, he posted the compiled version link in this post: http://forum.xda-developers.com/showthread.php?p=41456540#post41457062
Everything works nice now.
Click to expand...
Click to collapse
The version you have linked is for boost, not for k2u
old.splatterhand said:
The version you have linked is for boost, not for k2u
Click to expand...
Click to collapse
ooops, i guess that's why I lost all my data, it changed the partition somehow and it got wiped.
Yup, bad idea!
old.splatterhand said:
Yup, bad idea!
Click to expand...
Click to collapse
So I should flash the old recovery back, the one with the battery issue
At least that.
And pray that no important partition is wiped!
old.splatterhand said:
At least that.
And pray that no important partition is wiped!
Click to expand...
Click to collapse
Too late for praying, it's back on and seems fine. What should I check to make sure I'm ok?
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
fbpw131 said:
The ones from here don't work: https://goo.im/devs/OpenRecovery/k2_u/
Click to expand...
Click to collapse
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
old.splatterhand said:
Use the twrp from 1. post of my thread you have linked.
And live with this bug, its only cosmetical. Or try to find someone who can fix it.
Click to expand...
Click to collapse
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
I've lost only some music and a bloons td 5 savegame but I could have lost much more. I have Sky/One Drive for my photos.
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
fbpw131 said:
It's more than a visual bug. I need to pull out the battery for the phone to restart. I'll be living with it.
Click to expand...
Click to collapse
Don't put your phone off for charging. I never did and never noticed that bug
I'll wait and see if someone will ever build it. I should be able to compile it myself, but it's better if someone that really knows those config params do it. I'm done messing, this was as close to a brick as it can get. Lucky me!
Click to expand...
Click to collapse
I also think so, thats why i never messed with recoveries or kernels
old.splatterhand said:
Don't put your phone off for charging. I never did and never noticed that bug
Click to expand...
Click to collapse
It happens when my battery goes empty. This happens because of another bug.
Well, i don't know how often you use TWRP to flash things or make a backup. But a workaround could be, to use the stock recovery and only use TWRP when you need it.
So, where could find the stock recovery firmware?
Inside this firmware.zip - 33.62 MB
Related
If anybody need recovery, full worked with new 4.1.1 JB get it here.
Moderator Edit:
Link removed as it is proven this recovery can damage your device.
Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app
pawitp said:
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD
Moscow Desire said:
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD
Click to expand...
Click to collapse
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.
Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
this one save´d my TAB!!!
i was able to reanimate it after i messed up ..
THX a lot
pawitp said:
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.
Click to expand...
Click to collapse
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Gigabyte0 said:
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
You should give some info when posting, otherwise it is "unknown".
The boot.img contains the kernel not the bootloader. The kernel source is yet to be released by Acer and we don't know if Acer has blocked the dangerous emmc wipe command (which will randomly brick tablets, the more you wipe, the riskier you are) like I did on my kernel or not.
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
But what it does not, it does not flashes. Freezes and hangs. Have my tab after 30 minutes. removed and restarted, now it hangs in APX mode. Do you have a solution for this?
Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?
meier2009 said:
Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?
Click to expand...
Click to collapse
"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.
"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.
Click to expand...
Click to collapse
Yes, it meant the version of Gigabyte0. Does not sound good.
Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!
NoThrills said:
Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!
Click to expand...
Click to collapse
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD
Moscow Desire said:
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD
Click to expand...
Click to collapse
Maybe you can also let this know on 4PDA.ru, as I am not Russian (and you are) you can probably explain it better:
In the Acer 3.0 Android kernel the command MMC_CAP_ERASE, which has caused all the old bricks, is still present. At least it is in the A110 3.0 kernelsource and I have no reason to believe they would remove it in the A700 3.0 kernelsource but not in the A110 one.
When this command exists in the kernel, and the Recovery also allows it (Recovery can also disable it, but the current A700 recovery doesn't do that), you are almost guarantueed a brick.
If you could translate that to 'the Russians' I guess we can save a few more people from bricking.
Thread Closed
Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!
Obagleyfreer said:
Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!
Click to expand...
Click to collapse
Pointless thread. Everyone knows to find chainfires thread.
boterkaaseneieren said:
Pointless thread. Everyone knows to find chainfires thread.
Click to expand...
Click to collapse
Well yes, but still good to know and please don't be offended by his comment. That kind of comment is indeed pointless! We're all here to learn and have fun, keep this kind of comment to yourself please...
Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.
can we downgrade with this
pnr2020 said:
can we downgrade with this
Click to expand...
Click to collapse
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way
donalgodon said:
Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.
Click to expand...
Click to collapse
Yeah that's what I thought too.
Hopefully we can fix it in time
Obagleyfreer said:
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way
Click to expand...
Click to collapse
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck
pnr2020 said:
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck
Click to expand...
Click to collapse
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122
DjeMBeY said:
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122
Click to expand...
Click to collapse
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Obagleyfreer said:
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?
Click to expand...
Click to collapse
Flashing older firmware with PIT didn't work for me.
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
Let me know if it works for you - unfortunately didn't for me.
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Click to expand...
Click to collapse
Any chance of a step-by-step guide on how you did this? Especially what you deleted. Also is there any chance it would work if you wanted to go back to an older stock ROM? Reason I want/need stock is because I use the Bluetooth RSAP profile - unless anyone knows if this is included in the CM ROMS...
If you boot into recovery does it have any of the KNOX lines or is the recovery with CM different to stock? If so perhaps it would be possible to do something like (assuming I've understood correctly) : Root Phone -> Install CM -> Un CM the phone with a stock ROM?
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
please put up a step by step guide to what you did
pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes
@DjeMBeY
thanks for bootloader and i added here that same bootloader but for Odin cread as tar file
Zippyshare ---> http://www28.zippyshare.com/v/62712373/file.html
no work
DjeMBeY said:
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes
Click to expand...
Click to collapse
Im tested,and not working for me. Im use kt-sgs4 kernel with mh8 rom, with root, busybox and the system is ok...but the bootloader is nt cool, i cant intall any custom rom. No voice, and cant call. Odin .tar file no working nand flash fail...
I think install with odin mh1 rom, and install philztouch recovery and intall bootloader recovery...its fine?Thanx
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.
donalgodon said:
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.
Click to expand...
Click to collapse
Hopefully it helps at least a couple of people.
The problem comes when you need to send your phone back to Samsung for warranty purposes.
Even if you have old firmware, reset flash counter etc. I can bet my bottom dollar when it returns from Samsung they would have flashed the new firmware and new bootloader to your device. They are great like that!!
Like the title says, Official TWRP is now available for download on their site. The other version is 2.7.0.0 (unofficial) and the official one is 2.7.0.2. If you are experiencing any bugs this will probably fix them? I was using the one in our section and it worked fine but I upgraded. Just an FYI...
download - http://techerrata.com/file/twrp2/m8_...0.2-m8_wlv.img
command:
fastboot flash recovery nameofrecovery.img or use flashify from play store
shojus said:
Like the title says, Official TWRP is now available for download on their site. The other version is 2.7.0.0 (unofficial) and the official one is 2.7.0.2. If you are experiencing any bugs this will probably fix them? I was using the one in our section and it worked fine but I upgraded. Just an FYI...
http://teamw.in/project/twrp2/226
Click to expand...
Click to collapse
When I install the app and tried to install it, but it says "No recoveries were found for your device" any ideas?
You have to download the .img file and flash via adb or flashify.
Sent from my HTC6525LVW using Tapatalk
Nice find, thank you
download - http://techerrata.com/file/twrp2/m8_wlv/openrecovery-twrp-2.7.0.2-m8_wlv.img
command:
fastboot flash recovery nameofrecovery.img
andybones said:
Nice find, thank you
download - http://techerrata.com/file/twrp2/m8_wlv/openrecovery-twrp-2.7.0.2-m8_wlv.img
command:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Thanks and added to OP!
PSA: don't use the terminal emulator method as written on the official release site. I think they listed the wrong partition. When I flashed it using that method earlier I ended up with 2.7.0.0 running where the recovery SHOULD be and 2.7.0.2 where my system should be. I had to restore a nandoid to get things sorted back out.
dsEVOlve said:
PSA: don't use the terminal emulator method as written on the official release site. I think they listed the wrong partition. When I flashed it using that method earlier I ended up with 2.7.0.0 running where the recovery SHOULD be and 2.7.0.2 where my system should be. I had to restore a nandoid to get things sorted back out.
Click to expand...
Click to collapse
lol that is funny I wondered what would happen if a recovery was flashed to a system partition =]
It does not seem to work correctly. It cannot see the contents of the SD card directory on the internal memory. It reads the internal memory as being the only 990 megabytes.
HughesNet said:
It does not seem to work correctly. It cannot see the contents of the SD card directory on the internal memory. It reads the internal memory as being the only 990 megabytes.
Click to expand...
Click to collapse
I'm not having this issue. I fastboot the img right when it came out..so far zero problems on my end
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Working fine here too. Can see my files as expected.
FWIW, it's working fine for me too.
Been using Simon's release and no issues at all. Any benefit flashing this over the Simon release version? Thanks
Can anybody confirm that flashing through Flashify works? I'm apprehensive because TWRP Manager and GooManager both say there's no official recovery for this device
I have this recovery installed and noticed something odd. With the phone powered off and not plugged into the charger, when I plug the phone into the charger the phone goes into recovery and then flashes a battery charging screen then back to recovery. It will do this until the phone is unplugged from the charger. Has anyone else seen this?
gris1016 said:
I have this recovery installed and noticed something odd. With the phone powered off and not plugged into the charger, when I plug the phone into the charger the phone goes into recovery and then flashes a battery charging screen then back to recovery. It will do this until the phone is unplugged from the charger. Has anyone else seen this?
Click to expand...
Click to collapse
I have something similar happening with the unofficial CWM. It just went into recovery though, didn't flash the battery charging screen at all. I assumed it was a bug with the recoveries that'll get worked out somewhere down the line.
sparky_005 said:
I have something similar happening with the unofficial CWM. It just went into recovery though, didn't flash the battery charging screen at all. I assumed it was a bug with the recoveries that'll get worked out somewhere down the line.
Click to expand...
Click to collapse
Thanks for the response.
yeah its odd. I wanted to get the device fully charged while it was off and then do some battery life testing.
gris1016 said:
Thanks for the response.
yeah its odd. I wanted to get the device fully charged while it was off and then do some battery life testing.
Click to expand...
Click to collapse
No problem mate. I know it wasn't very helpful but I figured I'd let you know you weren't alone/it isn't a pure TWRP issue.
Flashing via flashify works just fine for me.
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Duckman_UF said:
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Click to expand...
Click to collapse
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
krazie1 said:
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
Click to expand...
Click to collapse
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Duckman_UF said:
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Click to expand...
Click to collapse
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
krazie1 said:
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
Click to expand...
Click to collapse
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Duckman_UF said:
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Click to expand...
Click to collapse
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Is a Gapps package needed for this ROM. Ive used Cyanogen ROM's before just not on this Phone.
Duckman_UF said:
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
Click to expand...
Click to collapse
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Thats what I thought..Thanks! About to dl Gapps and give it a shot.
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Yep flashed fine...no problems.
Duckman_UF said:
Yep flashed fine...no problems.
Click to expand...
Click to collapse
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
krazie1 said:
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
Click to expand...
Click to collapse
Already tried...Various Roms, various versions, 2 versions of TWRP (As stated) Aroma, non Aroma...They all just sit there and churn away on the boot screen or power down the device. I always wipe in that fashion
Man I'm out of ideas, I really want to help but can't think of anything. I'll still look and see if I can find anything.
krazie1 said:
Man I'm out of ideas, I really want to help bit can't think of anything. I'll still look and see if I can find anything.
Click to expand...
Click to collapse
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Duckman_UF said:
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Click to expand...
Click to collapse
Yeah cm11 is what I'm currently using, it recently had a speakerphone issue but its been fixed since 7/30. The only AOSP ROMs that have incorporated the fix are cm11, liquidsmooth & aokp. Here is the section for all the aosp ROMs they are universal so means 1 zip for all HTC One M8 variants.
http://forum.xda-developers.com/htc-one-m8/orig-development
Have you tried a RUU?
young0ne said:
Have you tried a RUU?
Click to expand...
Click to collapse
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Duckman_UF said:
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Click to expand...
Click to collapse
it put stock back on the phone just like it was new out of box. it re installs everything from factory.
Thanks!
GNU con Linux
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh