Hello guys, this is the first time I am posting anything so if I am doing anything wrong, sorry just say what it was and I will try to correct it. Well due to some unfortunate events I needed to get my GSM Galaxy nexus running again, I rooted it a long time ago when I was trying to get into roms and mods, but I had to leave that aside due to some other projects that demanded a little more attention at the time. Since my device was having some battery problems I thought that by updating it the problem could be fixed, at the time it was running CyanogenMod 10.2.1 if my memory is right. I went into the update tab under settings in the phone itself and tried installing CM11 from there. the phone prompted me if I would like to do it and I hit yes, it booted into CWM and it proceeded with the installation. But then it gave the status 7 error and the instalation could not be completed (from what I've read this problem happens when the device is not the one compatible with the Rom being installed, I went in the script and checked it, but it was maguro the same I had used for some time , since my device is a GALAXY NEXUS GSM model. Well I went to bootloader again and then do CWM and found the Rom I was using earlier (the CM 10.2), I flashed it and it was all "nice" and working but the battery was discharging way too fast and I tried it again but this time, for some reason (some times I do stupid things) I deleted some folders from the inumerous 0/ folders my device was accumulating and the CM 10.2 was among them. After I that I tried flashing another CM 11 Rom, an older one to try and see if it went well. sigh.... It did not. The same problem occured and now I cannot flash the working Rom. The Phone boots but it does not get past the google logo and then turns off and boots again going directly into CWM , I tried using Wug Fresh's Nexus Root Tollkit, but since I can't go into the settings of my phone I can't configure the drivers properly and if I try to use the Flash Stock + Unroot option with soft-Bricked/Bootloop option checked it returns that a fastboot device was not found. And hence I can't do anything else. Well I don't know what to do and my knwoledge is fairly limited, so anything can help. I have already searched some solution in other treads but none have given results. Does anyone can guide me where to look or some thing I should do?
Thank you very much for any time spent helping.
Hi,
I will have your thread moved to your device section so the experts who own your device can help.
Good luck!
I have recently traded in my old Nexus 7 2012 for a 2013 model and since day one its been rebooting (a lot) also struggling to boot up (most of the time), It is running android 6.0.1 and after rooting TWRP recovery is not sticking either it seems to revert to stock recovery. After browsing the internet im not sure if its suffering hardware or software problems any help would be much appreciated thanks.
Twrp issue is discussed a lot recently in several threads. Late manufactured N7-13's, the ones preloaded with LP and not JB, have other Emmc chip. Regular Twrp not compatible. But a multirom Twrp is.
Concerning the reboot and boot issue. If already done a factor reset I don't know. Normally Ota's to new version leave a mess with bugs and decreased battery life. I always factory reset before and after big updates. (And easy restore everything with Tiranium). Sometimes via recovery only wiping cache partition is sufficient. Try that first.
Thanks I got TWRP to stick using Flashify and have tried resetting and reflashing but am still suffering from reboots/not booting up im beginning to think its a hardware issue from what ive read online.
Could installing lollipop help maybe then updating to Marshmallow?
After a bit of poking around inside and applying some insulating tape on the ribbon connectors I now have a usable device. Reboots once or twice a day and suffering with issues when typing (getting ip instead of o in portrait mode) so still not 100%. Am now waiting for a replacement tab. Just out of curiosity does anyone know how to find the date of manufacture without the box?
Got a replacement yesterday and what a difference. 100% better than the last one so it was definitely a hardware issue, and I got a refund for the waiting so basically its been a straight swap - my 16gb 2012 for this 32gb 2013 ?
Greetings,
I really don't want this to be a repeat post, so I have spent many days now searching for this answer, not just here on XDA if I was honest, I have links to prove it
The aim is to give a little new life to my old phone, and get off the 4.1 build it is on.
With that said, in summary, I have tried a few different custom ROMs; Cyanogenmod 11 - 13, stable to nightly. PAC MAN ROM for Lollipop, some other roms for KitKat I found else where, but in all these I have not been able to get 4G to work. I understand about updating the Modem, and got the latest version from DocHoliday77's post for the Galaxy S3, in point of fact I tried every modem version for 4.3+ on there
But for all this, and it's been time consuming I never managed to actually get 4G to work as stated
I tried playing with settings in Test Mode (*#*#4636#*#*), changed preferred settings, added APN's, rebooting during certain phases of the moon ... but somehow it all avails me diddly.
Finally I have genuinely tried searching for info on if this just isn't going to happen and that's how it is, but somehow I found lots of posts about other models or networks that made it work more than something saying this won't work (putting aside the info on CM 11 that states it's a known issue and won't work on some build I forget).
Which leads me to this post: I wondered if anyone could point me in either the direction of a 4.4+ custom ROM or other ROM, compatible for SGH-T999 (T-Mobile Galaxy S3), that has working 4G. Or how I can get 4G to work on one of the ROMs I have already tried, kind of partial to a nice CM but I am willing to venture.
Also happy to just hear other input about giving new life to the phone so any feedback welcome
Thanks for your time!
NOTES
======
Using TWRP 3.x for flashing
Phone is rooted
IMEI is visible & fine on custom ROM
4G works on stock ROM
not experienced at this but willing to read
Edit: something I had not noticed before, I install Gapps for most of my tests but never use it. I just tried to download from Play Store, it acts as though I have no connection; waiting to download appears, then eventually it says waiting for network. Yet I am able to browse the net fine with the phone floating between 3G & H+. I don't know if that might help, so figured I should add it.
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
audit13 said:
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
Click to expand...
Click to collapse
That's a really good question, let me see if I can find out how to get my bootloader info and I'll get back to you.
May I ask what the latest bootlader is for the SGH-T999, or where I could find this so I can compare it? I couldn't seem to find it, though the most resourceful post I did find related was T999 UVDMD5 Firmware / Bootloader by mnasledov, though it is also a little outdated it appears, I haven't read my entire way through it yet sorry, I also know the phone is a little outdated too .
So that wasn't too bad to find out
I don't have the latest bootloader if that should match the baseband I install.
Where after a ROM install I get my baseband to T999UVUEOH1, but the bootloader stays on T999UVDLJA.
I haven't quite found where to get the latest bootloader just yet, though I did really spend the last few minutes discovering about the bootloader; if you or someone could find the time to point me in that direction that would be awesome
Simplest way to make sure you have the latest would be to flash the most recent stock rom from sammobile.com in Odin.
Thank you very much @audit13, I do appreciate the time you took out to help me and I also appreciate the point in the direction of what next.
I'll go dig into that for a while and see what to do to be sure, before I start
Looks like this is the latest one, so I will give this a shot : PDA T999UVUEOH1 & CSC T999TMBEOH1, version 4.3.
So just as a quick question, since I've never upgraded the bootloader in this fashion etc., from what I have read this is a one way street correct? And since I am upgrading to stock, then I guess will I lose root, which I will have to go back down the path of for a reinstall, or could I flash my old back up over this from TWRP and in that fashion have the latest bootloader, but keep everything I have for the moment as I investigate a ROM that will offer 4G.
I guess what I am getting at is even if having the latest bootloader and some other ROM with the latest baseband doesn't give me 4G still, can I go back in terms of the OS version to my 4.1.1 and keep things as is with a newer bootloader?
I will investigate this myself too, I just always preferred some additional input when discovering things where possible.
I do appreciate your time, thanks again!
No, you cannot run stock 4.1.1 on a 4.3 bootloader unless it is a custom 4.1.1 rom based on a stock touch wiz rom.
I do not think it is a problem to run the latest bootloader and modem as the latest custom ROMs often require an updated bootloader and modem.
Once on a 4.3 bootloader, you can't downgrade to something older.
Thanks again @audit13, that matches what I have read, I appreciate the confirmation!
Looks like I will be undergoing a re-root etc. so I'll get my information together, have a little more read, see what I need to back up and then jump down the rabbit hole
I'm grateful for your time and help.
If you decide to run a custom rom, just flash a stock rom, then immediately flash twrp via Odin, then install the rom and gapps. No need to root before hand.
Ahh ok, that would have made the most sense. However I didn't have an opportunity to check back on this thread until now so even though you had awesome speedy reply I missed it.
I did manager to successfully flash the stock ROM from Sam's. It did also update the bootloader so THANK YOU very much for that.
I had to fiddle a little to get Odin to recognize the my Galaxy S3 in the end it was simple: after I installed Kies to get the drivers on, I disabled WI-Fi (I use it for my dev work, and then it didn't try to spend time getting other drivers and it all went great. But that's just a note incase maybe one day someone else reads the thread and wonders how, this might help.
I'm just actually restoring a couple f things on the stock ROM, I figured I would have it ready in the event a custom ROM doesn't suit immediately, as I find one I like, then I have a back up of the stock ROM on 4.3 to revert to. Incidentally I just used TWRP manager from Google play store to install TWRP, hopefully it's the same as the flash, except now I know I rooted when I didn't have to
@audit13 Thanks, I know I keep saying that but I appreciate your time the same way I would hope someone else appreciated mine.
Incidentally once ready I will post an update here about the success of getting 4G on Cyanogenmod 12 or even 13 maybe, or someone of the other custom ROM I try, to share that info.
So just an update, I can confirm even with both an updated bootloader and matching updated baseband there is still no 4G on Lollipop Cyanogenmod 12, haven't quite tried any other yet, that was the one I liked the most but I will carry on and get a list as I have time then update here.
If there are any further suggestions I'm all open to them
Thanks [email protected]
Do you get 4G on a stock ROM? You have an LTE capabale sim? You get 4G on another phone with the same sim card?
Right, this SIM gets 4G on 2 other phones it's been in, on this phone on stock ROM it gets 4G too. Reverting back to stock backup in TWRP, from CM12 looks like it tripped knox I think it is, so now the warranty bit is 1 oops. But I managed to Odin back to 4.3 stock, so now I also need to see if I can try to flash maybe to CM 11, which is 4.4.x, or if maybe I'm stuck here. If I can find out I certainly will update the result of 4G testing.
You've been really patient & helpful thanks!
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Shack70 said:
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Click to expand...
Click to collapse
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Morrigon said:
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Click to expand...
Click to collapse
In twrp I wiped system and all caches before installing the rom and gapps. I installed an older version of twrp using Odin and updated it to 2.0.8.7 using the twrp app in the play store. Yes I have 4g/lte. I've seen it switch from lte to h+ to 3g depending on my location so I'm sure it's working correctly. The camera and Bluetooth also work fine. I hope this helps, I'm still learning and most of what I've done is just by following others instructions here at XDA.
Sent from my Amazon Jem using Tapatalk
I definitely appreciate the reply thanks!
I gave the latest nightly CM 13 a shot just now, 7/31/16 version essentially. Not finding any issues with the ROM, can't get 4G to show up no matter what though , even with changes and attempts to APN settings etc. None the less maybe to give my phone a rest I'll just stick with this a while and decide if a newer nightly comes out I want to try, or better yet a stable version at some point. Then I can verify how much I really miss my 4G I guess.
All the previous attempts, including this one always results in 3G to H+ network with no issue, it's just that 4G that never shows up for me.
Incidentally without a serious search around I couldn't even find TWRP 2.0.8.7, it's not on the TWRP manager version I have so curious, I ended up just going with 2.8.0.7, thinking maybe it was a typo?
Otherwise I basically run the same type of install you mention, I also clean dalvik, cache, system & data in my case. Just to confirm that.
I have a slightly off topic question here, if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
@Shack70, thanks for the input, thanks for the guide on your steps, glad I've confirmed I'm doing the same even if I can't get my 4G, hopefully someone on a Galaxy S3 T-Mobile, went through this found a solution, and maybe will let me know what they did too, not sure if you are on T-Mobile or not.
@audit13, also thanks, you've been replying plenty too and I appreciate that also!
One small thing I just came across looking over the logs of the install.
When flashing CM 13 with TWRP, I noticed it said the Target: samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys.
Is it normal and OK for it the be referencing a different baseband/bootloader than what I actually have on my phone?
UVUEMJC vs the UVUEOH1? Where the one as named by TWRP flash is 2 versions older than what I have installed? Not necessarily stating this is an issue, just asking please if this is normal, and I also understand it could be something I have overlooked in my reading, it's been a lot of reading
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
audit13 said:
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
Click to expand...
Click to collapse
That makes sense thanks @audit13, just a few of the questions I had building up.
So that my previous question doesn't get lost, and although I know it's a dying phone for users hopefully this might get some visual
if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
Click to expand...
Click to collapse
Hi folks,
I'm after some information. My Nexus 4 is about kaput now with the battery lasting about 4 hours or so with a full charge so I am looking to move over to my S4 mini for a while before buying an upgrade.
However i don't fancy rolling back to 4.4.2 from 5.1.1 as have got accustomed to it now. so there for I am looking to upgrade/flash it or whatever.
I am quite the novice and have not done this on any phone before so I am looking for a bit of help,
I have looked over xda and read some bits but think someone just telling me would be better, i'm not a tech dunce but I am not 100% confident in this at the moment as there seems to be more than one way of doing this.
What do i need to do first and foremost to make the process go as planned?
I take it I need to "root" the phone first (what does this do ? give me access to the firmware level? is that it?) using a "recovery tool" as they are called (is that right?)
Then after I have done that I can install a fresh ROM onto the phone and basic app's etc.
I have seen these guides:
http://forum.xda-developers.com/showthread.php?t=2364980
and
http://forum.xda-developers.com/gal...i9190-i9195-cyanogenmod-13-0-s4-mini-t3276141
Is it just a matter of following them or are there other things I need to do first, in between or after?
I am not bothered about anything being saved on the s4 mini it can be wiped clean and start a fresh, I don't need any of my data on it backed up
A quick bullet guide or acknowledgement of the two threads above or pointing me towards some better ones would be great and any pointers or descriptions of the acronyms or places in menu's which may have had their names changed or have been moved.
Many thanks Everyone,
Dahools
Hi!, you dont need to worry about anything, the only thing that you need is follow these guides, but make sure if you have the correct variant.
First Install Kies and connect your phone to it( For correct phone drivers). And after phone connect wells, Close kies from task manager.
You Need Odin to install a recovery software in your phone(TWRP, Clock Recovery, Philip). I only used twrp now.
Here is link below with instruction. Download recovery for your variant(i9190,i9192 or i9195 base on your model).
http://forum.xda-developers.com/showthread.php?t=2678420
Suppose if you install TWRP. Boot into recovery, And click Wipe, Do a factory reset , Clear Devil cache, Then go back and install your Firmware(cm12.1 or cm13 for your intended model). And flash Gapps as well. Then reboot. And you are done.
I have tried TWRP for both i9190 and i9192 model. and installed custom roms. Work fine.
Good Luck.
thanks fellas
I went for it with the original links and it worked. (eventually) A bit of user error on my part missing recovery mode on reboot first time and thinking it was done when it wasn't. Only putting the first bit in (root kit v2) then not realising how to flash the next parts. A bit of persistence paid off.
I have a I9195 model and rooting with that clockwork worked then loading the CM13 and then the Gapps. All one after the other in one go finally worked for me! so so far so good, just getting used to Android 6 now I think everything is working though, not put my sim in yet. will do that tomorrow.
If anyone was to follow what I did the big tip I would say is copy everything onto the SD card before you start anything, not as I did at first just putting the first bit on then thinking I can copy the next bit on later . . .
Hi, I'd like to start off by saying I'm new here, and have went over all the newbie threads as best as I can. I appreciate how welcoming this forum is, I never took that much of a deep look at it besides looking at threads in the past for multiple things. Still very new to all this stuff in general. Due to being stuck rn, I cannot provide a proper signature, apologies.
Couple Days Ago- Unlocked bootloader on my Oneplus 7 Pro using adb, flashed TWRP for the then current version for the 7 Pro Guacamole referenced from the post here, then sideloaded Lineage through TWRP. Started using the device and it seemed to have went well and like a pretty average install as far as I can tell.
Note- I'm not sure if I installed TWRP properly, as I was able to boot into TWRP through power button and volume up, but I remember also accidentally booting into the Lineage Recovery at some point after my phone was already rooted after the next step, but idk honestly. I note this bc I seen that there might be another step to permanently install twrp once inside after flashing, but not sure, apologies. My lack of knowledge feels inexcusable with how abundant it is here.
I rooted the device soon after with magisk, which I installed the zip (which was simply placed in main directory) through TWRP, then finished the install in the OS and that seemed to be good. Mention I didn't actually know that the device was rooted after the first time, dumb ik, but I did this maybe 3 times before realizing that the device was indeed already rooted and I did it extra times.
Today I got the notification for a Lineage OS update in the OS. Because I know it's coming, yeah, ik how stupid this was to not make backups beforehand as I already have a good bit on there I don't wish to lose, although I have MEGA for all my super important stuff like my password database, etc. Needless to say, I have learned my lesson. Nonetheless, I downloaded the update and pressed the install button. It said installed and would need a reboot, so I did. Then it got stuck in the boot animation for 1.5+ hours.
Force shutting it off and into fastboot, I could boot into the updated lineage recovery, but no TWRP. I have tried reflashing the previous version of the lineage recovery and it did not make a difference. I also tried flashing the next newest version of TWRP for the 7 Pro running guacamole, but then I couldn't get any further than the bootloader.
I ended up reflashing the up to date version of the lineage recovery and it sat doing nothing for a while, so it's off now. I presume that Nebrassy and other devs for TWRP are working on a version for the new update, but idk how long that takes, not complaining though. (mad respect for all who make lineage, twrp and all this possible) (not to mention I don't even know the root of the problem)
Any thoughts or help would be much appreciated, and feel free to ask questions. I would preferably not have to wipe it all and restart, so I'm looking for solutions, although I'm willing to accept this might be for nothing and take the L. Lastly sorry if I have done anything "wrong" in this thread, lmk if I can do anything better, I appreciate it.