Related
New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even get to the red android error screen.I am forever stuck at the GOOGLE screen or a blank one. When stuck at the google screen it is recognized as Nexus7 but when i try to reset to bootloader (black screen) its QHSUSB_DLOAD.
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.
vinland123 said:
New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even turn it on. My device manager recognizes the nexus 7 as "QHSUSB_DLOAD"
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.
Click to expand...
Click to collapse
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.
cgehring said:
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.
Click to expand...
Click to collapse
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution
Aria807 said:
http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution
Click to expand...
Click to collapse
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?
vinland123 said:
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?
Click to expand...
Click to collapse
If you can get to your bootloader, and follow directions, then the above will work. Good luck!
It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?
vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Why did you try to install the factory images from the old Nexus 7?
vinland123 said:
It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?
Click to expand...
Click to collapse
Glad to hear you got it running again!
http://forum.xda-developers.com/showthread.php?t=2381438
Try this. I had the exact same problem as yours and I fixed it. This works!
vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Not sure if you are clear on this or not but the Nakasi image is for the old Nexus 7. The new Nexus 7 is named Flo and the official Google image will have that as part of the file name (Google still hasn't released a factory image for our device though. However, there are a few unofficial versions floating around on the forum).
I rooted my G2, installed TWRP 2.6.3.1, then tried installing CleanROM 1.0 but it froze during installation, so I held down the power button to reboot and now it won't boot past the LG logo. I tried a bunch of button combinations to see if I could get back into TWRP recovery but I couldn't get it to work. All I could do is get into firmware update mode, which I don't know how to use. Can anyone help me out? :crying:
bryanhayn said:
I rooted my G2, installed TWRP 2.6.3.1, then tried installing CleanROM 1.0 but it froze during installation, so I held down the power button to reboot and now it won't boot past the LG logo. I tried a bunch of button combinations to see if I could get back into TWRP recovery but I couldn't get it to work. All I could do is get into firmware update mode, which I don't know how to use. Can anyone help me out? :crying:
Click to expand...
Click to collapse
You can go into download mode by pressing Volume UP and connecting USB to the computer. Then you can restore the stock from there. There is a post on restoring stock, follow that
Here you go.
http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my VS980 4G using Tapatalk 4
emplox said:
Here you go.
http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
I stayed up until about 4AM trying to figure it out and finally got it working using this link: http://forum.xda-developers.com/showthread.php?t=2432476
Thanks for responding though :highfive:
bryanhayn said:
I rooted my G2, installed TWRP 2.6.3.1, then tried installing CleanROM 1.0 but it froze during installation, so I held down the power button to reboot and now it won't boot past the LG logo. I tried a bunch of button combinations to see if I could get back into TWRP recovery but I couldn't get it to work. All I could do is get into firmware update mode, which I don't know how to use. Can anyone help me out? :crying:
Click to expand...
Click to collapse
Just an FYI, I prolly did not freeze during install...
As I noted in my OP it takes a LONG time to decompress 1.5Gigs of RAM.
These roms take a long time to flash, a very long time for some. Let it flash in recovery. Do what others are doing if you need to even if it seems excessive, take a shower or something leave your phone for a while just let it work its course.
UPDATE: I gave up and restored a backup. I'm wondering if the issue is because I didn't wipe System
Hello everyone,
I'm also stuck at the LG logo. I wiped data, cache, and dalvick in recovery. I installed the ROM. Neither of these steps took a very long time. When I went to reboot, it stated that I was rooted and asked whether I wanted to install SuperSU. Since the ROM description stated that SuperSU was included in the ROM, I said no. After rebooting, I have been stuck at the LG logo for over 15 minutes.
Is it supposed to take a long time during the actual install, or at the LG logo? Should I wait it out or work on my backup plan?
Thanks for the help. I'm very excited about CleanROM.
Hi,
My i9505 Intl (Australian Telstra LTE) SGS4 has been rooted for a year at least now, and recently (a few months) had TWRP recovery and CM13 installed and everything was going great. I loved CM!
Anyway I had done a few nightly patches of CM and all seemed good and then a week ago I installed the most recent nightly (possibly this one cm-13.0-20160819-NIGHTLY-jfltexx-recovery.img ). Well the subsequent reboot put the phone into a boot loop. So I thought no problem just boot to recovery and install my recent Nandroid back up. So did that but in my haste didn't clear cache or data. The nandroid reinstall seemed to go ok but a subsequent boot hung at the CM logo (I think it was a while ago now) and I couldn't boot to recovery, just hung with the blue text.
So I fired up Odin and booted to download and reflashed with TWRP. Boot to recovery still didn't work however I could still boot to download.
Tried different USB ports, different versions of Odin, re installed drivers to no avail. Also tried CWM, TWRP and Philz recovery and once I did get it to boot to recovery with Philz. THIS TIME cleared cache and data and loaded a good copy of CM that I had on my SD card. Again stuck in boot. Couldn't get back to recovery.
Tried loading the orginal samsung firmware and they I was stuck with a Samsung logo boot looping. Ditto recovery just hung at the logo and the blue text "recovery booting".
Rinse and repeat a few times and now the phone has started to become difficult to get into download or recovery. If I leave it with the battery out for a while it seems to come good again.
Odin when flashing a new recovery either hangs half way though or completes and says everything is OK. Full blue bar on the phone.
Rebooting however still leaves me in the boot loop.
There is no mention on Odin of any issues with the partition however I have d/l a PIT file from one of samersh72's posts but am not sure if it is the correct one for my Int phone or indeed if I need to use it as Odin doesn't seem to report any partition errors.
If any one has any suggestions I am very receptive to ideas right now.....
Thanks
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
audit13 said:
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
Click to expand...
Click to collapse
I did a factory wipe and then installed CM from my SD card but that is the only time I have able to get into recovery since the first time when I reloaded my nandroid backup
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
audit13 said:
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
Click to expand...
Click to collapse
Yup tried that, as I realised that the auto boot might be overwriting the custom recovery...........however as a new development I haven't been able to boot to download or even the stuck recovery since yesterday.
I think it has now moved to a full hard brick
Is still turns on? You have a USB jig to try?
audit13 said:
Is still turns on? You have a USB jig to try?
Click to expand...
Click to collapse
No I don't have one but I have all the makings of one so i'll put one together and give it a go. Though I have to say that I am not that hopeful as I can't even get a peep out of it now.
A jig may be the last solution before sending it for repair or replacing the motherboard.
audit13 said:
A jig may be the last solution before sending it for repair or replacing the motherboard.
Click to expand...
Click to collapse
Thanks Audit, Ill let you know how I get on. Just looked at some replacement motherboards and they don't seem too common for the LTE version used here in Australia AND USD60......pretty much get a working phone locally here on ebay for that and I get the rest of the parts too.
Have you tried already flashing a stock rom as a tar file from sammobile?
justgamer01 said:
Have you tried already flashing a stock rom as a tar file from sammobile?
Click to expand...
Click to collapse
Yup did that as well!
Ghostdog1 said:
Yup did that as well!
Click to expand...
Click to collapse
I'm not sure if it will work! But try emergency recovery with Smart Switch!
justgamer01 said:
I'm not sure if it will work! But try emergency recovery with Smart Switch!
Click to expand...
Click to collapse
With Smartswitch I get the same outcome as with Kires
"GT-I9505 does not support initialising. Please contact our service centre."
But on the plus side it is actually responding to button presses today. I will pick up some 100K resistors tomorrow and finish off my USB jig. See how that goes.
Well it appears to have finally died fully. No response to any button or combination of button presses. Made up a USB jig but without some response to a boot that won't work either.
Thanks to Audit and Justgamer for your advice. Think it is time to draw a line under this one and move on. Maybe a new Nexus when they drop?
Hi All!
I seem to be stuck in a bootloop on my 6P. I was running the latest Pure Nexus build, and I was having a bit of trouble with some apps, so I decided to reboot into TWRP and wipe the cache. After booting up again, everything seemed normal. The phone was running for a minute or so, and it just shut off. After that, it just keep rebooting. It's not a normal bootloop. I do not reach the animation, I only get to the screen where it says "google" and has the unlocked padlock symbol on the bottom. After that, it starts all over again with the "cannot check for corruption screen."
To be very clear: I can't boot anything at all, including recovery. I have tried flashing multiple versions of TWRP and multiple versions of the stock recovery.
Here is what I've tried so far:
I have flashed back to the latest 7.1.1 release both manually and using the flash all command
I used fastboot to erase the system, cache, boot, and userdata. I ran the commands normally and also with -w.
I've tried to flash an older version of android - 6.0, I think.
Nothing seems to work. I haven't made it to the boot animation once since it shut down.
I also left it on the charger all night just to be sure. The battery was at about 75% when it shut down.
Thanks!
RMA bro.
mtpease said:
Hi All!
I seem to be stuck in a bootloop on my 6P. I was running the latest Pure Nexus build, and I was having a bit of trouble with some apps, so I decided to reboot into TWRP and wipe the cache. After booting up again, everything seemed normal. The phone was running for a minute or so, and it just shut off. After that, it just keep rebooting. It's not a normal bootloop. I do not reach the animation, I only get to the screen where it says "google" and has the unlocked padlock symbol on the bottom. After that, it starts all over again with the "cannot check for corruption screen."
To be very clear: I can't boot anything at all, including recovery. I have tried flashing multiple versions of TWRP and multiple versions of the stock recovery.
Here is what I've tried so far:
I have flashed back to the latest 7.1.1 release both manually and using the flash all command
I used fastboot to erase the system, cache, boot, and userdata. I ran the commands normally and also with -w.
I've tried to flash an older version of android - 6.0, I think.
Nothing seems to work. I haven't made it to the boot animation once since it shut down.
I also left it on the charger all night just to be sure. The battery was at about 75% when it shut down.
Thanks!
Click to expand...
Click to collapse
Can you get to the bootloader?
I'm going to go out on a limb and say if you flash a factory image and get no errors but it's still boned the way you described then RMA if your answer. Your in an every growing boat!!
Sent from my Nexus 6P using XDA-Developers Legacy app
jhs39 said:
Can you get to the bootloader?
Click to expand...
Click to collapse
Yeah, I can get in to the bootloader just fine. I can flash anything I want wit no errors. I just can't boot anything.
CyberpodS2 said:
I'm going to go out on a limb and say if you flash a factory image and get no errors but it's still boned the way you described then RMA if your answer. Your in an every growing boat!!
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah, google agrees with me. They've sent me a new phone. I wish I could have found a solution, though.
mtpease said:
Yeah, google agrees with me. They've sent me a new phone. I wish I could have found a solution, though.
Click to expand...
Click to collapse
Glad your warranty worked for you. Pure Nexus seems to be a recurring factor in several threads. I've never used it myself. Over in this thread, an experienced user ran into a bootloop that would not clear with a fresh wipe and installation with flash-all.bat or even flashing partitions manually. Flash-all.bat finished with no errors but still looping. As a last resort he used Skipsoft's Toolkit to re-install stock and it worked. The toolkit script formats userdata and cache and this appears to be what solved the problem. Interestingly, he was able to reproduce the problem with PN. After installing it, he went into a bootloop again and the toolkit again got him back to stock. So, others that are stuck in a bootloop especially after running or updating PN should try formatting userdata and cache, or use the toolkit.
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
garylawwd said:
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
Click to expand...
Click to collapse
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
4tson said:
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
Click to expand...
Click to collapse
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
Yeah, I may or may not have already tried hehe.
You wouldn't happen to have a rom that's not being hosted on Mega would you? I exceeded my limit when I was 95% done downloading one of them.
I think I found one, whoops.
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Dyeide said:
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Click to expand...
Click to collapse
Yep, I tried that, although I'm not sure the USB drivers I downloaded were correct, since the official page isn't working at least for me. So I downloaded what the websites claimed were the correct drivers, I went into download mode that way, which has some debug info on the top left stating it's in Odin mode, but Odin still didn't recognize it.
I'm pretty sure usb debug options were turned on before this, but I'm not sure if the factory reset could've messed with that, thought I'm assuming it could be part of it.
I'm currently trying to download some custom roms to follow garylawwd's advice, I'll reply once I've got results.
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
4tson said:
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
Click to expand...
Click to collapse
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
garylawwd said:
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
Click to expand...
Click to collapse
Tried this just now, it rebooted twice and on the second reboot it got stuck on the logo once again.
I think I'm done trying to mess around with it, I'll take it to a repair place :/
Thanks for looking out though, definitely appreciate your tips even if they didn't end up working out. :good:
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...nt/recovery-twrp-3-1-2-blue-dogerino-t3768707 Try flashing this recovery it's a newer version.Just download the .img file and install it through twrp as recovery when prompted.
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
DontTouchMaPhone said:
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
Click to expand...
Click to collapse
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
garylawwd said:
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
Click to expand...
Click to collapse
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
DontTouchMaPhone said:
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
Click to expand...
Click to collapse
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
4tson said:
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
Click to expand...
Click to collapse
Are you on stock now?
DontTouchMaPhone said:
Are you on stock now?
Click to expand...
Click to collapse
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
4tson said:
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
Click to expand...
Click to collapse
Wait,so you paid for the repair right?And he flashed you a custom rom?Looks pretty scammy to me..Anyways do you have twrp or stock recovery?