Here's a good one for you:
So, I decided I wanted to try for a more permissive kernel, so I decided to flash new firmware to my T510 and get the latest Nexus ROM version from @Magendanz. The last time I had Nexus, the Nethunter chroot that I also install granted me y-cable support. I wanted that back (I'm going to try my hand at kernel building next). Anyway, I flashed the BUA1 firmware through Heimdall (I linux), and due to my past successes, I proceeded to flash the matching TWRP and OS in quick succession. I was somewhat concerned upon completion about the very long hangup on the Google loading screen during bootup (hours). So, I got impatient and decided to try again. I was unable to get Heimdall to initialize, and while rebooting I missed the key-combo for recovery and ended up successfully booting the Nexus ROM. So, now I'm running TWRP and NEXUS ROM (both BUA1) on a machine with BTH4 firmware (verified via multiple sources).
So, I guess my question is: Should I be concerned? Do I have a magic tablet? Can I monetize this power? But, really, has anyone else had this happen with bricking a device? Is there any good reason to leave it as is? Should I start fresh from firmware? Do you know of a kernel that'll flash to my T510 that will run an external wifi adapter?
Thanks for the advice.
Related
I'm writing this as a new Nexus 7 2013 owner so that people with a moderate level of tech savvy and are still on the fence about unlocking and flashing their device can check it out from a non expert perspective. I think a lot of times people are afraid after reading tutorials and a bit intimidated by the procedures (and XDA).
I decided to get a nexus device because they are very well supported here on XDA and the general consensus is they are nearly impossible to hard brick barring a hardware issue or the user doing something really really dumb
After unboxing the device I put it on charge while making some final decisions on what direction I wanted to go with the "rebuild". As you will see some of these decisions will have cascading effects...
I settled on cleanrom 2.6 and the elementalx kernel, I also decided I wanted to use CWM (non touch) recovery instead of TWRP because I'm familiar with it and hoped that I would not spend enough time to justify having a gui.( and ... to be honest I am not a fan of TWRPs gui ).
So now that I have made my decisions for better or for worse it is time to proceed. I powered on and configured the device for the first time. Since I wasn't paying attention Google started downloading all my apps from Play. This was not a big deal but folks on a data plan might want to make sure they read the screens and decide not to restore their apps. The option for OTA upgrade was available from jellybean to kitkat, so I went ahead and proceeded with the OTA. In retrospect it was a waste of time because you can download the stock images and reflash them later if you want.
ADB and FASTBOOT were already on my Debian desktop and working properly so I went ahead and unlocked the bootloader, then rebooted and flashed CWM. I them installed supersu from CWM. (I left out the part about using adb to push the files but you get the picture...) So far so good except there was a fatal flaw in my plan. Cleanrom and ElementalX both use aroma installer, which doesn't work on CWM. So as I was doinking around In CWMs advanced options looking for a slim possibility of salvaging the situation I managed to end up in the key test application. The problem here being that since the device doesn't have a back button there was no way to get out of they key test. No worries though I simply connected the USB cable fired up adb and did "adb reboot". A few minutes later I had downloaded and installed TWRP and was ready to pick up where I left off.
Here is a note for folks doing this for the first time, read the instructions and erratta for your new kernel and ROM carefully before you proceed so that you avoid time consuming issues. By reading up a little before I started the project I knew that the ROM and kernel were compatible and work well together. I also knew that I would need to install the ROM first, then the kernel, because I I installed the Kernel first I would have to re-install it after flashing the ROM. No point in doing it twice, right?
SO I fired up TWRP and did a factory reset in preparation for flashing the ROM. So far so good. Cleanrom installed, but AROMA did not ask for my installation options. Fearing something was wrong, I clean flashed (wipe first then flash) the ROM 2 more times with the same result. After the third flash I said wth, as long as the ROM flashed and works I can always change software on my own. So a quick reboot and test drive of the device confirmed the ROM was installed and there appeared to be no glaring issues, so I went back to recovery and flashed the kernel. BTW I did check the md5sums and verified that the files were correct and not corrupted.
I know there is an option to flash more than one update with TWRP but since the install did not occur the way I expected I chose to install the ROM and kernel separately, I'm sure some more experienced members of XDA will agree with this decision and others will say that "it's nexus, go ahead and flash the ROM and kernel at the same time, you can't break it
Anyhow the kernel installation went fine and AROMA prompted me as expected before installing. Note to newbies like me, reading the thread really helps, Knowing exactly how you want to configure your kernel before you install it will save you hassles down the line. Expect the first boot to take a little extra time.
In nutshell, there really is no reason to be afraid of installing a custom kernel on your Nexus device. Sure the possibility is there for you to screw things up, but unless you do something very drastically wrong you wont brick the device, trust me -- If I can do it you can do it. Just think ahead a little and prepare yourself by downloading the files you need and maybe even writing yourself an outline of the steps. I'm sure that I could do this again and again now without referring to notes or tutorials, but having them readily available for guidance and reference was comforting.
I could continue with the saga of getting Debian to recognize the tablet in MTP mode but this post has already gone long and that is a rite of passage...
Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA
One thing you might try here, and another here.
dvandam said:
Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA
Click to expand...
Click to collapse
There are flashable zips of TWRP floating around to update and the TWRP thread in our section says to use the TWRP Manager app on the Play Store. As far as using ODIN, you won't be bricked. The unlock icon shows up when it detects the system files aren't stock/root is in place. Your bootloader should still be in tact, and if you can still boot into recovery that confirms it. Either way, you just need to use a different method to update TWRP and you should be fine.
Well I feel like a f-ing nimrod..
I failed to mention in my description that when I first tried to install, not only did I get the Unlock icon, but I got the "Software not authorized by AT&T..." error message that prevented me from doing anything. However, I thought this was related to my phone being carrier locked. I found out later that my phone was unlocked a while ago so that wasn't it. Had I looked more closely at the error I would have seen that it was a Kernel error. Turns out I had to install a LOKI'd Kernel. Not exactly sure why, but that was the only one that worked. Now the new ROM is installed and I'm restoring my apps now.
If nothing else, I got my TWRP updated finally, so I like to think this wasn't all for naught. Thanks for the insight anyways. This was easier than doing an ODIN back and forth.
This is because you're on the MDL bootloader. You need to search the forums for your phone in regard to the MDL bootloader and loki'd ROMs. When you see the "software not authorized. .." message, it just means you need to flash a loki'd kernel for your device. Search for Jeeboo's Recovery and Kernel and you should be right a rain. Good luck.
Edit: I was half awake when I tried to answer your question, and somehow missed that you had discovered the loki'd kernel already. The reason for this is because the MDL bootloader is susceptible to the loki exploit, which for all intents and purposes is the equivalent of unlocking the bootloader. I've been using Jeeboo's recovery for a year or so and never had an issue with any ROM I tried. The kernel cones in handy for those that need a loki'd kernel. There's a ton of easy to find info in the forums to help you get a better understanding of the MDL and how loki applies to it.
My N7 has been getting laggier recently - accepting the 5.1.x OTA updates was clearly a bad idea, and possibly the 5.0.x ones. So I have been thinking of giving it a new ROM after this past weekend.
Last night, it started bootlooping, getting to the initial 'swipe to use' main screen but not accepting any touches and then crashing to a restart after a few seconds regardless.
I long ago used the Nexus Root Tool Kit to root it and install TWRP. The most recent OTA 5.1.1 update involved an update to TWRP to version 2.8.6.0. So let's install a new ROM!
I can boot into TWRP and, while there, the NRTK will also talk to the Nexus 7 over USB.
In both of them, plus a console using fastboot commands, I can wipe and format partitions. By telling TWRP to use 'rm -rf' rather than formatting, I can also get its partition repair info to think, for a while, that the partition in question is empty. But looking again reveals that it's just as full as it used to be and indeed, whether or not the formatting, flashing and installing a .zip file appears to work - including fastboot commands reporting success - no files appear to actually change on the device. NRTK will believe it has successfully installed the latest 2.8.7.0 TWRP or any ROM, but rebooting finds the old ones still there. Even all my data is there, despite repeated wipes and reformats, including to different file systems.
What can I try next? At the moment, I am just grateful that this happened before I'd tried installing a new ROM because I'm not blaming myself for all this.
lovingboth said:
What can I try next? At the moment, I am just grateful that this happened before I'd tried installing a new ROM because I'm not blaming myself for all this.
Click to expand...
Click to collapse
It's now not powering up at all. Whatever it is, it looks terminal.
Poo.
Hi XDA Community!
I can find information to about almost single topic, but the big problem is, i dont know where exactly to start with and the correct order of all of these steps.
What i wanna do is, like on a pc, format the whole phone, delete everything and set up a custom rom and root the phone.
My first step was trying to root it because i dont know if the root is related to the OS or to the phone kernel.....
I tried the CF-Autoroot procedure from XDA-Forum http://forum.xda-developers.com/showthread.php?t=2219803 but i experience the same issue as many other users. When i click start the process starts, but gets stuck immediately when it comes to the imaging step. Then i get no response from my phone or Odin anymore, the bar wont process for hours.
I tried different USB ports, same result. But i can exchange data from phone OS to pc via USB without problems !
So im kind of thrown back now and i dont know what to do or where to start. Can anyone help me ?
5 Years ago i cooked a rom for my Sony Xperia X1 and put it on my phone without any problems lol, and now with Samsung i get only problems.....
If you want to put a custom ROM on it you only need to flash a custom recovery.
This can be done, also, with Odin.
The only other steps are with ADB or root.
TWRP have install instructions (for all methods) on their site.
One important thing is that you also have to take your device model into consideration. Some models (AT&T & Verizon) have locked bootloaders, which make the whole process of rooting and flashing a pain in the butt.
GDReaper said:
If you want to put a custom ROM on it you only need to flash a custom recovery.
This can be done, also, with Odin.
The only other steps are with ADB or root.
TWRP have install instructions (for all methods) on their site.
One important thing is that you also have to take your device model into consideration. Some models (AT&T & Verizon) have locked bootloaders, which make the whole process of rooting and flashing a pain in the butt.
Click to expand...
Click to collapse
My phone is NOT locked. But my question was the correct ORDER of these things to do. Please read my question carefully. What I do first and what comes next ? I also want to root my phone for full acess
C128D said:
My phone is NOT locked. But my question was the correct ORDER of these things to do. Please read my question carefully. What I do first and what comes next ? I also want to root my phone for full acess
Click to expand...
Click to collapse
I read it and I told you.
If you want to put a custom ROM on it, you have to flash a custom recovery First!
Recovery and root are two independent things. The only reason to root first would be if you want to backup your apps and data of your current ROM.
Custom ROMs are pre-rooted
Otherwise flash a custom recovery, put the ROM zip on your microSD card, boot into recovery, wipe the phone, flash the ROM.
And don't forget about gapps.
Since you said you've already flashed ROMs before, this shouldn't be anything different from what you did before.
Well, it was a lot easier on my Sony, even cooking the rom was a first time success. Here im struggling really hard since i feel im running around in circles, not able to proceed...
First of all some details to my phone:
Android 5.0.1
API Level 21
Bootloader I9505XXUHOJ2
Build ID LRX22C.I9505XXUHOJ2
Java VM ART 2.1.0
OpenGL ES 3.0
Kernel armv7l
Kernel V 3.4.0-5978264 (I9505XXUHOJ2)
Root No
Thing is, every source tells me that I need TWRP or a different custom loader to flash the ROM. But i cannot install it since my phone isnt rooted and the ODIN root-method fails for me, since the process stops right in the beginning at the recovery.img, like its hung up. I tried everything from different USB ports to disabling windows firewall and enabling USBdebugging in the developer settings of my phone... Still same result, no sucess....
Is there any way to do this via Kies ? What should I do ?
C128D said:
Well, it was a lot easier on my Sony, even cooking the rom was a first time success. Here im struggling really hard since i feel im running around in circles, not able to proceed...
First of all some details to my phone:
Android 5.0.1
API Level 21
Bootloader I9505XXUHOJ2
Build ID LRX22C.I9505XXUHOJ2
Java VM ART 2.1.0
OpenGL ES 3.0
Kernel armv7l
Kernel V 3.4.0-5978264 (I9505XXUHOJ2)
Root No
Thing is, every source tells me that I need TWRP or a different custom loader to flash the ROM. But i cannot install it since my phone isnt rooted and the ODIN root-method fails for me, since the process stops right in the beginning at the recovery.img, like its hung up. I tried everything from different USB ports to disabling windows firewall and enabling USBdebugging in the developer settings of my phone... Still same result, no sucess....
Is there any way to do this via Kies ? What should I do ?
Click to expand...
Click to collapse
There are 3 methods to flash TWRP:
1) Root and Flashify
2) Odin
3) ADB
Since rooting with Odin doesn't work, maybe you should try flashing recovery with Odin.
Have you tried a different version of Odin or a different Windows version?
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
ertech said:
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
Click to expand...
Click to collapse
It seems that the bootloader files for OS 6 (TZ and LK) are incompatible with OS 7.3.1.5. I found that you could not even shut down the tablet when it was bootlooping: holding the power button down for >30 seconds did nothing. To stop it you need to open the tablet and disconnect the battery.
You will need to copy a version of OS 6 onto a micro SD card (change the file extension from '.bin' to '.zip'). Insert the micro SD, after reconnecting the battery and putting the rear shell back on. You should be able to boot into recovery (TWRP) with the left volume button/ power button. Wipe system and data then flash the OS 6 zip.
Locate the newer thread for unlocking the HD 8/ 8th gen. tablet (amonet-3) and download the latest amonet version (currently 3.0.1) and the 'return to stock' zip, then follow the instructions in that thread to return to stock. Essentially you unzip the two downloads, merge, and run the return to stock script. From TWRP you boot the tablet into hacked fastboot mode and the script will restore stock boot and recovery images (unpatched). After a reboot you should be able to enter standard Amazon recovery mode. If you then ADB sideload the OS 7.3.1.5 software you will eventually boot into OS 7 (Pie).
Link to 'amonet-3' thread: https://forum.xda-developers.com/showpost.php?p=80166353&postcount=1
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
madman said:
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
Click to expand...
Click to collapse
I've had no luck unlocking the Karnak (or Mustang). I think there a couple of issues. The unlock doesn't work with the OS 7.3.1.5 bootloaders, you get a bootloop. I expected this as it is only the very first version of the Karnak LK file (OS 6.3.0.0) that has the necessary vulnerability for a full unlock. However if you use a modified version of Amonet to flash the OS 7.3.1.5 PL and TZ plus the OS 6.3.0.0 LK you get a bootloop, even without unlocking and unpatched stock boot and recovery images. It may not be impossible, I am hoping that the unlock authors (@xyz` and @k4y0z) will take a look at some point.
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
ertech said:
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
Click to expand...
Click to collapse
OK, if you just want to unbrick it is quite easy. If you have the latest TWRP (you will have if you unlocked with amonet version-3 for thIs tablet) it is likely that your bootloaders are unchanged. To get out of the bootloop you can either disconnect the battery or let it run down. Then you should be able to boot into recovery. From there you can flash a backup of your previous OS, or wipe system and data and reflash a stock OS 6 update.