Develop Bugs

[SOLVED] [Q] Help - getting stuck on boot screen after trying to revert from JB to GB

Hi guys.. I tried installing jelly bean on this device (i8160p and it's not mine) using odin and a stock 4.1 rom I got from samsung updates(I have no root and I went from a never-touched stock)... All went fine, It's working and has all the features. Except that now its owner is asking me constantly to revert back to the original os, since he did find 4.1.2 very slow. So I went back the same path as in the first place in an attempt to get the original gingerbread : I downloaded a stock 2.3 from the site and then tried flashing it.. All again went smooth, with no problems, until I got stuck on the bootscreen and noticed that there was no way to access recovery(download mode working fine though)... So what I'm left with now is a non-booting gingerbreak or the possibility to stay in jellybean(flashing it still works), I'd prefer if I could go back to GB; I think the problem is that there was some conflict caused by jellybean which will require a reset that I can't of course do since I can't boot into recovery, and I don't see any way to install a custom recovery. So can this be done any other way, I'm afraid I'll break this phone before I'll even come up with anything since this is my first experience with roms and boot on an android;
info : as I mentioned There is no root (for now. I might however get into that from jellybean, but I'd rather not if it's possible) and the model is i8160P . an emphasis on the P here since it's the reason I can't find any custom roms, and all I'm left with is the stuff in here
Edit : got gingerbread back after following what angrybb has suggested

Flash the working JB, and after that root your phone like here: http://forum.xda-developers.com/showthread.php?t=2139263 Reboot to recovery and after that follow the howto: http://forum.xda-developers.com/showthread.php?t=2352064 just in step 8 use original gb firmware.
If you can't get adb root access from stock recovery then flash kernel with cwm, for jb for example this: http://forum.xda-developers.com/showthread.php?t=2304432 or this http://forum.xda-developers.com/showthread.php?t=2171054
After flashing one of those kernel, again follow: http://forum.xda-developers.com/showthread.php?t=2352064 , again in step 8 use gb fw

Ok I'll see
Thanks man I'll try what you suggested as soon a I can...
I have a question though: now I noticed that some people fixed this issue by dowloading some other parts (.pit and something else), but of course I'm unable to find these for the model with the P... Now If someone can please tell me if these files have anything to do with the re-partion option in odin(I heard that it does format everything and not just put things on top of things).... Is using it safe given that I don't mind losing data, or should I stay away from it ?
For angrybb : the phone still shows as i8160p in the about section and has access to network...

Here there is a lot talking about pit files, some tehniques with flashing one fw after another, but with no real explanation why this should be done this way. I dont like doing things like that, i want to understand what i am doing. I still haven found some in depth info about pit files.
Anyway, i upgraded from GB to JB with kies, after that i compared some parts of fw and pit file is not changed. Pit from GB and JB have same md5 in my phone, so it is the exactly same file.
I know that method i suggested is not short and plain easy but it is tested and working.

Thanks
Sorry for the delay... For anyone with same problem just follow what angrybb has suggested, but do not under any circumstances ignore backing-up CSPSA_FS and MODEM_FS if you care about your phone's ability to make calls !

hey, maybe you guys could also help me out? i came from a custom ROM that i was having problems with so I wanted to go to an official ROM instead. Originally i came from a GB stock ROM, then i went straight to CM 10.1 but i didnt have any signal on my phone so i tried flashing original stock 4.1.2, now im stuck on the boot screen and i cant access recovery mode. please help?
P.S. my phone is i8160

Updater Binar in Zip Error

Hi all,
I've searched for a bit, and found a few threads similar, so am just posting this up to see what my exact situation requires. Basically, I have been running a rooted HTC One for a while, and flashing custom ROMs and Kernels all the live long day using TWRP fine without issue. My mom wanted tethering on her S3, so while home over break, I rooted her phone fine using Odin, and am now trying to install CM 10.2 onto her phone using TWRP (hers is version 2.6.3.1, mine is 2.6.3.0) and keep getting the following error:
Error executing updater binary in zip ....
The "...." is the path to the ROM on her phone. Coming from virtually the same recovery, I am not sure what the problem is. I've seen that possibly it could be looking for a different version than I am installing (I downloaded the d2spr version of CM 10.2) or that I may need to downgrade the a lower version of TWRP.
If it is the first problem, does anyone know the model number of the Sprint Galaxy S3 that I should be using?
An if it is the second, how do you flash in a new recovery with an S3, is it as simple as using Odin and the PDA option on there? I'm very new to S3 rooting.
This has happened for CM 10.2, CM 10.1 and now LiquidSmooth 2.9. Each time the exact same error, any help would be great for someone who is new to the S3 scene!
Thanks in advance!

Bump, anyone know what's going on with this?

OK, so I've attached a picture to this message. Any help would appreciated, I tried downgrading the recovery and that didn't work, exact same error. These errors are from flashing CM 10.2, and then LiquidSmooth 2.9, virtually the exact same errors for each.

odin flashing for upgraded roms to install?

I've been running a version of cm12 on my galaxy tab s 8.4 WiFi (t700) tablet for a while and had twrp 2.8.5 installed. I recently wanted to see how far roms have come and what was out there. I noticed there were recent lollipop roms and even marshmallow in the wild now! No matter which ROM I try to install now, i get a black screen when it goes to reboot and simply won't boot. With button presses I have managed to get into twrp (hold buttons on boot) and restore an old lollipop rom of mine. I'm not new and know all about clean flashing (which is what I did). Then i start reading and some of the threads talk about how you need the newest official bootloader from now on. I have now updated to the newest twrp (2.8.7.2 and I have a few questions regarding a few things:
1. Why do new lollipop roms all of a sudden require a bootloader change? I have lollipop roms saved in restore (2 different ones) but those are 5.0.2 roms. Could the fact that the new ones are 5.1.1 be the difference here?
2. If i just update the bootloader alone will that trip Knox?
3. Why is knox so important not to trip? Will it eventually not allow installation of roms in general?
4. I noticed there are a few versions of the new boot loaders here. Which version should I use? Also, those are listed as needing to be extracted and re-tared as there was a mistake with the upload. I think I've done it right but does it matter if the new tar I created is just called sboot.bin (same as contents)?
5. Will doing this update hurt any of my root stuff?
6. Anything else I should know?
I do not plan to run official firmware on this tab. Thanks to anyone and everyone for the help. Great information available on here!

flashed P5210 stock rom, but needed P5220 stock rom

i flashed my tab 3 10.1 P5220 to P5210 because i have 2 tablets. The first one is the P5210 and i have with odin selected the same rom on my P5220.
so now i have on my P5220 the software of the P5210. If i go in download mode with the P5220 you see this: PRODUCT NAME: GT-P5210 ////// CURRENT BINARY: CUSTOM ////// SYSTEM STATUS: OFFICIAL
so i have wiped cache and factory, and have try to install the P5220 stock rom. But in odin the proces stop! i have used newest version of odin, and the 3.07 and 3.08.
When i use kies it downloading, but it doesnt install. So kies doesnt work for me. I have tried installed roms with sideload,odin,kies,smartswitch.
what do i wrong?
UPDATE: i see on sammobile i need PDA and CSC number for original download, for my country are 5 different roms. So i download the other 4. Maybe it helps!
sammobile is this weekend not available, i just need 2 roms more. 1 rom is installing 99% and then fails. When i reboot then i receive firmware warning. choose kies etc.
LAST UPDATE: I see there is a strange thing! somebody have changed the parts on the tab 3! I looked into the SIM slot. and there is no hardware for it, but in the case is a SIM port!!!! i check serial number on back, and that is from a p5220. The part inside says P5200/P5210/P5220 And another serial number.... i checked that. But i dont know from what device that is! So i have now december rom latest installed from cyanogenmod.
everybody thanks for the help!
CYA!

Help with flashing an S8+ to Oreo

Hello! Figured I would ask here since all my searching only seems to get me bits and pieces of an answer.
Before we start: I have an unrooted S8+ on VZW (hence why I'm posting here). I got it running Nougat about a year ago. When 8.0 was leaked on the S8+ subreddit, I downloaded and flashed using sideload. Not the first time I've done it, everything went well during the install.
Flash forward a few weeks. My phone begins to randomly lock up and restart, oftentimes several restarts consecutively. I figure it must be something wrong with the download. Something must have been incomplete. I uninstall apps, try and troubleshoot in safe mode, everything.
So I hear about Odin, and I am told to download it and flash new firmware to my phone as a means of fixing it. I download the newest version I could find (3.13.1), and the newest version of the USB drivers from Samsung (ver1.5.65.0), straight from Samsung's website. I figured if I flash Oreo again, I might be able to fix the solution. Having experienced the frustration for a month plus, I read up on how to use it.
I downloaded my firmware from SamMobile. I selected the 8.0 build from the VZW section. I compare the builds. I was running CR1. The build number on their site was CRB9 (taking a wild guess and assuming the B stands for beta). I download and flash using the new version of Odin. I made sure the right files were selected for each slot (BL matches BL, AP matches AP, etc.). I selected the CSC file (not the HOME_CSC, although I did go back and try with the HOME_CSC as well). I added in the USERDATA. I made the right options are checked in the options tab. I hit start and let it sit, keeping an eye on it. It goes through everything. I see a green "pass" at the end, so I figure I'm good to go. It reboots into recovery, I wipe system cache and do a factory reset (already backed up all my data). I go to reboot, and now my phone is stuck on the "Samsung Galaxy S8+, Powered by Android" screen. It stays there for a second or two, then bootloops to the same screen.
So this morning I find out about an alternate site called "Updato". I hear people recommend it so I went there. I filtered my results to VZW, USA. I download the most recent version of Nougat. It flashes no problem and boots up. I go through the setup and all of a sudden I'm greeted by the TMobile app and not much else (stock apps were present). There's no bloatware either. My system settings had several new and redundant options (a few different system/software update menus for example). I immediately come to the conclusion it's not what I should have. I went through and tried flashing the 8.0 firmware with a slightly older (and theoretically more stable version of Odin (v 3.12.10.1). It has failed in the same fashion, so I'm currently stuck in the bootloop I mentioned earlier.
I can still access the download screen, and the information it lists in the top left corner matches what I had initially if memory serves (I can provide it if required). My question here is what do I do now? Can someone point me to an official 7.0 release for VZW that I can use to get the 8.0 update OTA? Should I switch back to the newest version of Odin or is there a different version I should try? Any help is greatly appreciated!
Edit: I can also access the recovery screen. I am unable to access the safeboot selection screen. Don't know if it helps!