Develop Bugs

Hello and a hard brick!

After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!

jamguitarist said:
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
Click to expand...
Click to collapse
Post the guide that you followed
You would have to kick your phone into Qualcomm USB Loader 9008 in order to fix it
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/

Trade-offs & Return - factory reset?

I want to love the OnePlus 3 but I'm not feeling it. I'm unlocked, rooted and running X-Posed framework and gravitybox on the 3.1.2 update.
Things that are really bugging me right now compared to the LG G3 I came from:
Lack of SD card. I thought I wouldn't care but I do. The 64GB of storage is enough but it was kind of safety blanket with flashing ROMs that I miss.
Inability to change out the battery. I know, only LG has that now, but it was so easy to carry an extra battery in my pocket compared to a charger or a some device and a cord and look for someplace to charge it. It was great while traveling on long flights or walking around all day to never have to think about where and when I need to charge my phone. I don't know that I want to carry that Dash charger everywhere with me.
The power button on the side - this is where I grab the phone when putting it in my pocket so it keeps turning on when I actually want the screen to stay off. LG buttons are on the back.
The screen - I'm fine with the 1080p and I don't need Super pixel whatever, but the light reflections in various environments are very annoying compared to an LCD screen.
I knew these trade-offs when I bought the phone but I didn't think through how I would feel about them.
Maybe I'm overplaying these in my head and they aren't as important as I think they are but again, I'm not feeling the love because of these trade-offs.
I think want to return the OnePlus 3 and get an LG 5 which has all of the features I want (at a higher price). Or maybe just go back to the G3.
But two things...
1) Now that I'm unlocked and rooted, how should I go about restoring the phone to factory (or near factory)? Should I just restore the nandroid backup I took? Or does it not matter?
2) I can't start the return process because the One Plus system doesn't show I've received it yet - I'm going to call and see if I can get an RMA over the phone, but probably not.

You have just noted all of my worries.
I have a G3 at the minute and i said id upgrade when i found a phone that had :
1) SD slot
2) Swapable battery
3) NFC
I've ordered the OP3 but 2 out of my 3 reasons i "forgot" about.
Not sure how i will cope with side buttons again, or a fingerprint scanner on the front.
After this post, i will for sure not be rooting for a while just in case i end up in the same boat.
A

So do I just go into TWRP, clear the caches, and then install the stock recovery.img file over the top? Then, by not installing the SU binaries I'm no longer rooted, correct? I don't care if the bootloader remains unlocked because they should take it back even if it is.

Its better whene you relock the bootloader.

I found the link - seems straightforward. I already put in a return request.
http://forum.xda-developers.com/oneplus-3/how-to/how-to-unroot-oneplus-3-to-stock-oxygen-t3403324
I'm still not sure why the bootloader needs to be re-locked. It seems like that's something that could result in bootloops and other problems.
The LG G5 is what I want but even the H860 (LTE) is not yet unlocked, only the H850. So, I would get some of the features I want back, but then I couldn't root. If I can't root, then I'm stuck having to make software trade-offs. I may have to just stick with the OnePlus 3 now.

digger16309 said:
I found the link - seems straightforward. I already put in a return request.
http://forum.xda-developers.com/oneplus-3/how-to/how-to-unroot-oneplus-3-to-stock-oxygen-t3403324
I'm still not sure why the bootloader needs to be re-locked. It seems like that's something that could result in bootloops and other problems.
The LG G5 is what I want but even the H860 (LTE) is not yet unlocked, only the H850. So, I would get some of the features I want back, but then I couldn't root. If I can't root, then I'm stuck having to make software trade-offs. I may have to just stick with the OnePlus 3 now.
Click to expand...
Click to collapse
Did you have any luck with this? I can't find stock recovery anywhere.

I did not. I'm not returning the phone. I would have returned it with TWRP anyway. A bug in the bootloader puts me into stock recovery half the time anyway.

digger16309 said:
I did not. I'm not returning the phone. I would have returned it with TWRP anyway. A bug in the bootloader puts me into stock recovery half the time anyway.
Click to expand...
Click to collapse
Yeah I think I'm just going to have to return mine with TWRP. I can't help that they haven't released OOS or the recovery yet.

The stock recovery appears to be available with one of the toolkits I forgot which one it's the one with the cmd prompts just download and get the file from there or use it

Bootloop on Rooted Pure Nexus ROM

*Irrelevant thread*

@Omnitrix4m3
Call Project Fi. Talk to them. They'll probably send a replacement (no waiting for repair). You can always talk to them and then after hearing what they say decide no.

Omnitrix4m3 said:
Wow. I spend so much time on Reddit ignoring these threads until today.
Allow me to set the scene, I'm a student who loves to tinker and modify, and the idea of unlocking my bootloader, rooting, and running custom ROMs on my device seemed fascinating at first. Becoming an avid user of this after fashing my device countless times and performing backups, I began to find a system thatworked for my device and was stable. Having not flashed anything for months on my phone, I had no reason to take a backup of my phone. Until today.
Realizing I had too many garbage apps on my phone, too much RAM being used, and my SOT being garbage, I decided on deleting some of the 222 apps I keep for fun on my phone. With that, I used my phone's built in free space client which cleared unused apps and saved photos. However, it also included my downloads folder where I consciously chose my downloaded ROM and vendor images to save space (Remember, my build was stable at the time and I wanted space to do an eventual nandroid backup). After deleting those flashable files I continued about my day as usual. However, until the end of the day I realized my phone was logged out of my school's wifi, so I logged back in. My phone then began to lag, and a combination of the phone and me using the powerbutton allowed it to reboot. Then it began to bootloop. Normally as a flasher bootloops are easy to get rid of, or may ensue for minutes after flashing a file, however this was consistent and I had no ROM to flash over it, muchless boot to TWRP to do it. I couldn't boot to anything but the system's own recovery mode. I gave the phone some time alone and tried to research how to fix the problem without opening the phone up and soldering. When I attempted again to boot the phone I realized I got boot into TWRP. However, that was shortlived as, when I tried to make a backup the phone froze and rebooted. Going home with my head in my hands, I later tried booting an hour and a half later making my whole boot animation until the very end when the name is shown and the lock screen should load, that's when it began to loop again. I spoke to my father who bought the phone through Project Fi, who recommended me to talk to support. However I just realized: A) If I send it, I lose my data or have it tampered with in a repair. B) If they attempt to boot it, they will see its void of warranty due to the bootloader unlock and rooting and might not honor my warranty (although people have done it after warranty, NOT BECAUSE IT WAS DEVOID BY UNLOCKING BOOTLOADER/ROOTING). C) I bought it on sale for like $250 for 32 GB so money I get back won't cover a Pixel or another phone I can tinker with again with AOSP roms (and I'm not trying to wait two years for Android O, the only other phone I would consider is a OnePlus 5 which launches in the summer and would be around $450).
What would you guys suggest I do?
1. DIY solder and fix
2. Continue tampering to find way to copy off data (I need suggestions)
3. Send it back completely wiped or in way it is to fix
4. Have it replaced with money (and then what phone would I buy?)
And finally do I go to Google Store, Project Fi, or LG to have this issue resolved while ommitting the fact it has been modified?
P.S.: While writing this, this actually booted up for 5 minutes and worked until it crashed and entered the loop again.
Click to expand...
Click to collapse
If you can get into recovery again, do a factory reset and see if it'll boot. If so, take the opportunity to back up your files then flash the factory images to go back to stock so you can get a replacement. Good luck

Phone soft bricked

So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.

Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
First of all, roms from other phones are not compatible with phones other than what it was designed for. If you tried others, that's why it won't boot up. Secondly, if you read all the posting about how do install twrp, it also said there wasn't any way back EXCEPT for your backups. Unfortunately there is no factory images for the Razer phone released as of yet. If you are unable to restore from your backup (or skipped the step and didn't create one) your only choice is to attempt to restore via the backups Xshooter726 made and posted, and if they don't work, you need to wait till the factory images are released and we don't know when they will be out other then a vague "soon" from a community manager on their forums.

Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.

Roxas598 said:
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Click to expand...
Click to collapse
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.

Boltrag said:
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Click to expand...
Click to collapse
Well you're lucky none worked it could have made your problem a lot worse. When factory images release you can flash those if the backup doesn't work but until then you're out of luck unfortunately.
Side note if razer ask for imie etc don't give them it. Might be able to list the device as have being unlocked etc.

Question Grateful for root and bootloader unlockables but ..

I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks

Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13

Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly

jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.

jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.

The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.

96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have

Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.

jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).

Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.