Ok so i am not new to rooting and romming, new to this phone but not new to the concept, anyways.. Looking through roms i decided on Pac Rom (GSM Version) BTW yes i am rooted and have safestrap on the device.. i used safestrap and flashed this rom and rebooted to the samsung bootscreen and safestrap boot and after it goes black nothing but if i push the unlock on the side the touch butons at the bottom light up and if i use the volume rocker it will beep up and down like normal just no picture.. i reflashed, nothing, i flash a different rom.. now im bootlooping.. cant use odin (No com port access) so could someone help me out as to how i can get this phone back up and running.. can i have someones stock back up so i can flash it? i just need something.. Im New to XDA hope you all are as helpful and generus as my last site (Moved here because it had more for this new phone so far i like it) Thanks to everyone who trys to give me a hand
Related
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
Hi,
I have the Galaxy S4 i9505 and having issues with trying to root the device. So after reading tons of posts over the last few days with regards to rooting I think I have finally worked out what I need to do and have all relevent files required (Odin, CWM etc).
So I went to put the phone into recovery mode by using the vol+ menu and power button but instead of getting the flashing custom roms warning message and press vol+ to continue it loads to a manual recovery with several options and an icon of dead android icon with a red exclamation mark.
The phone is brand new, not done any rooting on it before, the only thing I did was use KIES to update the phone.
Currently running Kernal 3.4.0-526204, Build I9505XXUAME2.
I'm not a complete noob when it comes to rooting android, have messed with a crappy MOMO9 tablet rooting and flashing different custom roms however this is a little different as this phone costs 10 times as much lol, I've also come over from iphone 4 which used to jailbreak etc.
I have done alot of searching and found guides for other devices, just not sure it will work on my version and brick the phone. Can anyone maybe point me in the right direction or know of a guide to help me resolve this problem.
Many Thanks
Goggers said:
Hi,
I have the Galaxy S4 i9505 and having issues with trying to root the device. So after reading tons of posts over the last few days with regards to rooting I think I have finally worked out what I need to do and have all relevent files required (Odin, CWM etc).
So I went to put the phone into recovery mode by using the vol+ menu and power button but instead of getting the flashing custom roms warning message and press vol+ to continue it loads to a manual recovery with several options and an icon of dead android icon with a red exclamation mark.
The phone is brand new, not done any rooting on it before, the only thing I did was use KIES to update the phone.
Currently running Kernal 3.4.0-526204, Build I9505XXUAME2.
I'm not a complete noob when it comes to rooting android, have messed with a crappy MOMO9 tablet rooting and flashing different custom roms however this is a little different as this phone costs 10 times as much lol, I've also come over from iphone 4 which used to jailbreak etc.
I have done alot of searching and found guides for other devices, just not sure it will work on my version and brick the phone. Can anyone maybe point me in the right direction or know of a guide to help me resolve this problem.
Many Thanks
Click to expand...
Click to collapse
For preparing your phone for Odin for flashing, you should be putting your phone in download mode (volume down, power and home button). This will display the custom ROM warning message, and you press the up volume key to put it in download mode. I'll assume this is what you're trying to do? Then the usual kill all Kies related processes, plug your phone in, wait till odin identifies it, then proceed to flash your file.
P. S. What guide are you following to root your device?
Sent from my GT-I9505 using xda app-developers app
I'm not sure
Hi,
I used a guide from galaxys4root.com I think, as luck would have it my pc crashed just after writing the orig post and my history/recover webpage didnt work, happy days. Its ok I like a challenge, think it helps with learning, wouldnt learn anything if it went right all the time.
I have made a little progress, I tried both vol + and vol -, both put me into manual recovery with dead android logo (i meant to put vol - in my previous post not vol +) Just incase I had a bad upgrade from XXUAMDD to XXUAME2 I reflashed the update using KIES and tried again. This time I was able to go into download mode and managed to get CWM v6.0.3.2 flashed and was able to boot to that using vol + no problem.
Now I have an issue with SuperSU failing to update the binary, I used CWM to load a file called "CWM-SuperSU-v0.99.zip" which I suspect is not correct for my current version so its back to searching for me. Trying to get my head round all the different versions of S4 etc and what works on which device.
CWM-Recovery?
Goggers said:
Hi,
I used a guide from galaxys4root.com I think, as luck would have it my pc crashed just after writing the orig post and my history/recover webpage didnt work, happy days. Its ok I like a challenge, think it helps with learning, wouldnt learn anything if it went right all the time.
I have made a little progress, I tried both vol + and vol -, both put me into manual recovery with dead android logo (i meant to put vol - in my previous post not vol +) Just incase I had a bad upgrade from XXUAMDD to XXUAME2 I reflashed the update using KIES and tried again. This time I was able to go into download mode and managed to get CWM v6.0.3.2 flashed and was able to boot to that using vol + no problem.
Now I have an issue with SuperSU failing to update the binary, I used CWM to load a file called "CWM-SuperSU-v0.99.zip" which I suspect is not correct for my current version so its back to searching for me. Trying to get my head round all the different versions of S4 etc and what works on which device.
Click to expand...
Click to collapse
Hey-
First you should flash a stock rom namely XXUAME2.
Than try this here: http://forum.xda-developers.com/showthread.php?t=2238442
That recovery is stable and reliable. The CWM-Recovery is currently not fully bug-free.
I think SU is included in TWRP, so you don't have to worry about that.
After you've done that, you can flash any custom rom for the GT-I9505.
My recommendation is OMEGA 3.1 and the ADAM-KERNEL 1.3.1+
All that stuff you can find here.on xda.
Good luck -
Your SU 0.99 is too old and doesn't fit at all.
Getting there
Hi,
Thanks for tips and pointing me in the right direction. I have since downloaded a couple of ROM's, both pre-rooted to get a better understanding of things, at present i'm running [ROM][ME2][31May] FoxHound GearEngine 0.1 Stable | Themed | Smooth | Clean | Hybrid. Its way faster than stock rom and quite impressive.
I'm still trying to understand why so much memory is taken up by the OS, i understand it has something to do with TouchWhiz or something. I now need to look into running apps from the sd card if this possible, I know its not with standard rom and un-rooted device.
I actually got both S4 and HTC One as I have two contracts with t-mobile ready for upgrade, I have since sent the HTC One back to have it replaced with another S4 as the wife also prefers the S4 over the HTC One, not to say its not a good phone as its amazing, the main selling point for me was the ability to upgrade memory with SD Card.
Hopefully I can get back into this again and maybe start creating roms again, i used to create them for the older HTC windows phones, mainly TYTNII and touch.
HI im very new to rooting and decided i wanted to try it because i wanted to get something close to stock android on my phone since im not the biggest fan of lg's skin and i love stock android. I rooted got a custom recovery installed and everything was going fine. than i was having problems getting any rom to actually instal. I was looking it up online and saw a couple threads saying to update the version of my recovery. So i did that and now i cant get into recovery it just sits at a black screen. Once its there i can restart the phone and get back to the normal phone but i want to get recovery back so i can continue trying to get a new ROM. Please help :crying::crying::crying::crying::crying::crying:
Hello everyone! I'm brand new to the forums so if I am breaking any rule or regulation, just give me a heads up. So, some basic information about my predicament.
- own a Samsung Galaxy Note 3 from Verizon.
- I use t-mobile network. Works great with no problems.
- phone was successfully rooted via towel root.
I was looking to get cynagenmod on the phone so I started looking up guides and such. Only thing I wasn't aware of was that carrier branded versions can't have their recovery flashed. That said, I used flashify and the clockwork apk. The app did its job, killed the stock recovery, but couldn't load the new one. Now the phone says error, no recovery when trying to access it during boot.
It should be said that the phone still boots and works normally but I really want to get the recovery working so I can at least try again the right way to get cynagenmod working.
My question is, is it possible to get my hands on the stock recovery for my phone and just flash it back to how it was? Basically, how do I fix this problem I put myself in. Of course, I didn't make backups. During the whole process, I figured "if I follow this tutorial word for word, why bother with backups?" look how wrong I was
Any help would be sincerely appreciated. I'm posting this from my replacement phone, not my note 3.
Hello there,
I am having a little bit of an issue with a new Galaxy Note 4 that i got for my wife. We both bought our devices yesterday, mine from Three, and hers from EE (we are in the UK), both SM-N910F, so i proceeded to root my device and it worked all great. So earlier today i started the exact same procedure, unfortunately, my wifes Note 4 got stuck in a Recovery Boot Loop, and i genuinely don't understand what is happening.
As for the rooting method, i went with the [SM-N910*] CF-Auto-Root and choose the right .tar file, or else it wouldn't of had worked on the first device.
I have read quite a few posts, saw a few videos on youtube, but it far beyond me. I have seen a few people mention that i need to download the German (?) version of the Stock firmware, and then flash it. I seem to have found a link for it on SamMobile but it's gonna take 5 hours to finish, and i don't understand why i would download the German Stock firmware, is that the correct one for her device ?
At this point, is there any way around it ? Why did my device which is the same work perfectly, but not hers ?
I would appreciate any and all help, if you could make it quite detailed for me i would appreciate it even more.
Thank you!
Hi @Vaskie!
Can you enter in download mode?
Hello there @_mone, the following has happened since i posted:
Went ahead and flashed the following: N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.tar and it made the device reach the home screen, from there i attempted to root using the same method which worked, but it ended installing a few extra applications, which i don't understand how. I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
On the other hand, most things seem to be working perfect, but i am having some issues with the front camera. I have two Note 4s, both bought yesterday from the same place, but one was flashed with the Stock rom (N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.ta r) due to being stuck in a boot loop. The front camera seems to be massively over exposed compared to the other Note 4, not just a little bit either, making it almost unusable.
Would anyone be able to help ?
Vaskie said:
I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
Click to expand...
Click to collapse
That's because you "dirty" flashed a new ROM on top of the old one.. it was like an "update".
What I suggest you (because you already rooted your phone and your knox is 0x1) is to flash TeamWin Recovery Project from ODIN and then flash a TW ROM from the Galaxy Note 4 Android Development (Snapdragon) page
To do so download "twrp-2.8.7.0-trltexx.img.tar" from here, put your phone in download mode, connect it to the pc via usb, from the pc launch odin, let it recognize your phone, add the downloaded .img.tar file on the pda button, click on the "start" button and let it flash the recovery.
Now download a TW ROM like _alexndr's DevBase from here and this modem and this bootloader.
Then put the downloaded ROM (N910FXXU1POF2_DevBase_alexndr.zip) in your external SDcard. Reboot your phone in recovery mode. From TWRP go Wipe/AdwancedWipe/ and tick DalickCache, System, Data, Internal Storage, Cache and "Swipe to Wipe". After go back to the first page, hit "Install" search "N910FXXU1POF2_DevBase_alexndr.zip" in "/external_sd" and install it. Wipe Dalvick and Cache again and reboot into download mode. Again connect your phone to the PC and launch ODIN now put the downloaded modem "CP_N910FXXU1POF1.tar.md5" in the CP button and the bootloader "BL_N910FXXU1POF2.tar.md5" in the BL button and click on the "start".
Once it is done switch off and on your phone and start again with the latest samsung rom for N910F already with root, busy box and all the fixes by _alexndr
And let us know if you still have problems.
Thank you very, very much for the very well detailed reply @_mone
I will attempt to go ahead with your explanation tomorrow. Would that somehow fix the camera, and i guess the other question is.. is the front camera issue that i explained myself above to do with me "dirty flashing" ?
Is there anything inherently wrong with "dirty flashing" ?
Thank you yet again!
Nothing wrong with dirty flashing.. but sometimes doing so you can create conflicts between old and new rom or leaving "bugs" from the old to the new generating problems in your new os that may wont be there if you performed a clean install. :good: