I posted this in another thread and no one was able to help me. So I am posting it in it's own thread hoping that someone can. I know a lot of people having this same issue.
Guys, I have a brand new Galaxy Tab 2 that I bought yesterday and after following the first rooting guide, the one that uses Heimdall to flash a .pit file and a "boot-bjr.img" file, I'm having a really serious issue.
So I went through the process (not the first time I rooted an Android device) using the original heimdall method and it was easy and simple. After the root I made sure by downloading root checker basic from the Play store. I was indeed rooted. But then something weird started happening. The screen goes into standby by itself after a few seconds like normal, but I can't get it to wake up from standby. I have to shut off the device by holding the power button and then turning it back on again. When I do that it works normally again until the screen shuts off either by me pressing the power button to do it manually, or until the screen dims out into standby. I've tried wiping the cache, I've tried a factory reset, and I've even ran the process again all over using heimdall. I'm guessing it's probably the kernel that gets flashed using heimdall? Please help me out here because I only got this device yesterday and It really sucks that it's not working. Someone suggested that It's the kernel's problem and I need to be running the original kernel which is (Kernel version: 3.0.8-292098-user [email protected] #1 Build number: IML74K.P3113UEALCB). I checked and I'm running kernel version (3.0.8-275757-user se,[email protected] #1) Build Number: (IML74K.P3113UEALD3). He also suggested that I do a factory reset to reset the kernel. I did using the stock recovery and the kernel remained the same modified version. Is there anyway that I can revert back to the stock kernel? Someone please help.
I was able to fix it easily. I found someone online who had an identical Galaxy Tab 2 and had them make a nandroid backup and send me the files over dropbox. I got an md5 mismatch error which was simple to fix after some googling and then the restore went fine. Now I have no problems with the tab and the kernel is @SEP-66 #1 instead of @SEP-103 #1 which was causing the problem.
Related
A friend has the null IMEI issue and I want to try the procedure outlined for the Samsung Captivate in the following thread:
http://forum.xda-developers.com/showthread.php?t=881162
Samsung Captivate Android Development - > RESTORE IMEI and Product Code w/o ADB, PC (ALL DONE ON PHONE) nv_data.bin
I don't think the product code used for the captivate will work with the nexus S. Can someone tell me the product code to use when editing the following lines in nv_data.bin? (copied from the above thread!)
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
Sorry if this has already been conclusively shown as not possible for nexus S. Some people on the captivate thread have managed to restore it using this method and I thought it would be worth a shot.
The nexus S in question is the SLCD version i9023.
Given below are the steps that caused the issue.
==============================================
Some days ago, official ICS for Nexus S was released, but my cell couldn;t auto update because it was running a custom ROM. I tried to follow this procedure to switch to 2.3.3 or .4. (http://www.pcworld.com/article/242759/how_to_revert_your_android_smartphone_to_a_stock_rom.html )
Installing the above ROM, my cell went berserk. The ROM booted fine but 3 of my touch buttons wouldn't light up and keyboard input alignment was all wrong and I had to remove battery and restart it every time I wanted to go back into some other setting.
After 9-10 restarts, I managed to reach the update setting, downloaded Gingerbread 2.3.6 OTA and installed it. It worked perfectly, and I was all set to download ICS and install it. Then I followed this link and installed ICS reaching where I am at the moment. (http://www.addictivetips.com/mobile/manually-install-android-4-0-3-ics-update-on-nexus-s-download/)
This ICS works perfectly fine, except that the phone is not receiving any network signals whatsoever.
I had made Oxygen's backup using CWM's backup feature on the cellphone and I thought I'd restore it, so I did a vol up + power, and selected recover. The cell restarted, showed a dead android, and booted into ICS. Several attempts have resulted in the same.
==============================================
what were the cercumstances when he lost the "IMEI" ?
would you tell us please , so we avoid that from happening to us ?
Thanks
mahanddeem said:
what were the cercumstances when he lost the "IMEI" ?
would you tell us please , so we avoid that from happening to us ?
Thanks
Click to expand...
Click to collapse
Have updated the opening post with the answer to your question.
Hey, so basically I'm in a situation where I have no idea what to do.
I recently just got a new phone, and am going to give my Samsung Galaxy S3, SGH-T999V model - from Wind Mobile to my Dad. Basically, when I first got the phone - a couple months after, I decided to try Rooting it, and I did, successfully. Since I didn't really know what to do with my rooted phone, I decided to unroot it - then tried rooting it again some months later, but it didn't work successfully. Basically my phone wasn't rooted, but I had the "Team-Win" recovery on it.
I wanted to bring my phone back to it's original state - and have the stock recovery on it. After some Googling, my solution seemed to be to flash the stock rom for the SGH-T999V model onto my phone using Odin. And I did that - and it worked successfully. But I still couldn't check for OTA updates or anything, it said my phone had still been modified in an unauthorized way.
Now that I need to give the phone to my Dad, I have to format the device and erase everything. This is where my problem starts. When I try to format it (using the Stock recovery), I see a bunch of error messages, with the Android logo falling down in a kind of dead way. I reboot my device, and nothing changes.
It still has all my data, and everything on it.
Sorry if this is the wrong area to post this (I'm relatively new to the forum), and if my problem doesn't make much sense - I've tried being as detailed as possible. Could anyone help?
Hi, thank you for using XDA Assist. Flashing the stock firmware should show you to get ota's. This should have everything you need,http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125. Also, you can ask further questions here,http://forum.xda-developers.com/galaxy-s3/help/help-thread-galaxy-s3-question-t2690307
Thread closed
I am asking for help if anybody here can spare the time. I had my J700P Virgin Mobile rooted and xpose installed. I had notification that I had missed at least one update and wanted to go back to original firmware. I flashed back to original version of firmware no problem and the phone took the update. After the update I was unable to get wifi working again so I tried to reflash the original firmware. Phone flashed fine but when trying to reboot the phone is stuck in bootloop. I have reflashed the original firmware and the new updated firmware several times, tried to restore 3 TWRP backups, everything I can think of and all bootloop. I get the bootup screen - galaxy J7 then it goes to the samsung screen then to the Virgin Mobile screen then loops over and over. Every so many loops it goes to android starting up screen optimizing various numbers of apks, usually 1 of 1. I can do pretty much anything needed, use odin, access adb ect. Any other info needed please let me know. I am at the end of my knowledge on what to do-----HELP!!!!!!! Thanks.
kjslabber said:
I am asking for help if anybody here can spare the time. I had my J700P Virgin Mobile rooted and xpose installed. I had notification that I had missed at least one update and wanted to go back to original firmware. I flashed back to original version of firmware no problem and the phone took the update. After the update I was unable to get wifi working again so I tried to reflash the original firmware. Phone flashed fine but when trying to reboot the phone is stuck in bootloop. I have reflashed the original firmware and the new updated firmware several times, tried to restore 3 TWRP backups, everything I can think of and all bootloop. I get the bootup screen - galaxy J7 then it goes to the samsung screen then to the Virgin Mobile screen then loops over and over. Every so many loops it goes to android starting up screen optimizing various numbers of apks, usually 1 of 1. I can do pretty much anything needed, use odin, access adb ect. Any other info needed please let me know. I am at the end of my knowledge on what to do-----HELP!!!!!!! Thanks.
Click to expand...
Click to collapse
restoring a twrp backup breaks the phone. go here http://forum.xda-developers.com/galaxy-j7/development/twrp-3-0-2-0-beta-j700p-2016-fixed-t3485766 and follow the steps for fixing your efs. then you could flash stock rom again.
Bootloop fix
That did the trick!!!!!!!!!!!!!! You are the wizard of the day. Thanks from the bottom of my heart. I'm trying everyday to learn because I like to tinker with these expensive toys. You saved me a lot of scouring over endless piles of info.
Hello everyone, I am no expert but have installed Rom's for at least a year now. Mainly on my Note 3 but I just switched to my wife's SM-G920T — Galaxy S6. Late last night I was playing around with Kernels on DAMUZ+v4+EPH2 rom. Well one of the kernels has switched everything to be reversed and I can't find a cure. What I mean is in TWRP in order to install I have to hit the wipe button. If I hit wipe it will choose install, if I hit backup it chooses restore and visa versa. I have usually cured any problems in the pass by flashing Odin firmware to start over but it's not fixing the problem. Everything has to be opposite side of the screen to choose the correct choice. After flashing firmware G920TUVU5EPK5_TMB5EPK5_TMB_T-Mobile_USA_6.0.1 odin passes, it reboots and everything looks fine until the phone boots up. On setup of Wifi once again everything is reversed. I don't know what else to do, please any suggestion's are welcomed?
I found the solution by Google search, and someone else had the same issue. The fix for me was the exact same,
Update: Resolved by flashing the stock Marshmallow using Odin, then using *#2663# to reload the TSP firmware. This resolved the issue.
Hello there,
Please forgive me if i posted this thread on the wrong place.
-I would've not posted a thread here unless this got serious, so i own a Samsung Galaxy S6, it's 1 year old phone, when i first got it, i used it normally like everyone else and had no problem with it, but my curiosity got me to root the phone, i still did not get any problem with it until i chose to add a ROM. I used NNE 5.1 S8 port and it was working well until it got my phone broken somehow.
-My phone started acting really strange after 2 months of activity of that new ROM, my phone just started restarting randomly and it got me worried, i thought it's an application problem so i first just factory reset it. It seemed it was not the problem on an application, so i chose to change my firmware to a stock one. I searched up recently on the newest firmware for S6 and i found out it's: XEF (France) , PDA (AP): G920FXXU6ERC1 and CSC : G920FOXA6ERC1 on 2018-03-22. I Downloaded 4 files: BL,AP,CP,CSC , and i found out about PIT on one of the posts in this forum (Filename: SM-G920F-ZEROFLTE_EUR_OPEN.pit).
-Before i flashed with Odin, i wiped System, Data, Cache and Dalvrik Cache. The firmware worked well but after 1 hour it started doing the same thing but now differently. It happend to me only 1 time that it froze up on an application, but i think that is just an app problem. The main problem is that when i lock my screen, i cannot unlock it anymore, it just freezes there until it restarts after a short period of time. After the restart, it just keeps going, restarts, asks for pin, restarts and so on.
I tried removing the sim card and putting it back in, did not work.
I tried Safe mode, still same.
Model of phone: SM-G920F
Current firmware: XEF (G920FXXU6ERC1)
Android version: Nougat (7.0)
If you can help me, or you know something about this problem, please repost here, i would be really grateful since this is my only phone
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
lenovot said:
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
Click to expand...
Click to collapse
How could samsung switch possibly help?
I did flash it with different versions already, but no luck :/.
I've been praying a lot for this lately but it is not working lol
Please Bump this!
try doing this.
1) go here: https://updato.com/
2) choose download 2 roms. 1 nougat and another marshmallow (to my knowledge, stock roms are one file. no more splits and unless otherwise stated... no need for pit)
3) first flash nougat using oden
4) try the phone for a few some time.
if after a set amount of time, phone works fancy and no issues present then it's solved.
if not... install marshmallow. then try again.
if all this fails then...
install nougat. as soon as possible afterwards install twrp.
boot into twrp and just leave it there. my twrp locks after a while and screen goes dark until user interaction (just like it's supposed to)
if the same thing happens then its a hardware issue... probably... (i have had my main board fail... kinda similar not similar issue... hope you dont have the same issue and that its just software related)
good luck.
In my case every time there was an update available it would download the whole firmware and by doing so you would get the most fresh and updated version. Also it updates every partition to match