Hi Someone can suggest how can I solve following problem?
P5220 stuck at "Samsung Galaxy Tab 3" after I done following steps or (my itchy hand).
1. I flash TWP with Odin, PDA, choose file, uncheck auto-reboot, looks fine. I can enter recovery mode.
2. Then I flash root.zip to try whether I can get root, because I need to install font which is not supported by official rom.
3 Then after reboot I still can get in OS and seems like superuser working. Installed font installer and installed my font.
4. After I reboot to refresh my fonts, the tablet is stuck on samsung logo.(I tried 3-4 time, still cannot)
5.So I decide to install custom rom, I download BinDroid_ONE_P5210_V2.0.0.zip and flash with TWM(done some wipe that suggested).
6. This time stuck on the title( samsung galaxy tab 3) . Also tried version 2.0.1 and reboot,also same.
7. I tried to wipe again and re-installed different ROM version , still the same.
8. Some more try to install CWM again , wipe data, cache and Davik cache, install BinDroid_ONE_P5210_V2.0.1 ROM
Same result.
9. Install ROM again without wipe, reboot, same result.
10. Install bindroid_kernel_p5210_v0.0.1 , Kernal . Same thing.
11. Wipe Cache and Devik cache and reboot also stuck at text title.
(Or can I go back to Official status?) just ask I am very new with Samsung. I am HTC lover, I root and installed
so many HTC models, no problem at all, but now my first Samsung make me sad. :'(
If anyone understand and how to solve it, please guide me.
I am not very demanding but I wish someone know well and help me.
I will give well credit or give a lot drinks. :highfive:
(Forgive my bad Eng and exciting questions)
nyanlone said:
Hi Someone can suggest how can I solve following problem?
P5220 stuck at "Samsung Galaxy Tab 3" after I done following steps or (my itchy hand).
1. I flash TWP with Odin, PDA, choose file, uncheck auto-reboot, looks fine. I can enter recovery mode.
2. Then I flash root.zip to try whether I can get root, because I need to install font which is not supported by official rom.
3 Then after reboot I still can get in OS and seems like superuser working. Installed font installer and installed my font.
4. After I reboot to refresh my fonts, the tablet is stuck on samsung logo.(I tried 3-4 time, still cannot)
5.So I decide to install custom rom, I download BinDroid_ONE_P5210_V2.0.0.zip and flash with TWM(done some wipe that suggested).
6. This time stuck on the title( samsung galaxy tab 3) . Also tried version 2.0.1 and reboot,also same.
7. I tried to wipe again and re-installed different ROM version , still the same.
8. Some more try to install CWM again , wipe data, cache and Davik cache, install BinDroid_ONE_P5210_V2.0.1 ROM
Same result.
9. Install ROM again without wipe, reboot, same result.
10. Install bindroid_kernel_p5210_v0.0.1 , Kernal . Same thing.
11. Wipe Cache and Devik cache and reboot also stuck at text title.
(Or can I go back to Official status?) just ask I am very new with Samsung. I am HTC lover, I root and installed
so many HTC models, no problem at all, but now my first Samsung make me sad. :'(
If anyone understand and how to solve it, please guide me.
I am not very demanding but I wish someone know well and help me.
I will give well credit or give a lot drinks. :highfive:
(Forgive my bad Eng and exciting questions)
Click to expand...
Click to collapse
Problemo solved ,
>>http://forum.xda-developers.com/showthread.php?t=2473652
Related
Hi there,
I'm new so I'm sorry if there is already a thread like this.
I'm having problems installing CM9 on my Gio. I'm following the instructions by Maclaw. Here are the steps I do:
1. install via Recovery Menu the px-cwm-v2.zip (ClockworkMod I think)
2. reboot
3. install the CM9 main zip (cm-gio-ota-eng.13052012.zip)
4. factory reset
5. reboot
6. Apply patch v2 and v3 (patch-cm9-v2.zip & patch-cm9-v3.zip)
7. reboot
I thought that was it but all i see now on the screen is "ANDROID". I tried rebooting several times but nothing works for me.
I tried the whole process now for 3 times but everytime the same failure. I have now Android 2.3.3 with root rights but I want to try out CM9.
I don't know what I'm doing wrong so pls help me if you know where the problem is.
Thanks a lot
-Hibuja
xXHibujaXx said:
Hi there,
I'm new so I'm sorry if there is already a thread like this.
I'm having problems installing CM9 on my Gio. I'm following the instructions by Maclaw. Here are the steps I do:
1. install via Recovery Menu the px-cwm-v2.zip (ClockworkMod I think)
2. reboot
3. install the CM9 main zip (cm-gio-ota-eng.13052012.zip)
4. factory reset
5. reboot
6. Apply patch v2 and v3 (patch-cm9-v2.zip & patch-cm9-v3.zip)
7. reboot
I thought that was it but all i see now on the screen is "ANDROID". I tried rebooting several times but nothing works for me.
I tried the whole process now for 3 times but everytime the same failure. I have now Android 2.3.3 with root rights but I want to try out CM9.
I don't know what I'm doing wrong so pls help me if you know where the problem is.
Thanks a lot
-Hibuja
Click to expand...
Click to collapse
Don't apply patch, they are very outdated and should be removed.
iok1 said:
Don't apply patch, they are very outdated and should be removed.
Click to expand...
Click to collapse
THANK YOU!!! Now it's working!
LOL
I was having the same problem even a half year ago....
Lolzz
Hello guys,
I tried to flash a new rom on my wildfire but every rom i tried got "bootlooped".
Thats what i did:
(followed this guide: http://forum.xda-developers.com/showthread.php?p=12782364)
1. Verified i had hboot 1.01.0001.
2. Installed and deleted htc sync
3. Hacked hboot drivers
4. Usb debugging is on
5. Used revolutionary, when asked - installed cwm recovery.
6. Booted to bootloader. It now says "hboot 6.01.1002" (after installing revolutionary of course).
7. Got into recovery (cwm v4.0.1.4).
8. Cleaned data, cache and dalvik.
9. Install zip from sd - and then i tried mini cm9, miui v4, cyanogenmod 9 (each one after cleaning as stated in 8)
10. Reboot
11. Crap. Stuck in bootloop. Every time.
I have no idea what to do... Lucky me i backed up using cwm, so i can still restore with no problem. But cant install any new rom!
If you have any idea - i would be glad to try... I'm quite desperate.
Thanks!
USe the guide in my sig
HELP
Liorgi said:
Hello guys,
I tried to flash a new rom on my wildfire but every rom i tried got "bootlooped".
Thats what i did:
(followed this guide: http://forum.xda-developers.com/showthread.php?p=12782364)
1. Verified i had hboot 1.01.0001.
2. Installed and deleted htc sync
3. Hacked hboot drivers
4. Usb debugging is on
5. Used revolutionary, when asked - installed cwm recovery.
6. Booted to bootloader. It now says "hboot 6.01.1002" (after installing revolutionary of course).
7. Got into recovery (cwm v4.0.1.4).
8. Cleaned data, cache and dalvik.
9. Install zip from sd - and then i tried mini cm9, miui v4, cyanogenmod 9 (each one after cleaning as stated in 8)
10. Reboot
11. Crap. Stuck in bootloop. Every time.
I have no idea what to do... Lucky me i backed up using cwm, so i can still restore with no problem. But cant install any new rom!
If you have any idea - i would be glad to try... I'm quite desperate.
Thanks!
Click to expand...
Click to collapse
Hi, could you help me with the backup files. A friend brought his phone to me for upgrade. Unfortunately I didn't do a backup, and now CWM cannot flash any of the ROMS. I need help badly.
Thanks.
I have a realy serious problem with flashing lpx13d flashable pack. each time I try to flash it via twrp recpvery says that everything was flashed succesfully but then when I try to reboot the system it stops on google logo and after a reboot comes back to recovery mode. Do you have any ideas about wht am I doing wrong? Thank you in advance
First things first, the easy things.
Is it a clean install, or are you installing on top of a different version.
Did you clear the caches, if you didn't that's the first thing to try.
I have actually installed custom ROMs many times. and I have solved the problem. I havven't thought that instalation of the multirom is neccesary. When I installed it - everything works fine so as I can see - instalation fromthe stock KTU84 kernel was the issue.
To moderator- please, close the thread.
Hey guys. I'm going crazy for days. I tried to root my T805 and something went wrong. After rooting and after the reboot there appeared many many error massages like "Google service stopped" or "android..... stopped". You can't really skip them because they are coming over and over and over. After some time it rebootes by itself and voila same issue... makes it unuseable. So right here nothing special I thought. Just flash the stock rom over it with odin and you will be fine. But whatever kind of rom or firmware I tried to flash I'm getting the same issues. Plus after every flash I got stuck at the Samsung logo incl. some vibrations in intervals. So when I get stucked (over 20 min) I have to force shutdown it and yeah it starts and hello error messages.
I rooted and flashed so many smartphones and tabs and I've never seen a problem like that. Please oh please try to help me. Probably I'll donate you some dollars for the perfect hint or solution, I'm really desperate.
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
mihailrusia said:
Did you try wipe system before flash ROM?
Can you try install Lineage OS or wipe system and flash stock ROM
Click to expand...
Click to collapse
Yes. Every time I'm flashing I wipe befor and after it. And after I tried LineageOS the same happend with the error messages . But now after flashed stock ROM again it seems now that I'm totaly stuck at the Samsung logo. Even when I try to reboot and reflash I get stucked at the logo with these vibrations.
Thanks for your reply.
Ok now I'm not stucked at the logo but get the error messages again...
Are you flashing the last firmware and system and data are on ext4?
mihailrusia said:
Are you flashing the last firmware and system and data are on ext4?
Click to expand...
Click to collapse
Yes I'm flashing the latest. About the filesystem... I'm not sure. Where can I look at the filesystem? In Recovery? What I reached in the last houres: I flashed LineageOS again WITHOUT Opengapps. And boom ist startet pretty well but yea now I have no google playstore and such stuff. Now I'll try to flash the opengapps stock over the ROM using the TWPR.
Edit: I looked at the filesystem, it's ext4
You can view the partitions with DiskInfo
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=es
Install the pico gapps
So now I flashed opengapps stock again and I'm now stucked again in at the Samsung logo. I have to hard reboot now and yeah I think there will be the error messages. But I'll try the Pico version of opengapps like you said.
Edit: I didn't have to hard reboot it. It booted by itself after some minutes but yea with the errors. After some errors it shutsdown and reboot... and so on.
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
mihailrusia said:
If pico Gapps doesn't work install old pico Gapps. You can try with ironrom 3.2 if this doesn't work
Click to expand...
Click to collapse
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Metero said:
Pico doesn't work ... same issues. So now I'll try to flash the PhoeniX ROM v3 which is based on 5.0.2
Click to expand...
Click to collapse
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
Thanks for searching. I'll try this next. (Give me some minutes )
mihailrusia said:
I found a post
https://forum.xda-developers.com/go...fix-install-google-gapps-stock-build-t3226205
Click to expand...
Click to collapse
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Metero said:
unfortunately it didn't work ... as long I don't flash the gapps everything is fine. I have no idea what to try next. Maybe there is a way with the ADB to do things like re-partitioning or i don't know.
Click to expand...
Click to collapse
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
thejase said:
Remember to grab the right gapps that are arm but not 64 bit. Try to start fresh with any rom your're installing. Boot up tablet first before installing gapps. then reboot into recovery ( from within android hold home + vol up + vol down + power. right when tab goes black, switch finger to vol up while still holding all the other buttons. Hold until you see twrp logo). Now install your pico gapps, then reboot.
I think the important thing is to boot the system first before installing gapps. I have had to do this multiple times and have had the same issues with gapps that you're describing. Good luck and let us know how it goes.
Click to expand...
Click to collapse
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Metero said:
Thanks for your reply. I flashed every time "ARM" so not "ARM64". And the problem is that the error messages not only apply when I'm trying to flash the opengapps (when installing a ROM). The error also applys when I'm flashing the STOCK firmware with stock BL and so on... And the only ROM I was able to install was LineageOS. I also tried IronRom v3.2 but when the aroma installer finished and it rebooted there only popped up the normal Galaxy Tab S - screen... no bootloading so no Samsung - Logo ... no nothing... (and I'm really sure that I am not the problem. like I said I flashed so many ROMs and repaired so many soft bricks and I know how to follow installation instructions and that I have to wipe and to flash a new bootloader (for IronRom) etc. ... Ok so what I now try is to flash the original firmware (to reset bootloader and kernel) and then I'll try to flash the TWPR and then I do a full wipe and install LineageOS and reboot BEFORE I flash the Gapps (like you said). But honestly I don't think this will change anything.
Greets from germany
Click to expand...
Click to collapse
Try using https://forum.xda-developers.com/ga...olkit-unified-android-toolkit-galaxy-t2998205
This should take you back to stock as if the tab was new. It has many many features, including rooting the tablet for you. It runs in windows ( hopefully you have). Habben Sie einen guten Tag! (is this right? I love German but I am just learning)
It's been three years since i changed phones and I naively thought that things had gotten easier.
But nope. Still a mess of stiching together various incomplete "guides" from around the web only
to end up with a phone stuck in a boot-loop.
It's a Galaxy S9. Using Odin I've been able to install TWRP 3.3.1-0.
With that I tried installing both Carbon ROM as well as Havoc OS each followed by Open Gapps 8.
In some of the "guides" there was mentions of no-verity, so I've tried adding that in various steps.
Still, the only thing that works reliably is power+bixby+up to enter twrp. It's the only way I've found
to power down the phone.
Very grateful for any suggestion.
I've thought about installing the ROM using Odin, but I'm afraid that I would lose twrp.
From TWRP boot into download mode and use Odin to flash stock.
Or download soldier ROM and flash that in TWRP. It's based on stock ROM.
basicreece said:
From TWRP boot into download mode and use Odin to flash stock.
Or download soldier ROM and flash that in TWRP. It's based on stock ROM.
Click to expand...
Click to collapse
Thanks for taking the time to reply - I appreciate it!
Just to be suuuper clear: Should I flash the ROM the same way as I did twrp? Option AP and F. Reset time?
And why stock ROM? That's where I came from. Ultimately I want a custom ROM (preferably Carbon or Havoc).
Is this a step towards that?
Sam Sunk said:
Thanks for taking the time to reply - I appreciate it!
Just to be suuuper clear: Should I flash the ROM the same way as I did twrp? Option AP and F. Reset time?
And why stock ROM? That's where I came from. Ultimately I want a custom ROM (preferably Carbon or Havoc).
Is this a step towards that?
Click to expand...
Click to collapse
Flashing stock will return your phone to the way it was when you bought it, having to flash TWRP etc all over again
When flashing stock you flash all 4 sections together and do not change any settings in Odin
CSC = Reset phone
HOME CSC = Do not reset
Only use one or the other
You will need to use CSC if you have TWRP / Custom installed
If you are wanting a custom ROM flashed from TWRP you should wait for someone else who knows why it won't flash to help you as I have just kept stock on my S9 so don't know what's wrong
You do know you flash the custom ROM zip using TWRP right? Copying it to your SD card then choosing it from TWRP itself, not using Odin
*Detection* said:
You do know you flash the custom ROM zip using TWRP right? Copying it to your SD card then choosing it from TWRP itself, not using Odin
Click to expand...
Click to collapse
That's exactly what I did. I used Odin to install twrp and then tried to install the custom ROM with twrp. That's when the wheels came off and the phone got stuck booting.
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Sam Sunk said:
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Click to expand...
Click to collapse
Then you should follow the guides on this XDA S9 forum instead, then you know they are for the S9
Sam Sunk said:
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Click to expand...
Click to collapse
you still bricked?
In TWRP did the internal storage maybe say 0mb? Tat happens when you dont abort the factory reset after OEM unlock. If it is that than just go to advanced wipe, pormat your data to fat2 and then back to fat4
Hey there, I had the exact same problem over the past 2 days - so I feel your frustration.
I have a 9604f (galaxy s9) , and there are different types so you may have to see if yours is different. I also used ressurrection remix OS. Short version is:
1. Get resurrection remix (final version for starlte)
2. Get gapps (for 8.1 arm64)
3. Get magisk
The above 3 are all on the post for the official resurrection remix on this site with the header -[ROM] [OFFICIAL] [6/01/18] ResurrectionRemix 6.0 for S9/S9+ (Exynos)
4. Download the BRE5 vendor. I used a link that went to a mega.nz site and it worked. So I'm sure you'll be able to find one. I can't post links cause this is my first post.
5. Boot into twrp
6. Format data in wipe section of twrp
7. Wipe dalvik, cache, data, system.
8. Install in this order -do not reboot or wipe anything. Just install.
(I) BRE5 vendor
(II) resurrection remix ROM
(III) gapps
9. DONT WIPE cache, and reboot into the OS
10. If you want root -just go back into twrp once you have set up google, apps etc. And then install the magisk zip.
update
Not bricked any more.
The advice from @basicreece to install soldier worked. I made a second attempt to install Carbon afterwards but that resulted again in a twrp-only device. Now I'm back on soldier.
Perhaps I'll give @Madsikhey's instructions a go later.
To show my gratitude for all the help in times of darkness I'd like to give back and I'll let @basicreece decide:
1. Donation to XDA
2. Donation to EFF
3. A beer/coffee for yourself (PayPal)
Answer me in a PM.
Madsikhey said:
Hey there, I had the exact same problem over the past 2 days - so I feel your frustration.
I have a 9604f (galaxy s9) , and there are different types so you may have to see if yours is different. I also used ressurrection remix OS. Short version is:
1. Get resurrection remix (final version for starlte)
2. Get gapps (for 8.1 arm64)
3. Get magisk
The above 3 are all on the post for the official resurrection remix on this site with the header -[ROM] [OFFICIAL] [6/01/18] ResurrectionRemix 6.0 for S9/S9+ (Exynos)
4. Download the BRE5 vendor. I used a link that went to a mega.nz site and it worked. So I'm sure you'll be able to find one. I can't post links cause this is my first post.
5. Boot into twrp
6. Format data in wipe section of twrp
7. Wipe dalvik, cache, data, system.
8. Install in this order -do not reboot or wipe anything. Just install.
(I) BRE5 vendor
(II) resurrection remix ROM
(III) gapps
9. DONT WIPE cache, and reboot into the OS
10. If you want root -just go back into twrp once you have set up google, apps etc. And then install the magisk zip.
Click to expand...
Click to collapse
Hello, Iám also having the same problem. I got all the files needed but the BRE5 Vendor file, could anyone link it plz? Iám using a G960F (S9).
Haxomen said:
In TWRP did the internal storage maybe say 0mb? Tat happens when you dont abort the factory reset after OEM unlock. If it is that than just go to advanced wipe, pormat your data to fat2 and then back to fat4
Click to expand...
Click to collapse
Thanks :good::good::good:
I have somewhat same problem. Rooted my S9 original OS and it worked fine. After power off the phone is in bootloop and the only way to shut the phone off is to boot in the twrp and reboot-->shut off.
And the only way to get to the twrp is power+volume up+bixby button combination.
I made a thread about my problem, it's here
Problems with rooting Galaxy S9 (Android 10 Exynos SM-G960F)
Hi, this is My first post here, so be gentle. My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine. Yesterday I decided to root it (there are a few features that need root and I...
forum.xda-developers.com
Now I'm stuck and I need a help to proceed. What i should do to get the phone open again? Would it be a good idea to flash lineageOS now, or is there a way to reset the phone back to original?
I can open trwp or download mode, but cannot boot to the OS.