Develop Bugs

CM10.1 crashed and softbricked itself, can't access the file system

I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode

If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.

FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.

According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.

[Q] Secure booting Error! after official update - TWRP installed

This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?

Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?
Click to expand...
Click to collapse
What all have you tried?
A simple shut down and re-start possibly could fix it. Just a guess, but worth a try. You should update to TWRP's latest also.

same problem here
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!

g---man said:
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!
Click to expand...
Click to collapse
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.

Cal-123 said:
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.
Click to expand...
Click to collapse
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done

Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
Click to expand...
Click to collapse
I did a recovery with the LG tools. All my data was backed up so it wasn't a huge deal for me. I can't even remember why I rooted my GPad in the first place.

g---man said:
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done
Click to expand...
Click to collapse
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!

Cal-123 said:
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!
Click to expand...
Click to collapse
Cal-123, thanks, I was restoring backup done with TWRP - same problem (rebooting to TWRP screen, not to system). Still don't know root cause, but problem was resolved by flashing stock KK update by using B2CApp. Obviously root is gone, so back to reading forum
At least can play Deer Hunter again
Cheers!

Help Plz - Boot loop brick, Tab 3 7.0

Hello all,
I've got a Tab 3 7.0 T210R stuck on the Samsung logo with pulsing blue background. I've read through several Samsung boot loop help threads as well as the general Loop noob helper but haven't found a fix yet.
For my stuck T210R, What I've done & can do:
Was rooted with a "patched" stock UK ROM from last March [sorry, don't recall which]
Was running fine until after I tried to install from Play the TWRP Manager, I obviously did something bad! like select wrong device maybe
I can get into Philz, TWRP, & use Odin
I don't have a recovery back up [i really don't care about restoring back to anything - just want it to work, clean slate, ya know]
Tried a couple of latest ROM's through Philz and a stock ROM XAC-T210RUEAMK1-20131122134958.zip though ODIN. They seemed to be successful but I still can't get past Samsung logo
I've tried these ROMS that seem to load but ixna on successful boot afterwards:
ODIN: KIES_HOME_T210RUEAMK1_T210RXACAMK1_1304745_REV00_user_low_ship.tar.md5
Philz: Stock.rooted.deodexed.T210R.zip
Philz: TAB3-T210-HASSAN-ROM-V1.0-kitkat-4.4.2-Aroma-Mods-all Languages.zip
Philz: cm-10.1-20131209(1)-UNOFFICIAL-lt02wifiue.mine.zip
What's killing me is that loading new or stock ROM's SEEM to work - no errors or anything obviously indicative that I'll still be boot looping as soon as I restart. I'm quite desperate and thinking I'm truly bricked.
I haven't yet tried using ADB but if I can use ODIN and TWRP or Philz, will ADB do anything better than what I've already done? I haven't tried anything with the kernel as I can't really understand what to do there. I read and read and read the kernel threads but with my experience its really not as straight forward as rooting or flashing a ROM or software, and I could conceivably screw up worse! I'm mildly experienced at following guides to have rooted and ROM loaded a 1st gen Kindle Fire, Samsung SII skyrocket, S4, Tab 2 7.0, Tab 3 7.0.

No replies or interest? Please help
I'm I in the wrong forum? Did I offend someone? Could really use some input, please.
Any one seen this before? If you've any experience LOSING this battle, please speak up and I'll know to just resign to now owning a pretty white Samsung brick.

Boot to customed recovery under wipe choose format this will zero all partitions then redo

thanks!
andynroid said:
Boot to customed recovery under wipe choose format this will zero all partitions then redo
Click to expand...
Click to collapse
if i could find the "thanks" button I'd use it.
I'm traveling now but definitely try your solution. By "redo" I presume you mean load a ROM. When I wipe I also presume I'll still have custom recovery? I should still be able to ODIN, too, if needed?
thanks again

Yes exactly recovery will not go away once you have formatted the partitions you can now flash a new customed ROM or reflash original FW using Odin..Cheers

Hey buddy wanted to know if you ever found a solution for your issue? I am in the same bind you were in. Can you help guide me. I tried installing the same files you did and to no avail. I bought a Tab 3 T210R from eBay that was stuck in boot loop, I am assuming that it isn't rooted as when I would I went into download mode, it said the firmware was official.

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?

I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.

stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:

I agree. I got it used tho which is an issue.

Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.

stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.

Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.

Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?

stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.

Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.

I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.

MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:

stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.

smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.

S10e - impossibility to install Lineage OS

I need to install Lineage OS on this phone.
After multiple tries several months apart, I am still not in success.
Followed all internet tutorials and sites.
I don't want to install any G apps or any special root-things like magdisk..
I only want pure Lineage OS without any extra applications.
Way I tried and probably ended up like before:
Get newest official samsung ROM installed, update, enable usb debigging and oem, go download mode and go factory reset, get back in, sign in to wifi again, again enable develop. settings and usb debugging, go into download mode, take odin and install through the AP option the TWRP now that the phone is in download mode a 3rd time, supposed to be possible now with OEM unlock.
Most of the names on the way I don't understand, just follow tutorials.
I need to get to TWRP to then finally, as used to always, install Lineage from zip.
But I never get rebooted into TWRP recovery, just forver the samsung one, even when firmware is no longer there - after flashing in ap option the twrp tar again it never boots into TWRP afterwards.
Is there something else i must do? is not getting into oem unlock and flashing TWRP enough to get there?
And after, will the zip install finaly get me to have lineage installed?

Did you try the official guide?
https://wiki.lineageos.org/devices/beyond0lte/
I hope I picked the right phones, otherwise check devices overview.
Alternatively, perhaps this helps:
https://forum.xda-developers.com/t/...-a-graphical-installer-for-lineageos.4509995/
PS: Usually LOS doesn't do TWRP anymore but comes with its own recovery (a/b)

Why they don't do TWRP now?
I saw TWRP tuorial fot s10 on tutorials and it worked
Do I have to give up on TWRP way and od it with the adb commands from PC

frustrateduser118 said:
Why
Click to expand...
Click to collapse
It's because of this new double recovery scheme:
https://forum.xda-developers.com/t/help-understanding-a-b-partitions.3748003/post-75545902
https://source.android.com/docs/core/ota/ab
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
EOD: It's safer, updating happens in the background, then just a quick reboot et voila.
frustrateduser118 said:
I saw TWRP tuorial
Click to expand...
Click to collapse
Yes, it's still there but perhaps you post a link to your guide (or ask there). To me it seems you had TWRP just in your RAM but not your phone?
As for me, I finally gave up on TWRP and use the "crappy" LOS recovery Have way more important things to waste my time on...
PS: Sorry to bring such "bad" news, wasn't too happy with that change myself

Great, I finaly made it work.
I followed the site with turotial on installation and did not try TWRP
First I had to install samsung ROM again
It turned out to still stay unlocked so went straight to download mode and this time flashed Lineage recovery sucesfuly with heimdall
Then it booted up and a half samsung sreen made it seem like there is trouble
but Lineage recovery launched
The adb load from PC did not work so i chose to instal zip from SD even there
Now Lineage is installed
Still don't know how much is randomness, luck and so on
But it's done and hopefuly repeatable

frustrateduser118 said:
hopefuly repeatable
Click to expand...
Click to collapse
I am afraid it is
Well, most of times: Far too often I forget some little prerequisite, too... so started a little text file with steps/reminders.

anyway glad for support sigmund
you re my friend now