Hi,
I rooted my tab yesterday and downloaded rom manager. I then dowloaded the synergy rom and installed it using the rom manager. After I installed it I tried to reboot my device and its stuck at the reboot screen with the samsung galaxy tab 2 10.1 logo. I can go back to the rom manager thing where you can reboot your device and install zips from sd card etc.But if I try t reboot it it goes back to the same logo.
PLEASE HELP! Thank You!
This is the wrong forum for your thread, you'd do better asking in your device-specific Q&A (although I'm sure a mod will move/delete this thread fairly soon).
Nigeldg said:
This is the wrong forum for your thread, you'd do better asking in your device-specific Q&A (although I'm sure a mod will move/delete this thread fairly soon).
Click to expand...
Click to collapse
And you sir are correct.
Thread closed.
Related
Hol friends, podran to help I have this problem, have installed the TWRP V2.1.8 And I wanted to install a rom 4.2.1, forget to become I a nandroid and erase the whole system and it did not want to install it rom for that the recovery is very obsolete now not that to do .. my alone telephone starts in TWRP and I do not find a rom that is compatible anybody it can assign a compatible rom to me help me please I am nervous...
mataflakitas said:
Hol friends, podran to help I have this problem, have installed the TWRP V2.1.8 And I wanted to install a rom 4.2.1, forget to become I a nandroid and erase the whole system and it did not want to install it rom for that the recovery is very obsolete now not that to do .. my alone telephone starts in TWRP and I do not find a rom that is compatible anybody it can assign a compatible rom to me help me please I am nervous...
Click to expand...
Click to collapse
You can ODIN a stock ROM back to something that has CWM like GA10 (jellybean). This will get you back where you need to be. Just remember to wipe everything. Remember jellybean modems do not work with JB 4.2...good luck!
link please friend
Easy Peasy....
http://forum.xda-developers.com/showthread.php?t=2103000
thanks my friend
work ,work im very happy ...thanks third son
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
HELP - my ATT Galaxy S3 is bricked after flashing Liquidsmooth 2.8.
I mistakenly downloaded from the link in the ATT Galaxy Note forum, but apparently posting there to ask for help left some Note owners severely POed. I had downloaded V4.2.2 from the same Note thread and flashed it with no problem.
I see the same download link in this thread in the Galaxy S3 developers forum. For some reason, this thread was closed on July 1.
Before flashing 2.8, I wiped the data and cache, then flashed the ROM and it installed with no problem. But on reboot it didn't restart. Battery has been pulled several times, Vol+ - home - power does nothing at all.
I've tried the instructions here, but ODIN doesn't recognize the phone when I plug it in.
I know there's dozens of brick-related threads -- most of them seem to have the same answers in the midst of a lot of BS.
I've installed quite a few ROMs on my phones, and have never had this problem come up before.
Any help getting my phone back would be appreciated.
I have the same issues as others in several other brick threads. Battery out and phone plugged into desktop, the red LED comes on and the desktop dings but the phone doesn't show as a device.
I've tried all of the suggestions in this thread, even though it's for a Captivate. No joy with any.
I tried installing the driver downloaded from Samsung, but got the attached error. I got the same error when I plugged the phone in the first time after flashing 2.8.
Wondering if I'm going to have to send the phone to Mobile Tech Videos for a JTAG job??
Again, any advice would be appreciated. Hopefully, I don't PO any S3 owners.
You bricked it. Mail it out for jtag. Next time, only flash software intended for your device.
Don't
Flash
Roms
For
Different
Devices
.
mrhaley30705 said:
You bricked it. Mail it out for jtag. Next time, only flash software intended for your device.
Click to expand...
Click to collapse
Yeah, I was afraid of that.
I can assume the S3 Liquidsmooth thread was closed BECAUSE it offered a ROM (2.8) that doesn't work on the S3, even with the video with v2.2 on the S3 posted right at the top of the OP.
Liquidsmooth seems to be at the root cause of much grief for our phones. Maybe the good dev can pull it off the forum until these issues are resolved.
Sent from my SAMSUNG-SGH-I747 using xda premium
jamesc760 said:
Liquidsmooth seems to be at the root cause of much grief for our phones. Maybe the good dev can pull it off the forum until these issues are resolved.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Doubt will get reimbursed for all the money heading to MobileTechVideo
Icersman said:
Doubt will get reimbursed for all the money heading to MobileTechVideo
Click to expand...
Click to collapse
Of course you're not going to be reimbursed anything... NO ONE BUT YOU MADE YOU FLASH THE WRONG ROM. Why should anyone else pay for it...
Flashing any Rom is done at your own risk.
studacris said:
Of course you're not going to be reimbursed anything... NO ONE BUT YOU MADE YOU FLASH THE WRONG ROM. Why should anyone else pay for it...
Flashing any Rom is done at your own risk.
Click to expand...
Click to collapse
Lighten up Francis. I was being sarcastic.
I'm fully aware of the risk. I'm also fully aware that the v2.2 ROM in the OP for Liquidsmooth and the updated 2.8 ROM that was added to the OP supposedly worked in the S3. Hence my suspicion that the thread was closed -- BECAUSE 2.8 BRICKS S3s
I am sorry you flashed a rom that did not belong on your device. I really am sorry.
but your posting got me to thinking why I was unable to install v2.8. after using the search bar I found a similar issue. followed the threads and was able to update the bootloaders and have flashed successfully flashed liquid smooth v2.8. I was surprised to have found it since you claim the post was taken down. it must have just been moved. It did not brick my device by the way.
I have enjoyed the work the liquid smooth team has turned out since I got my s3 and will continue to support them.
aircooledbusses said:
I am sorry you flashed a rom that did not belong on your device. I really am sorry.
but your posting got me to thinking why I was unable to install v2.8. after using the search bar I found a similar issue. followed the threads and was able to update the bootloaders and have flashed successfully flashed liquid smooth v2.8. I was surprised to have found it since you claim the post was taken down. it must have just been moved. It did not brick my device by the way.
I have enjoyed the work the liquid smooth team has turned out since I got my s3 and will continue to support them.
Click to expand...
Click to collapse
I enjoyed v2.2 after flashing it a month or so ago. Here is the thread that I downloaded 2.2 from. The updated link to Goo in the OP sends you to a page that contains the download links for 2.7 and 2.8.
The final post by Forum Moderator Jayharper08 posted on 7/1 says simply "Closed per Mike's request."
I had downloaded 2.8 prior to the 1st, so I assumed that all was OK. I don't see anything anywhere about the need to update the bootloaders, so again I assumed that clearing data and cache before flashing would be sufficient.
I don't blame Mike or the LS team. I would like to continue using the ROM once I get my "brick" back from MobileVidTech. To that end, which thread did you download 2.8 from?
http://forum.xda-developers.com/showthread.php?t=2346973
aircooledbusses said:
http://forum.xda-developers.com/showthread.php?t=2346973
Click to expand...
Click to collapse
Thanks. I searched the S3 Dev forum for "liquid smooth 2.8" and the only reply was to my linked thread.
So, when my phone comes back I'll flash from this thread.
Sent from my A500 using xda app-developers app
OK, now that I've had the chance to look at aircool's reply on my desktop, I'm confoozed.
I'm not a noob, but can someone 'esplain (without trolling) why there are two forums:
AT&T Galaxy S III Original Android Development
Original development for the AT&T Samsung Galaxy S III
and
AT&T Galaxy S III Android Development
Android development for the AT&T Samsung Galaxy S III
In my less than expert opinion, they seem redundant.
Original development is for source built roms/kernel with the work done originally by the op.
Development is another project that has stemmed from those works (kangs)
Or roms/kernels based on a modified TouchWiz.
studacris said:
Original development is for source built roms/kernel with the work done originally by the op.
Development is another project that has stemmed from those works (kangs)
Or roms/kernels based on a modified TouchWiz.
Click to expand...
Click to collapse
Thanks for clarifying that -- I think I get it.
And I apologize for spouting off earlier in the thread. I was a little cranky about bricking the phone. Of course, at my age I'm usually cranky!
Porting is a pain in the buns.
So let me inform all of you on my toubles with the Samsung Galaxy s4 (T-mobile variant SGH-M919).
I had tried to install the latest CyanogenMod v10.1.3.1 ROM, (which was indeed successful, and infact, I love how
sexy and smooth the UI is), but I didn't install Gapps when installing the ROM, if that makes any difference.
So later, I realized how much I needed Google Play store, and I installed an off-store apk of ROM manager and
Installed Gapps. After flashing it, I set up everything on my Google account.
But here is where the bun-pain starts. Google play works great, but literally, no other Google apps will work
(IE: Google search, crashes every time).
If you have experienced the same issue and have sought out a way to fix this issue/ you know a possible way to fix
this, please don't hesitate to help, as that would be greatly appriciated!
You simply must flash GAPPs. Simple as that.
But...
dynospectrum said:
You simply must flash GAPPs. Simple as that.
Click to expand...
Click to collapse
But I did flash Gapps. That's the reason for posting.. So after flashing CyanogenMod and Gapps, on my cgm ROM, Google search crashes every time as well as the other apps don't work that were installed with gapps. :/
But...
dynospectrum said:
You simply must flash GAPPs. Simple as that.
Click to expand...
Click to collapse
But I did flash Gapps.zip with CWM (After installing CyanogenMod). Google play store works just fine, but google search crashes with the message "Unfortunately, Google Search has stopped."... :/ Any ideas?
androidiphonehacker said:
But I did flash Gapps.zip with CWM (After installing CyanogenMod). Google play store works just fine, but google search crashes with the message "Unfortunately, Google Search has stopped."... :/ Any ideas?
Click to expand...
Click to collapse
Use 10.1.3
I just flashed 10.1.3.1 without wiping from 10.1.3, and it's wank.
androidiphonehacker said:
But I did flash Gapps. That's the reason for posting.. So after flashing CyanogenMod and Gapps, on my cgm ROM, Google search crashes every time as well as the other apps don't work that were installed with gapps. :/
Click to expand...
Click to collapse
You must flash gapps right after flashing CM. Before first boot.
Update...
dynospectrum said:
You must flash gapps right after flashing CM. Before first boot.
Click to expand...
Click to collapse
Update: Okay, Google search is working just fine Turns out, all I needed to do was just flash the latest gapps, then reinstall Google search :good:
Now I just have to worry about fixing the su binary, it doesn't want to execute. :silly:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Sorry kennyglass ;____;
kennyglass123 said:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Sorry for posting in the wrong place! Whoops! Newbie to the forums here /_\
Now I'm going to go eat a banana in my depression. *Sad face meme*
androidiphonehacker said:
Now I just have to worry about fixing the su binary, it doesn't want to execute. :silly:
Click to expand...
Click to collapse
Did you enable Root in Developer Options?
Yes :/
baseballfanz said:
Did you enable Root in Developer Options?
Click to expand...
Click to collapse
Yes I did enable root rights in dev options. I'm just so lost... I've spent hours googling for answers,
And so far, nothing has helped
The only known thing I know to do, is to execute the /system/bin/su file.. I just have to figure out how. Honestly, I'm not sure. This whole thing is a long, LONG rabbit trail, just to get freaking root rights on cm10.
I may just end up flashing an AOSP ROM (one close to cm10) that actually HAS root.
Okay, I found a nice looking AOSP Rom- Eclipse ROM 5.1 ...
Question! -Does this ROM Development have any flash zips for T-Mobile S4? (Sgh-m919)
androidiphonehacker said:
Okay, I found a nice looking AOSP Rom- Eclipse ROM 5.1 ...
Question! -Does this ROM Development have any flash zips for T-Mobile S4? (Sgh-m919)
Click to expand...
Click to collapse
Always provide links to exactly what you're asking.
Also, make sure you flash the appropriate Gapps.
There's some for 4.2 and some for 4.3.
lol All releases of CM have root. You need to do a clean install of cm and flash gapps before first boot. You more than likely also flashed the wrong gapps. Consult the link below.
http://wiki.cyanogenmod.org/w/Gapps
Guys,
I tired to flash a custom rom Jelly Dream Z1 with a ICS Kernel, it installed OK. But now I am not able to get out of the CWM 6.0.0.28 recovery loop no matter what I try. Please can anyone help me regarding this?
Very wrong section to post. Questions go to Q&A, showing off your work goes in Development section. Read the section description before you post.
Which kernel did you use?
Someguyfromhell said:
Very wrong section to post. Questions go to Q&A, showing off your work goes in Development section. Read the section description before you post.
Which kernel did you use?
Click to expand...
Click to collapse
did you flash arc S patch after you install the rom?
Moved here as this does not belong in the Dev Section, Thanks.
I tried to flash JellyBam ROM and when I installed it, I got the Downloading screen and said could not boot normally, has anyone tried to flash this rom?
I think you should post this in the JellyBam thread specifically & not the ROM development threads. Just a guess out suggestion for the best answers to your problem.
TheGame1083 said:
I tried to flash JellyBam ROM and when I installed it, I got the Downloading screen and said could not boot normally, has anyone tried to flash this rom?
Click to expand...
Click to collapse
Wrong section.
TWEAKED 1.0 NOTE 3
Yea if a mod sees this he will shut it down. As jellybam has been banned from xda, which is completely dumb but nonetheless true. Awesome rom by the way.
Reported.
MODERATOR EDIT - LINK REMOVED go here for further instructions. in the future, learn forum rules before posting. have a nice day :victory:
As already stated, Jellybam has been banned from XDA, and this is not a development related thread. Thread closed.