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
Related
I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it
Hello XDA. First post here. I need the pros.
I may have seriously messed up my Nexus S 4G. The "Google" logo appears when I turn it on but there is no lock on the bottom (there was before) and after that, boot animation of the X keeps restarting. Pull the battery. Hold up and power on. Go into Recovery and I end up with the white triangle and yellow exclamation point inside it.
Did I just brick my phone? Any way to get out of this? I have an upgrade available, but I'd rather check out the Nexus4 before buying the Galaxy Nexus. (Nonreplaceable battery in the Nexus4 might be a killer for me.)
I searched around but no other situations were like mine. Sorry if I missed something. Help me XDA. You're my only hope.
mjnouri said:
Hello XDA. First post here. I need the pros.
I may have seriously messed up my Nexus S 4G. The "Google" logo appears when I turn it on but there is no lock on the bottom (there was before) and after that, boot animation of the X keeps restarting. Pull the battery. Hold up and power on. Go into Recovery and I end up with the white triangle and yellow exclamation point inside it.
Did I just brick my phone? Any way to get out of this? I have an upgrade available, but I'd rather check out the Nexus4 before buying the Galaxy Nexus. (Nonreplaceable battery in the Nexus4 might be a killer for me.)
I searched around but no other situations were like mine. Sorry if I missed something. Help me XDA. You're my only hope.
Click to expand...
Click to collapse
What have you done before this happened?
You have relocked your bootloader?
Fix is easy, you'll lose your data doing so.
Unlock the bootloader using fastboot
Install a custom recovery such as Clockworkmod
From within recovery wipe data
Try to boot like this. If it doesn't boot, go back to recovery, wipe everything and re-install your ROM/stock ROM depending on which you have. You can transfer the flashable zip from within Clockworkmod recovery by mounting your USB storage when connected to your computer.
polobunny said:
What have you done before this happened?
You have relocked your bootloader?
Fix is easy, you'll lose your data doing so.
Unlock the bootloader using fastboot
Install a custom recovery such as Clockworkmod
From within recovery wipe data
Try to boot like this. If it doesn't boot, go back to recovery, wipe everything and re-install your ROM/stock ROM depending on which you have. You can transfer the flashable zip from within Clockworkmod recovery by mounting your USB storage when connected to your computer.
Click to expand...
Click to collapse
First of all, thank you polo for helping me out!!!
At first, I was flashing nandroid backups between AOKP, CM10 M2, and CM7. Then it got stuck in a boot loop of a different sort (don't remember the details) and before I remembered to come over to XDA, I formatted some partitions under Mounts and Storage in CWM like an idiot. However I did wipe data/factory reset, wipe cache, wipe dalvik cache and still nothing.
I just googled some directions on unlocking from fastboot, flashing CWM, and from there let's see how it goes. Wish I brought a cable with me to work, but it'll have to wait a few hours. Thanks polo!
mjnouri said:
First of all, thank you polo for helping me out!!!
At first, I was flashing nandroid backups between AOKP, CM10 M2, and CM7. Then it got stuck in a boot loop of a different sort (don't remember the details) and before I remembered to come over to XDA, I formatted some partitions under Mounts and Storage in CWM like an idiot. However I did wipe data/factory reset, wipe cache, wipe dalvik cache and still nothing.
I just googled some directions on unlocking from fastboot, flashing CWM, and from there let's see how it goes. Wish I brought a cable with me to work, but it'll have to wait a few hours. Thanks polo!
Click to expand...
Click to collapse
Well if you formatted system and the like, you pretty much wiped your ROM. If you installed a stock ROM, it's possible your recovery was replaced by the stock recovery, otherwise there should be no reason for your recovery to get wiped.
Rooting again with the whole unlocking process and re-installing a ROM will get you back online in no time.
Welp, it looks like I need a little more help if you don't mind polo. For someone who was rooted, I guess I didn't know much, but learned a lot from this so far.
I flashed CWM from my desktop via fastboot and can now get into CWM. I then mounted the phone as a USB drive and loaded CM7.2 and then installed it. "Install from sdcard complete." after that. Rebooted and now it's looping at the boot animation for CM7.2. Wiped data/factory reset and same thing happens.
What am I missing here?
After I'm in CM, I plan on going back to stock + root.
Make sure you also wipe cache and dalvik cache. If this doesn't seem to work, in mounts and storage format cache, data, sdcard and system then reinstall your rom. Be sure you have the correct rom for your phone and not the crespo4g version or vice versa.
I just followed those exact instructions and it still loops at the boot animation. Damn.
The world needs more people like you polo. Thanks for trying to help me through this!! I have a genuine gratitude for you my friend.
OK, run a log cat with Adb. First night I had mine had serious issues, nothing worked same problem.
If you don't know how to do log cat
Is
Adb logcat > log.txt
Same as if fastboot. Upload that and we can find your prob instantly.
Sent from my A100 using Tapatalk 2
das_webos_transformer, I just PMed you the dropbox link since I can't post links here, but I don't see it in my sent. Did you get it?
I would try the factory images from Google. Make sure the phone is working as per usual and then take it from there.
There are guides on how to do so on the forums. It is very easy.
albundy2010 said:
I would try the factory images from Google. Make sure the phone is working as per usual and then take it from there.
There are guides on how to do so on the forums. It is very easy.
Click to expand...
Click to collapse
Hey Al. Thanks for replying. My problem is I'm seeing too many guides. I know it's a mortal sin to ask, but can you link me to one that you think is done correctly? Unfortunately I need a little more hand holding if that ok with you guys.
UPDATE - SOMEhow, I got CM10 installed and gapps. Just flashed it it worked. I did nothing differently than before. I installed a bunch of apps and that went well. I had a feeling I wasn't in the clear and now I can't restore a nandroid backup, a fancy widgets transparent background goes missing but the text remains, and Swype won't install. It's just weird. I'm more than willing to go back to stock now. If you can provide a link for how to flash the stock images, I'll definitely give it a shot. Thank you!!!
You're all over place so here are some general FYI.
Depending on which recovery was used to make the nandroid you may not be able to restore it with a different recovery.
When you say you can't restore a nandroid and a widget or swype won't restore I am lost. What are trying to restore it from and with what.
Anyways. Stock images are here https://developers.google.com/android/nexus/images
Make sure you download the ones for your device. The sprint d720.
Once the download is finished extract the file. You should have a few .img files and a update zip in there. Take those files and move them to the directory you have fastboot in.
With the phone in the bootloader enter the commands.
Fastboot flash bootloader bootloader file name.IMG
Fastboot reboot bootloader
Fastboot flash radio radio image name.IMG
Fastboot reboot boot loader
Fastboot -w update image name.zip
You can most likely skip the reboot 2nd and third reboot bootlaoders . People seem to do it for some reason. If your device already has versions of the bootloader and radio installed you can skip those flashes as well.
Make sure you change the commands to the actual file names you're going to flash. Can manually type/ paste the names or just hit tab after you typed the first letter. Example. Fastboot flash radio r tab. It should auto fill it in. Check anyways.
If you're not comfortable with this dont do it. Read some more or find a video on YouTube if you're unsure. I am not responsible if you screw something up . End result will give you factory up to date bootloader radio and rom. It also wipes the phone but not the internal storage. The bootloader will still be unlocked so you can relfash a custom recovery later and do what you want.
Guides are all over. Just make sure you're flashing the correct files for your device. The commands and procedure is the same for all nexus devices.
And last if the factory images give you issues then there most likely is something actually wrong with the device. Or you managed to screw up flashing.
Thanks Al! I did all that and am pretty comfortable with this stuff, but when time came to flash the image...
C:\Users\Nouri\Desktop\Fastboot>fastboot -w update image image-sojus-jro03r.zip
error: failed to load 'image'
Same issue without the -w. I'm starting to think something is wrong with the phone. But how can it. It's functioning. is it possible that a hardware problem can cause these inconsistent issues?
Issues
- When I had CM10 installed, it ran choppy. It ran fine when I flashed it a few days ago. I didn't do much and flashed another ROM, but I know the S 4G is capable of running CM10 smoothly. Swipes between homescreens were choppy and so was bringing up the app drawer.
-I couldn't take a screenshot. "Screenshot not saved" or something to that effect
-Swype would get to 100% download and then halt for a few minutes. I'd hit Install and it would just stay there for a few minutes and nothing would happen.
-I couldn't restore from a CWM nandroid that I just made.
Internal sdcard faulty maybe?
THANK YOU FOR YOUR HELP!!!!!
Nevermind! Back to stock! Thank you so much Al!!!! Holy crap you have made me a happy man before I sleep tonight dude!
The last step was actually fastboot -w update image.zip, but it's all good!!!!! Thank you ALL!!! XDA is a pretty special place where you guys help someone to the best of your knowledge. I'm going to pass this forward.
Polo, das, Al, I can't thank you guys enough. Know that you guys helped someone out big time here. Hopefully this makes your day better too!
Hey all. I just wanted to send a quick update your way. I successfully went back to 100% stock thanks to Al's awesome directions. Still couldn't install swype and there were some files on the internal storage that had all sorts of strange symbols and were .01 to 5 GB in size! Clearly there is something wrong here. I rebooted and that all went away actually. This morning I rebooted and I see a notification saying "Damaged USB storage - USB storage is damaged. Try reformating" I tapped it and successfully formatted the storage, but that's my issue all along. Wish I left the notification up there, but I'll get it back and take it to Sprint. Hopefully get a replacement.
You guys freakin rule. You helped me until we all, especially I, were blue in the face. Thanks again!!!
If you're going to take it sprint you should probably re lock the bootloader. They may not check or care but eh
Fastboot oem lock.
That doesn't wipe anything
Fastboot oem unlock does and that would be needed if you wanted to root and flash your device again .
Thanks and yup! I got pretty good at this whole thing now. I feel very good now learning fastboot. I flashed completely stock like you said. It worked. Problems arose. Locked the bootloader and tucked the phone away. If it wasn't for Google Voice, my life would suck right now! Hopefully my trip to Sprint turns out well. A few short hours.
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
twtoned said:
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
Click to expand...
Click to collapse
Looking for one as well. I have not found one.
Recovery is actually preinstalled
I found this just tooling around. Use your favorite file browser, I used
Total commander. /system/vender/itson
The zip file is there. Hope this helps. (Rooted LG ls620)
Could you explain in a little better detail on what you mean Enigmatic177... I'm pulling my hair out Hehe
If anyone makes or finds a working recovery please post it.
Itson is a zip file that was installed after last update it has the basics to unlock the boot loader. I unpacked it used Rom toolbox pro rebooted to RECOVERY did regular reboot system upgraded.
A couple if bit mapp errors 11111. Then I basically flashed CWM.
Before you do this the partitions change from ext2-ext4. I'd advise
Backing them up.
LG Realm & exceed 2 TWRP recovery/fastboot files
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
TWRP recovery help L620 LG Realm
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
I think i know what seems to be the problem. I think i might have accidentally replaced the boot img with the twrp recovery img. i did not make a backup before this happened. is there anything i can do to make my phone boot up to its normal image? thanks
Nope. It is officially a paperweight and no one I know of has access to the stock ROM either.
Sent from my LGLS620 using XDA Premium 4 mobile app
Hey
Has anybody found a custom rom?
Finally. Easy as pie
Ok, I downloaded an image (w5c_twrp_bumped.img)
put that img on the root of my sd card
downloaded Rashr from the google play store
opened rashr and tapped 'recovery from storage', navigated to external sd and tapped the image and tapped
ýes please'
flashed it. after the flash the phone rebooted into the twrp recovery.
then just rebooted back into the system
worked perfectly.
im new here im not allowed to post outside links yet, just google "w5c_twrp_bumped.img" should take you to a link for a download of that recovery
i got twrp now as a custom recovery. on my lg realm.
That_One_Person760 said:
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
Click to expand...
Click to collapse
You have the bumped recovery so all i can say if u messed up is to flash a stock rom u can find on google i had to re flash mine a few times messing with root
right on, thanks for the info. I had no problems at all. it all fell in place like i was hoping. The Realm is the easiest device Iv ever rooted, flashed, and messed with. Well, as far as rooting and flashing a custom recovery. dunno bout roms though. Im sure its simple?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
OK, I grabbed and extracted this. I used Flashify to simply flash the recovery (w5c_twrp_bumped.img) and it works like a dream on my LG Realm.
OTOH, trying the same on an Exceed 2 gets me TWRP, but it cannot mount much of anything and the backup fails. After failing, it tells me "No OS found, continue?" I continue and get the message "Appears your device has no Root, install now?' I am absolutely certain I have root, or wouldn't even be able to run Flashify, so I continue and it simply boots into the OS just fine. Perhaps the readme isn't complete, as I see the following file in the extracted folder (resources.zip) with no explanation of why it's there. It "appears" to be a flash-able zip that installs "itson" (whatever THAT is). Note that the Realm has this in the /system/vendor/itson, yet the Exceed 2 doesn't.
Have you actually used this on an Exceed 2? And if so, what am I missing here?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
petermg said:
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
Click to expand...
Click to collapse
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
fathergweedo said:
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
petermg said:
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
Click to expand...
Click to collapse
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
fathergweedo said:
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
Click to expand...
Click to collapse
THANKS!!!! I'll make it a point to flash that to my mom's phone next time I get the chance!
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
victor-zorro said:
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
Click to expand...
Click to collapse
Try reflashing it with the factory original firmware using their own flashing tool.
Once you got it working with that, then you can try flashing it with whatever you want.
Till then, there just too many variables with custom ROM.
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