Hey guys I really need your help, my phone has been down for the past 3 days now. I followed this guide:http://forum.xda-developers.com/showthread.php?t=547133&page=2. I will state that I am new to the forum so I cannot post on the actual how to, due to rules, or I would have. Basically i have made it all the way thru the guide, to the point where it tells me to:
- press MENU to power off! (do not reboot)
- hold HOME and POWER to boot into recovery mode
- apply update
once I reach there I have no way of resetting the phone so I just pulled battery after it said the cyanogenmod was installed from sdcard. I flashed the splash.nb, but now all that happens is my phone loads up the MyTouch 3g screen freezes for a few min then restarts and goes back into Android System Recovery screen. I really need your help and would be forever great-full if someone could lend me a hand. I will check back regularly.
Thank you very much ahead of time for whoever lends me a hand.
Troubled Guy With Non Working Phone
OP here
Come on guys someone has to have had this problem before. Even if you are sending me to another link who has dealt with this before it will still be a help.
First of all, I'm not familiar with your phone. But I will try to give you a few ideas and see if any of it works for you.
If you have a recovery installed and you have flashed Cyanogenmod, then you are rooted. I'm not sure how your recovery works, but you should have to use the volume buttons & power button to navigate recovery - or something similar. If you can get into recovery, you should be fine.
Go to the wipe menu and wipe cache/dalvik cache. If these weren't wiped properly before flashing, this could be the culprit. There should be an option to reboot, you may have to choose go back a couple times to find it. If that doesn't work, try flashing a different rom. You'll need to wipe everything in recovery (except the SD card) first, then choose "flash zip from SD card".
If your battery is almost dead, don't try flashing anything, just wipe. You'll need to get an external charger or a full battery before flashing anything.
Again, I don't know how your phone works, I have an Evo & pretty much just treated your post as such. It's a start, though. If you can give me more info, I can try to help further.
I also just noticed this is an old method for an old version of the phone. You do have the phone this was made for, correct? Have you tried sending a pm to the OP?
There is most likely an easier, newer way to root, but what's done is done. It also seems like it may be using Amon Ra recovery? If that's the case, that's the recovery I use so I can help you out there. You may also want to look at how to unroot and get your phone back to stock, then start over. I'm going in to work, but if you post back I'll try to help you out as soon as I get the chance.
People that can't get the roms beyond stock to work, are your phones activated?
Is it possible to use the Pac Man Rom or CM10 on an unactivated phone?
I'm having similar issues to others trying to flash Pac Man and CM10.2. The first boot was fine and I can access everything on the phone fine, including settings. I rebooted and the activation screen (which I skipped as this phone doesn't have service) always pops up but I would like to use it without putting it on a cell network. I can skip the screen fine (until I decide to disable it) but then have issues like the keyboard (physical and touch), systemUI or NAV Bar crashing with a constant message pop up telling me it has crashed. I have returned to stock using RSD and reflashed Pac Man and CM10.2 MANY (15+?) times, doing a clean install 99% of the time but also trying a couple dirty installs to cover my bases. I should also note that I flashed the phone to Cricket but have no plans to activate it anytime soon.
Another thing to note is that I had issues getting the custom roms to boot at all as the initial setup would take hours. One time I though it was a boot loop but I left it on all night and it had booted in the morning. I believe it has something to do with the file check at boot (with my 32GB low speed class SD card) but that seems to be resolved and I can get the custom roms to boot fine (on the first boot) even with my 32GB (witch is fine and has no errors nor is generic, before you ask.) I also have tried 2 4GB cards and a 2GB card, all different brands, with no change in behavior.
I have done everything below multiple times and in different orders.(If needed I can give a direct breakdown step by step but if you could do it with the files below, I have probably tried it)
Wipe the phone (including all storage internal and external SDs included)
Using RDS v6.15
RDS asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (Works 100% of the time and never has issues. I keep reverting back to this if I actually need to use the phone)
RDS ClockworkMod, TWRP, and Open Recovery without TWRP (Tried different versions when available)
Then used each recovery to install Pac Man or CM10.2 (tried 10.1 once but had the same issues and I didn't see the need to troubleshoot a rom people seemed to not want to develop for. So 10.1 was only tried once but has the same issues)
Installed GApps at this point but I also tried alternate versions of GApps and not installing it at all. All have the same effect and don't seem to be contributing to the problems at all.
A few installed I tried wiping the phone again or installing each zip multiple times. I also verified the zips were good when on the device to make sure there was no corruption at transfer.
I also tried multiple (confirmed working) SD cards and installing from the internal storage.
I have tried installing arrrghhh's Kernel too.
The issue ether seems to be boot loop (if it's doing a file check) or more often it works until I get one of the said crashes after a reboot.(blame Tyler message is getting SO old...) The time I see the errors seems to be accelerated if I mess with the settings a lot but I don't believe it is directly related to the settings.
My next recourse is to try and flash it back to Sprint (maybe check my Cricket settings) and see if that helps, without it being activated.
On a separate note.
If people need help I can help get you back to stock easily. The instructions/guides on here are all but useless if you don't know what you are doing already. I have seen down to "USE RDS" or "DELETE LINE MD5" like people would just know what that means. I understand RDS Lite is a standard tool for flashing phones but it's nigh impossible to find real explanations on what stuff does in context. I understand the basics though, so if anyone has any questions I can walk you through it.
To start with if you are stuck in a loop at the start of a new rom and it loops between the 'Welcome' Screen (Select your Language) and Activation screen just skip the initial setup by tapping the corners on your screen in a clockwise manor when on the 'Welcome' screen to skip the setup there is a video to explain it here
pocketnow(can't post links )com/how-to/android-quick-tip-how-to-bypass-touch-the-android-to-begin-video
Without doing this or activating the phone it seems to loop between those 2 screens forever (might indicate part of the problem with customs roms....)
I hope this is enough info to go off of I can give you a play by play with the actual files if you need. Maybe a video if needed and I'm feeling extra fancy.
Thanks for your time.
Hey buddy,
If you're trying to make a guide, make sure you call it what it is properly - RSD Lite.
Also, maybe clean up your post a bit so it's a proper guide (as you point out, it's needed) and make a separate thread for your question.
To answer your question, the unactivated phone shouldn't be an issue in of itself - you'll just get the nag screen like you were talking about.
I know there is an issue some are having with rebooting the 4.3 ROM's. Have you tried any 4.2.2 versions of anything? Carbon, CM10.1?
I wonder if your "flash" to Cricket is causing issue, I'm not sure. Let me know about 4.2.
Edit - I missed this part on my first read of your PM. Taking hours to boot is NOT normal. Perhaps remove the SD card entirely, flash using the internal SD... I've never heard of that. Anything over say 20 minutes is probably cause for concern.
Thanks for taking time to answer me.
In no way was I trying to make a guide yet but I guess I could. I just hate posting stuff without useful content so I figured throwing that in was better than nothing. I'll clean it up and set up some links later today. It's frustrating to try and make a full guide before I can post links that would be needed for it. You are totally right though! (complain about crappy guides and kind of make one... )
Part of my point there was that I can't post out of Q and A and this wasn't really a question so I made a question out of it and that's how my post ended up.
I have flashed many phones before but like I said I'll try and put it back on Sprint later today (probably will be a few hours) as I backed up the settings the phone came with. I know it was a wall of text and not the easiest to read so you probably missed it but I also said in my first post that I tried the internal SD card many times and the taking hours to boot isn't the standard and doesn't seem to happen at 99% of the time. It seems to be related to the recovery software I use as it happened a lot more when I was testing TWRP and none when I use clockwork.
What Recovery do you recommend? I swear they aren't made equal...
I tested CM10.1 once and it had the exact same issues as CM10.2 and Pac Man so I didn't test it further but if you want me to test it I can. I just didn't want the Rom.
I don't want Carbon either but I'll test that and AOKP next. It's just annoying that the stock rom works perfect but I can't get these to function at all. I almost wish I didn't get Pac Man to work at all. I'm very particular about my settings and NEED these features after I tried them Pac Man is AMAZING.
Thank you for the help and I hope I can get this worked out.
PS I saw that you were frustrated about working on a rom you don't have a device for. I hope you don't let a little thing like that stop you as, for the little time I have used it, it's all I want. Thanks again.
Blasz said:
What Recovery do you recommend? I swear they aren't made equal...
Click to expand...
Click to collapse
Well, OpenRecovery has probably the most work done for this device specifically. I liked TWRP, but it seems lately it has been unstable - you're not the first who has reported issues lately. I don't think CWM has been updated, unfortunately - but perhaps that's a good thing, it's stable that's for sure.
Blasz- I was just about to start a thread when I found yours, and it very accurately describes the issues I've been having. Here's my progress so far.
I got my Photon Q with Sprint and used it for a few months before Sprint started finding creative ways to take my "$79.99" bill and make it more like $140 a month. Naturally, I refused to pay. So I had a Photon Q with no cell service. This is fine, as I only need it to work on WiFi, not 2G/3G and there is no 4G in the area. Anyway.
At the time, I had Ice Cream Sandwich on it, using the (latest?) ICS firmware from Motorola. This worked very well, but I later tried to use a newer firmware, and all the custom ROMs had shown up while I hadn't been looking. All of these seemed to be based on JellyBean. First off, I tried CyanogenMod 10.2. Worked amazing well! I had literally no problems at all. However, while I was experimenting with different software for the phone, and wanted to see if "Arrrgghh"(sp?)'s kernels would give me some decent overclocking capability. Turns out, the kernel I picked wasn't compatible with the JB firmwares (I probably picked an older one by mistake.) Needless to say, it now wouldn't boot. It'd go to the "Unlocked bootloader" screen and stay there all night (literally, I tried that.)
So, I went back into CWM, which is the recovery I have installed. I erased /data, /cache and /system, and also the dalvik cache and battery stats for good measure. I also formatted /pds and /modem, I believe, which was probably dumb of me since I'm not sure what those do. Then I tried re-installing CM 10.2 from CWM. The installation went fine, and it works gorgeously. However, there's two weird issues:
1) WiFi and Bluetooth don't even BEGIN to work! Neither does Cell, as far as I can tell, because where CM used to be unable to make calls or access the internet (of course, I've not been paying my bill), it now shows an empty signal bar or "No Signal" (the little red X) in the notification bar ... When I try to turn on WiFi using the slider in Settings, it moves to "ON" (stays gray) and pauses for a few secs, then goes back to OFF. Same thing for BT. If I open the WiFi menu where you select an AP, it tells me to turn on WiFi. I do, using the slider up top, and the same thing happens. WiFi and BT simply won't turn on. Tried fiddling with every setting I can find.
Before this misadventure with the kernel/reinstall, WiFi worked great. I connected to a local AP and was surfing the net and downloading apps.
2) The system takes a VERY long time to boot up. It sits at the "Unlocked Bootloader" screen for up to a whole minute. Then it goes to the Cyanogen screen for about 30 seconds. Then it gets to the homescreen. It's fine so long as you let it boot up, but this doesn't seem normal.
Next I tried other ROMs thinking that might help. I installed AOKP, PacMan, CM1.0, Carbon, SlimBean, and I think a few others without results-- they all work but WiFi and BlueTooth are dead. PacMan is the only exception-- it boots up and then endlessly gives me "Blame Tyler" errors until I force the machine to shut off.
I also tried an older ROM, since these are all JellyBean ROMs and I wanted to get back to ICS (I'm not that fond of JB's interface) anyway. I was unable to find any ZIPs I could install through CWM of the stock firmware. I found some IMGs that it looks like I could install via Fastboot, but I don't currently have a PC with admin priveleges (it's not mine) so I can't install the drivers to use Fastboot or any part of the SDK. (I can, however, put files on my SD card, that doesn't require privleges.) The closest ROM I found to stock was "TwistedAsanti" beta-1 or whatever it's called. That installs fine, but again, it takes about 2 straight minutes to boot and it's useless after that:
It gets stuck at "Starting Services..." and will sit there forever, even left there all night. Behind this, a dialog pops up saying no cell networks were found and asking if I want to switch to GSM. (i've been trying GSM and CDMA ROMs all this time, I don't need cell access so I doubt it matters which I use. I'm in the USA.) You can pull down the notification bar and get into the Settings, and even launch a couple programs, but I can't find ANY way to get to a homescreen. Task manager shows Circles is running, which is a widget on the homescreen, so where the heck is that screen? .. I try, again, to turn on WiFi or BT without success. The friggin thing just won't turn on.
Did I eff it up by erasing the "PDS" or "modem" partition? Am I missing something obvious or is my phone just possessed?
In a few days I should have access to a computer where I can hopefully use Fastboot and see about installing a stock firmware (wish me luck). Until then, does anyone have a ZIP file I can flash from CWM to get back to an ICS firmware? I managed to find a copy of the stock firmware, in the form of a dump done from TWRP (in .win files). But as far as I know the only way to install TWRP is using Fastboot, and I've explained why I can't do that. I don't know a way to install TWRP from CWM. Maybe I can do it from CM10.2, if I can put APKs or something on my SD card. I can't get it on the network, so I have to copy all the files manually. Needless to say, it's a pain.
After my frenzy of ROM installing, I got frustrated and decided to see if TwistedAsanti would do SOMETHING if I let it sit at "Starting Services" overnight. To my mistake, I left it under my pillow and the system was quite toasty, and the battery had run dead. Plugging it back into the charger, it made a few worrying clicking noises from the speaker, then the green LED came on. This LED seems to mean "I'm charging, but the battery is too dead to turn on for a while." After it sits there a while, the green LED turns off and it just goes black. Or it goes to BOOTLOADER UNLOCKED and bootloops, or goes to black untilyou fiddle with the power button some more. I can once in a blue moon get to CWM. Sometimes it gets to the homescreen. It will charge up to about 4-7% and no further (battery got damaged by the heat?) It doesn't reliably work when plugged in, it likes to shut off at random anyway.
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Epicenter714 said:
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Click to expand...
Click to collapse
Did you try to use RSD Lite and flash the device back to stock?
arrrghhh said:
Did you try to use RSD Lite and flash the device back to stock?
Click to expand...
Click to collapse
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Epicenter714 said:
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Click to expand...
Click to collapse
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
arrrghhh said:
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
Click to expand...
Click to collapse
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Epicenter714 said:
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Click to expand...
Click to collapse
I have no clue what MiniRSD is - you mean RSD Lite?
If it doesn't show up in fastboot devices, sort that out before trying to use RSD.
As I stated previously, if you were on JB and going down to ICS you have additional lines which are needed to remove.
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
fastboot said:
target reports max download size 31457280 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Epicenter714 said:
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Click to expand...
Click to collapse
I would NOT recommend entering those fastboot commands in the XML file manually unless you KNOW what you are doing.
Sort out why RSD isn't working. adb and fastboot are two different things. If fastboot devices shows the device, RSD Lite should work fine. Try again.
Okay, so! Greetings all.
Back about a month ago, I successfully rooted my phone with KingoRoot, flashed TWRP 2.8.0, and installed Crdroid 7.1 Nougat for my D850.
Now, everything was fine and well, besides being one of the very unlucky users to have their phone stop being a beautiful piece of technology and, instead, become very burdensome and aggravating. It would require a battery pull, sometimes two times back to back (if it would soft reset on first pull and get stuck in boot loop), about once or twice every 3 hours, to as often as a few times an hour.
So, I tried something new. I went back to LineageOS' website and looked through the other D850 releases(all of what, 3?) and settled on the AOSP 7.1 ROM.It seemed like it'd be a great idea, having everything functioning and not having to deal with battery pulls every day. Now my phone is practically nonfunctional, as it doesn't receive cell service and can't read SIM cards.
Needed Information:
-Phone is an LG D850, running a (nonfunctional) custom AOSP 7.1 ROM
-Phone seems to lack root access, and can't be One-Click rooted as is (Haven't been successful with any one click program yet)
-Phone is also lacking in recovery (Tried to access via adb, manual hard buttons, and neither worked)
Now for the actual question: What can I do to make my phone function again, whether I have to reinstall my backup of my previous fail (thus requiring TWRP and root) or just get it back to a truly stock ROM?
Thank you all for your time and consideration. I'll check back in the morning.
Warning: I am no expert, in fact I'm barely a noob, but one thing I do well, and that is I always do a backup. That being said it appears there are two paths to salvation. Get your recovery working or go back to stock. If you installed a recovery but can't get back to it try shutting off phone then pressing power and volume down simultaneously. When logo appears release buttons and then immediately press both again. It will offer a decision screen where you use vol up/down to select. Choose yes on both, (it will not reset the phone as indicated). This should get you into recovery, from there you may be able to flash the needed rom, gapps, root, etc. My suggestion is to load the needed files onto your sd card beforehand. If this fails there is the downgrade via LGUP. This is pretty nifty. I had to rely on the expertise of a Mr. Heyelton and his post, https://forum.xda-developers.com/showthread.php?t=2785089. To my knowledge the POS known as the AT&T d850 can only be rooted at KK. Mr. Heyelton's guide can get you there. from there you can stay with stock, upgrade to a higher stock (?) or proceed to root, TWRP and rom the phone. Don't forget to upgrade your modem, https://forum.xda-developers.com/att-lg-g3/general/modems-collection-d850-21r-20f-10d-t3213856.
alliance1975 said:
Warning: I am no expert, in fact I'm barely a noob, but one thing I do well, and that is I always do a backup. That being said it appears there are two paths to salvation. Get your recovery working or go back to stock. If you installed a recovery but can't get back to it try shutting off phone then pressing power and volume down simultaneously. When logo appears release buttons and then immediately press both again. It will offer a decision screen where you use vol up/down to select. Choose yes on both, (it will not reset the phone as indicated). This should get you into recovery, from there you may be able to flash the needed rom, gapps, root, etc. My suggestion is to load the needed files onto your sd card beforehand. If this fails there is the downgrade via LGUP. This is pretty nifty. I had to rely on the expertise of a Mr. Heyelton and his post, https://forum.xda-developers.com/showthread.php?t=2785089. To my knowledge the POS known as the AT&T d850 can only be rooted at KK. Mr. Heyelton's guide can get you there. from there you can stay with stock, upgrade to a higher stock (?) or proceed to root, TWRP and rom the phone. Don't forget to upgrade your modem, https://forum.xda-developers.com/att-lg-g3/general/modems-collection-d850-21r-20f-10d-t3213856.
Click to expand...
Click to collapse
Hey man. I wanted to say thanks for pointing me in the right direction. :good: :highfive: I managed to flash it back to stock, and I'll just figure out a different rom to go with. As far as fixing the issue with the recovery not coming up, I have no idea. It was just messed up, I guess. The phone wouldn't go to recovery even after selecting yes both times on the factory reset screen; it would just go black and a red+blue notification light would pop up. Was weird. Managed to get it to stock though, so it's better than it was. Thank you!
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
jp2572 said:
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
Click to expand...
Click to collapse
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Thank you so much for your help! I couldn't end up using that method because kies would not recognize my device for anything. It did get me inspired to try fixing it again however and it worked!
If anyone ever encounters the same or a similar problem, I just tried re-rooting it using odin and cf's autoroot file. It allowed me to be able to install roms again.
rhricik447 said:
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Click to expand...
Click to collapse
Try updating the bootloader again using odin
When this has happend factory reset
Flash the rom, addonsu and gapps in the same TWRP session
The rom should work then, I've been happily using it for about 6months now