Related
Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag
You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington
When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.
shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.
Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag
So, while I was messing around with my phone, I accidentally screwed stuff up. Unfortunately, I decided to get extra stupid and lock my bootloader. So now whenever i try to unlock my bootloader, boot into recovery or basically do anything beyond using CM11s, I get this youtu.be/tuWRHJA50hA. If any of you have any solutions, please help. If you need any extra details, I will be glad to answer. Thanks in advance for the help.
kurroption said:
So, while I was messing around with my phone, I accidentally screwed stuff up. Unfortunately, I decided to get extra stupid and lock my bootloader. So now whenever i try to unlock my bootloader, boot into recovery or basically do anything beyond using CM11s, I get this youtu.be/tuWRHJA50hA. If any of you have any solutions, please help. If you need any extra details, I will be glad to answer. Thanks in advance for the help.
Click to expand...
Click to collapse
You need to provide more information, like a detailed description of exactly what steps lead to this situation.
Heisenberg said:
You need to provide more information, like a detailed description of exactly what steps lead to this situation.
Click to expand...
Click to collapse
I wrote a detailed explanation on the OnePlus forums so here is it copy pasted.
TL;DR: Recovery won't boot, this happens
I've posted this on multiple sites to get as much help as possible. Check /u/braden26 for my posts on reddit about my issue. What I'm having trouble with is a strange issue when entering a recovery. . I'm guessing my recovery is corrupted or nonexistent, due to a few dumb mistakes I made. I first flashed the wrong rom and soft bricked my phone. At this time it was rooted, running cm 12.1 nightlies and using twrp. After this soft brick, I restored to cm11s, unlocked the bootloader and rooted. I installed sultan's cm12.1, but got another weird issue, so I decided to go back to cm12.1. Here's where my issue begins. When I tried to enter recovery, twrp was gone despite developer option for overwriting recoveries was off. So I downgraded to cm11s and tried again. Then it wouldn't install twrp at all. So I erased my recovery and accidentally hit oem lock instead of unlock. When I tried oem unlock after wards, it would reboot then do this which I already showed . The device runs fine, but I can't update cm11s to 12s or I stall custom recoveries. So I'm in a little bit of a problem here. I'm familiar with how to use fastboot, not all the commands, so don't be afraid to give them to me. Thank you for any help and if you need any more details please let me know.
kurroption said:
I wrote a detailed explanation on the OnePlus forums so here is it copy pasted.
TL;DR: Recovery won't boot, this happens
I've posted this on multiple sites to get as much help as possible. Check /u/braden26 for my posts on reddit about my issue. What I'm having trouble with is a strange issue when entering a recovery. . I'm guessing my recovery is corrupted or nonexistent, due to a few dumb mistakes I made. I first flashed the wrong rom and soft bricked my phone. At this time it was rooted, running cm 12.1 nightlies and using twrp. After this soft brick, I restored to cm11s, unlocked the bootloader and rooted. I installed sultan's cm12.1, but got another weird issue, so I decided to go back to cm12.1. Here's where my issue begins. When I tried to enter recovery, twrp was gone despite developer option for overwriting recoveries was off. So I downgraded to cm11s and tried again. Then it wouldn't install twrp at all. So I erased my recovery and accidentally hit oem lock instead of unlock. When I tried oem unlock after wards, it would reboot then do this which I already showed . The device runs fine, but I can't update cm11s to 12s or I stall custom recoveries. So I'm in a little bit of a problem here. I'm familiar with how to use fastboot, not all the commands, so don't be afraid to give them to me. Thank you for any help and if you need any more details please let me know.
Click to expand...
Click to collapse
You were using a toolkit?
Ok, so TWRP didn't initially stick and that's normal since Lollipop came out. It's in the FAQ thread, so doing some research most likely would have saved you from this whole situation. Right now though you're kinda screwed. With no recovery and a bootloader that won't unlock there's pretty much nothing you can do.
First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated
A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!
@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.
RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.
What did the trick to get fastboot working?
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.
berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.
I never thought that this would happen, especially after 6 years of being an ardent flashaholic but here I am like another noob requesting for guidance.
So it started a few days back when the Flashaholic in me wanted something to divert my mind from the monotonicity of a good ROM.I was using "[8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]" Rom on my 3 year old bacon happily when I decided to try "Crdroid ROM for OnePlus ONE crdroid-4.6".
As mentioned in the instructions I followed the steps to each word i.e. wipe,flash rom and then gapps (using modded twrp-3.2.1-K2-bacon.)and the ROM booted fine.I setup it as usual post boot however I faced few reboots which made me doubt myself so i thought of reflashing the same ROM again but the butter fingers got the best of me and while selecting partitions to WIPE( I guess) I selected some incorrect partition and after the flash my phone went into bootloop..
I tried to boot into recovery but I wasnt able to so but I knew I could boot into recovery using Fastboot so I reflashed the recovery while in fastboot mode and ran fastboot boot TWRP.img as I wasnt able to boot into recovery with VolumeDown+Power.I tried to fetch the nandroid backup but to my astonishment it was gone and my /data partition was wiped clean.I blame myself as I must have done something wrong as I was panicked.
Since then(last sunday)my phone has been in bootloop and doesnt start in recovery unless I boot recovery from fastboot. I have spent countless hours to fix it and the things I have tried already are mentioned below
1)Flash Stock rom (CM11,CM12,CM13)
2)Erase and flash persist.img
3)Flashed CM13 snapshot or bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip followed by RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
4)Flashed coloros and then stock rom(CM11,CM12,CM13) or RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
I have gone through this awesome guide ultimate-answer-to-bacon-flavored- by @Timmmmaaahh ,other noob friendly guides indexes , compilations ,threads on softbrick and hardbrick topics and used almost every tool created for one plus one.
I have ruled out below
1)Volume button not working as I can boot into fastboot fine using VolumeUp+Power button
2)Battery not working as my phone can stay in fastboot for pretty much a day with 50% battery or bootloops throughtout the day
I am really out of my depth and I am trying to find where I had kept my nandroid backup on Laptop/Drive but I dont think even that can help me now.I have lost a lot of precious and Important data due to my panicking and wouldnt want to lose my phone so any help and guidance would be really appreciated.
Hopefully I am posting in the correct place and havent breached any XDA rules!Aplogies in advance if I have
you are sure, that you have flash thr TWRP and not only load TWRP via sideload into the ram?
please post the command, which you have send to the phone
So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>
Stupid thing it seems but try different micro usb cable
vedanth123456 said:
So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>
Click to expand...
Click to collapse
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!
Because I had bricked my phone a few months ago and I changed my USB cable and it worked perfect
kallum7 said:
Stupid thing it seems but try different micro usb cable
Click to expand...
Click to collapse
Thanks mate..I did try that but it didn't endure fruitful results
Timmmmaaahh said:
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!
Click to expand...
Click to collapse
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.
vedanth123456 said:
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.
Click to expand...
Click to collapse
This is weird I just restarted my phone to see if it magically starts but it went into bootloop(displaying splashscreen not boot logo) in contrast to earlier when it died instantly when not plugged in also I can't boot into my recovery now!
Once I am plugged in and the phone is on bootloop and if I hold the volumedown+Powerkey it boots into TWRP properly..
This is just weird and I havent seen this behavious in the past three years of using my old lovely bacon
Try using the color os toolkit https://steemit.com/oneplus/@delusionalgenius/how-to-unbrick-oneplus-one-bacon and even though it says do not use if it is soft bricked use it this helped me
Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.
Timmmmaaahh said:
Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.
Click to expand...
Click to collapse
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.
vedanth123456 said:
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.
Click to expand...
Click to collapse
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Try bacon root toolkit you can perform most of the things very easily.
chineel said:
Try bacon root toolkit you can perform most of the things very easily.
Click to expand...
Click to collapse
Hey man, thanks for pinching in. I'm personally not a fan of these toolkits as one can accidentally lock the bootloader and I prefer manual style because it's educational and you see more of what's going on. It's like I preferred DOS over Windows 3.11 back in the day. That's pretty much the same, right?... ?
Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
kallum7 said:
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
Click to expand...
Click to collapse
Mate ,can you please help me with the link ?
I know I can google it but I just dont want to take chances anymore
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
I'd hate to say I told you so ?
Don't worry too much. The cool thing about flashing with Android is that there's always other ways to get to a working system. Plus, having a fizzled up system is how you'll learn the most about how this all works. You'll be a pro in no time. I personally got seriously into troubleshooting with a hard bricked OPO that had a wasted flash chip. Believe me when I say that's a whole other world of pain.
One question: did you wipe system/data/caches between the CM13 and the crDroid flash? That's kind of important. It would also be useful to mention the versions of everything.
I have no first person experience with broken EFS partitions but according to what I've read you'll indeed have to get ColorOS running. You could try wiping everything again and flash CM13 to see if that boots fine (with working connectivity) but I'm afraid you'll have to go through the whole works: wipe all, flash or fastboot flash ColorOS, get it running (verify IMEI), flash TWRP and backup EFS (MAKE AN EXTERNAL COPY), wipe all again, flash CM13, get it running, wipe all again, flash crDroid + Gapps, wipe caches and boot to a (hopefully) working system. If EFS broke again you can simply restore the backup made earlier instead of starting over.
Mind that when I say wipe all, it doesn't have to include internal memory or you'll be wiping backups you might need later on.
Alright, here goes your 27th attempt. Good luck! ?
mate here is the link https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 even though it says do not use on soft brick devices in your case you are going to have to
Ok so here's the situation: I originally modded the K1 tablet years ago and completely forgot what i did, everything was fine until yesterday when for some reason it was off, when I went to turn it on it loaded into the OS but would immediately power off. I went into TWRP (version 2.8.7.0) and made a backup of my OS in that state. Dumped onto my computer (where I have a backup from 2015 as well), wiped my tablet (Dalvik Cache, System, Cache, Data) and grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod from this guide:
https://forum.xda-developers.com/sh...-cyanogenmod-12-shield-tablet-lte-na-t3055043
and this stock rom from: https://forum.xda-developers.com/sh...rom-hyperstock-mra58k-shield-k1-v1-5-t3522897
however my tablet just indefinitely hung at the nvidia shield splash screen.
Honestly ive been at this for 4 hours and I just want a working tablet. I've gotten lost in firmware updates and some "blob" which i still don't fully understand. I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something. (preferably Lineage because I've read good things but I'll settle for a working tablet at this time)
Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too... I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem) or something because everything i touch is making this worse. I need an idiot proof step by step on how to fix this....
WhenSuddenly said:
grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod
Click to expand...
Click to collapse
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
WhenSuddenly said:
I've gotten lost in firmware updates and some "blob" which i still don't fully understand.
Click to expand...
Click to collapse
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
WhenSuddenly said:
I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something.
Click to expand...
Click to collapse
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
WhenSuddenly said:
Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too
Click to expand...
Click to collapse
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
WhenSuddenly said:
I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem)
Click to expand...
Click to collapse
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.
redpoint73 said:
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.
Click to expand...
Click to collapse
Lol ok Sorry for the lacking in specifics so I'll try again from the top to answer all your questions: Regarding the ROMs I tried I just went down the list of all the popular ones on the xda form as it is presently (so Bliss, CM13, Resurrection Remix, Lineage, and a modified version of the stock rom which I can't find anymore)
when I tried to flash these through TWRP they all bounced back with an error (this was after a clean wipe). I can't elaborate further on that as I can't access TWRP any longer on the device but the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13. So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu. On my PC end (running windows 7) when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Sorry for the brief spastic posting I got very frustrated the other day with the tablet but can now look at it with fresh eyes.
Link to the reddit: https://www.reddit.com/r/LineageOS/...d_tablet_original_lineage_failing_to/eh71q5t/
WhenSuddenly said:
the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13.
Click to expand...
Click to collapse
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
WhenSuddenly said:
when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Click to expand...
Click to collapse
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
WhenSuddenly said:
So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu.
Click to expand...
Click to collapse
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.
redpoint73 said:
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.
Click to expand...
Click to collapse
Sorry for the incorrect terminology its been a while since I've been in the android modding scene.
Anyway when I access the bootloader on my tablet I get the 5 option menu of continue, fastboot protocol, recovery mode, reboot, poweroff. When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
https://drive.google.com/open?id=1zS7FjUB754iSnWal18ch4EiFtHykM0fD
(clearly seeing that I'm having trouble uploading a picture to this website you can tell how far my skill level has degraded in 5 years)
WhenSuddenly said:
When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
Click to expand...
Click to collapse
Selecting fastboot shouldn't change much, as to the appearance of the screen. It should be the same bootloader screen (with options) but should have some indication of "fastboot" being the selected mode. Usually near the top of the screen. I can't say exactly what it should look like, as I haven't used my Shield in a long time (since last summer, when I broke the screen).
If you can confirm the tablet is indeed in fastboot mode (take a photo, and post if, if you like) and still no response to the command "fastboot devices" (no quotes), then something may be wrong with the connection. Try another USB port on the computer, or try another cable.
Also, make sure you have the drivers installed on your PC (first item on the following webpage): https://developer.nvidia.com/gameworksdownload#?search=shield tablet