Related
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
First thing i would recommend is : uninstall rom manager. It causes more problems. If you did a search on these forums you would find loads more tales of woe re rom manager.
Second thing is: have look through the dev section, at the instructions for installing clockwork recovery. Then look for the appropriate rom for your device.
But whatever you do, uninstall rom manager
Sent from my thingymajig
Isn't ROM manager ClockworkMod?
I searched Clockworkmod on the market and when installed the icon says ROM Manager though...
o2sys said:
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
Click to expand...
Click to collapse
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
TheATHEiST said:
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
Click to expand...
Click to collapse
i did following the tutorials, its how I went that far to begin with. Sorry for being a newb and maybe not fully understanding it thats why I am asking for help, not to spoon feed me...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
o2sys said:
...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
Click to expand...
Click to collapse
Have you tried booting into CW Recovery manually and running the KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip (like the instructions say)?
Your thread header says you are using ROM Manager and trying to run the update.zip package.
ROM Manager _should_ work, but maybe stick with instructions especially if you're having issues.
Yes I have tried going into Recovery manually as I stated in my original post.
I always flashed with SGS kernel flasher as it seemed to work well.
Then I tried manually going to Recovery w/o CWM and gets stuck at boot screen as well.
I tried WITH CWM and same stuck at boot screen.
Tried wiping data through Recovery, through the UI (Settings then ect, ect) and several other combos trying to load the custom ROM.
All I am successul is at rooting, then flashing the kernel. Then no matter which step I tried if i reboot it will get stuck at the SAMSUNG boot screen.
Even if I just turn it off and then turn it back on, after the flash, it will get stuck at the boot screen.
I downloaded the kernal flash directly from the link of the first page. And if the kernal file was courrupt i don't think the flash would go successfully.
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Sorry to hear you are having problems. I am also sorry for the rudeness on this forum. Although I seldom post I read it daily. Here is what I would try;
1. The issue may be with the file name update.zip if you can, rename it to anythingyoulike.zip on you computer and then copy it to your SD card. You may even have to take the card out of your tab to do this (delete the update.zip once the file is renamed). Once the renamed file is on the SD card try to reflash.
2. Have you tried to start again using Odin? There is a good clip on you tube about this. As long as the tab at least starts to boot it is not bricked. Feel free to PM me for any additional help.
Good luck.
tigercorp said:
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Click to expand...
Click to collapse
When I use SGS to flash, it reboots and i can see in settings that it has been flashed.
If I use Heimdall, it flashes then gets stuck at the boot screen.
Would appreciate if someone could help me with my problem - I had earlier used CF-Root to root and install recovery which went off well, took a nandroid backup and then tried to flash CM9 through recovery. WIthin a few seconds it rebooted, showed the Cyanogenmod splash screen and went back into recovery - only this time it was a newer recovery (6.0.0.2) than what CF-Root had installed. I'm not able to install through zip file and for some reason I am not able to restore from nandroid as it says the md5 does not match. So as of now I am stuck in recovery.
To add to this, I realize that I messed up as the instructions said to update to a GB rom if coming from Froyo, which I did not notice. Any idea what I can do from here? If I can still run through this process can someone point me in the direction of a suitable GB ROM I can install? My end goal is to be on CM9, but right now would just be happy to get back to the stock GB ROM as well.
Flash to the stock firmware again? at SamMobile? That is what I did when my device did not boot up after installing CWM recovery and some rom.
skiddyrow said:
Would appreciate if someone could help me with my problem - I had earlier used CF-Root to root and install recovery which went off well, took a nandroid backup and then tried to flash CM9 through recovery. WIthin a few seconds it rebooted, showed the Cyanogenmod splash screen and went back into recovery - only this time it was a newer recovery (6.0.0.2) than what CF-Root had installed. I'm not able to install through zip file and for some reason I am not able to restore from nandroid as it says the md5 does not match. So as of now I am stuck in recovery.
To add to this, I realize that I messed up as the instructions said to update to a GB rom if coming from Froyo, which I did not notice. Any idea what I can do from here? If I can still run through this process can someone point me in the direction of a suitable GB ROM I can install? My end goal is to be on CM9, but right now would just be happy to get back to the stock GB ROM as well.
Click to expand...
Click to collapse
you better use the overcome stock gingerbread safe 5 (the best stock for all situations) google overcome.com and get the files, you will find also a tutorial for how to stock your tab before updating it to overcome or cm9 etc...
If I helped you, please press the thanks button
MarlX said:
Flash to the stock firmware again? at SamMobile? That is what I did when my device did not boot up after installing CWM recovery and some rom.
Click to expand...
Click to collapse
so the reflash from scratch works for you
If I helped you, please press the thanks button
Thanks sos_sifou - worked great! I think I'll stick with the Overcome GB ROM for a while as it works pretty good, and look at CM9 / 10 whenever it gets stable!
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
ragvaror said:
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
Click to expand...
Click to collapse
hey mate,
i was just caught out by this last night. all you need to do is re-flash on a stock rom with ether oden of heimdall and youre good to go. im sure there is a oden flashable rom on these forums
take it sleazy!
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
ragvaror said:
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
Click to expand...
Click to collapse
yeah, i think its becaute the cwm recovery doesnt know what to do with the update.
you need to have the stock recovery installed. dont take my word for it though.
just look up a tutorial for flashing a rom via oden. its really easy, just make sure the image you are flashing is of .tar.md5 extension.
You can get the stock rom at sammobile.com. down load the zip file then extract the .tar.md5 file out of it using 7-zip.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
how ?
ragvaror said:
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
Click to expand...
Click to collapse
i currently have the same problem as you did, how did you flash with odin if you're stuck in recovery mode ?
please help, I'm racking my brain trying to figure this out.
my sons sg i9000 was rooted with a custom rom but then started playing up, now when i've wiped it and tried put new rom on it, all it does it force crash everything that was existing on his phone, so it looks like it is not wiping the phone anymore for some reason, i've tried flashing rom by odin but still the same effect, is there anything out there that totally wipes the phone for sure and then will allow me to put phone back to stock and then reroot.
many thanks if anyone can help as i am totally stuck now and my son is without his phone.:fingers-crossed:
If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?
rodman01 said:
If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?
Click to expand...
Click to collapse
thank you for the advise i will try and see what i can do
still having trouble with the phone, every time i reflash stock rom with odin it keeps starting up but then i have a lot of force close box popping up saying about all his old apps and and setting force closing and then when it get to the start up wizard it says it has forced closed and then can not go any further, this is why i cant understand why when i wipe all data and system it is not wiping it for some reason,im waiting on a download recovery for it but if anyone can understand what i mean and no a fix i will be most grateful as i have spent many hours now searching through xda for a answer and can not find any.:fingers-crossed::fingers-crossed:
Could you give us some more information? What device do you have? And which ROMs did you try to flash? Which stock and which custom ROMS? And when do have the problems? After reboot from flashed stock rom or after flashing the custom rom? I think the stock rom you try to flash does not fit to your device?
i have tried the stock rom from samfirmware and my device is a galaxy s i9000, the custom rom was a old gingerbread rom, the problem comes when i have flashed the new stock rom with odin, it flashes with odin not a problem but then when it boots up and starts to go through the first 6 or 7 steps of the phones steps, ie ( keyboard use, packed data settings, wifi on or off and so on) it keeps popping up little dialog boxes saying sorry google play is not working force close and goes through a whole load of stuff saying the same thing for them all, hope this helps a little but is hard to describe
I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...
rodman01 said:
I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...
Click to expand...
Click to collapse
ok thank you i will try that,
thank you for all the help today but think the phone is knackered nothing will work anymore on it nothing will boot up properly :crying:
no problem and you welcome...better would have been if my proposals had worked...but perhaps you are right and there is a hardware defect or something else...perhaps even a fluid defect....or it is only stressed for today and tomorrow all is fine again ! So head up, and don't give up.
Hope you flashed Stock GB ROM with pit file and Re-partition ticked
FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app
With the amazing work by @Chainfire we are blessed with a what seems to be almost perfect replacement for SafeStrap. Yes, this is still in Beta and you should go into this expecting to soft brick your phone every time when flashing something with this. That's why we need some brave souls to test the limits of FlashFire for our poor device.
If you would like to help contribute to see what we can flash with this application here are a couple tutorials on flashing by @muniz_ri
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
http://forum.xda-developers.com/att...-to-enable-native-tethering-g900aoc4-t3078561
If you come across anything that you can flash from the smallest things or even ROMs that you have found compatible please share the knowledge here and I will try to put it in an index that others can see through this beta testing and early phase of Android Lollipop for the G900A.
ROMs that have been confirmed to be flashed and working:
G900A_OC4 5.0 Stock Rooted Android Lollipop by @muniz_ri
Miscellaneous things that have been confirmed to be flashed and working:
Native Tethering by @muniz_ri
300 Fonts for Lollipop and KitKat by @nitol
Titanium Backup's update.zip file
Remote Play Installer
Notes:
If your device stays at the black screen when you try to flash something simply pull the battery out. Then, boot into recovery and wipe the cache partitions. That should allow you to boot your device again after failure.
If you find yourself in a boot loop and downgrading back to NCE you can restore your 5.0 backup while on 4.4.2 (if you made one like you should have) by following my tutorial in the following link. http://forum.xda-developers.com/showpost.php?p=60095108&postcount=21
Here is what I know so far about FlashFire's capabilities on locked bootloader devices:
- Will run on Android v4.x.x/5.0.x.
- Will not trip your Knox Warranty Flag.
- Will flash ROM's (use "flash .zip or ota" option).
- No AROMA installer ROM's.
- Caution! FF flashes to the boot partition, i.e. flashing custom kernels will result in soft brick!
- You can drop a Full Odin .tar or .zip file containing the raw images onto your device and it will flash system, kernel, cache, and recovery (will not flash modem, non-hlos, or bootloader) (use "flash firmware package" option).
- You can flash the remaining partitions via a .zip at the same time or via your PC using Odin.
- Flashes .tars with unsigned images, e.g. system.img.ext4, modem.bin. (use "flash firmware package" option).
- You can also flash individual (un-.tar'd) images, e.g. recovery.img, boot.img.
- Flashes .zip files, e.g. mod's, SuperSu Update.zips, etc (use "flash .zip or ota" option).
- Makes Backups of and Restores all partitions.
- Wipes partitions.
- Injects Root.
I will add here as I test and learn more.
Also want to add a note of caution....if you are a noob and don't have much experience with these things don't rush in. Best to sit back until safe and responsible guides are created. I for one am not at all sympathetic to those that don't take the time to read and understand before jumping in.
muniz_ri said:
Here is what I know so far about FF:
- Will run on Android v4.x.x/5.0.x
- No AROMA installer ROM's.
- Caution! FF flashes to the boot partition, i.e. flashing custom kernels will result in soft brick!
- Flashes stock or modified images, e.g. system.img.ext4, modem.bin, non-hlos.bin.
- Flashes .zip files, e.g. mod's, SuperSu Update.zips, etc
- Makes Backups of and Restores all partitions.
- Injects Root
I will add here as I learn more.
Click to expand...
Click to collapse
One of my questions about FlashFire is will it work on encrypted phones? My work phone is Verizon GS5 and SafeStrap would not work because of my encryption, so I'd be very interested in updating that phone without losing root if it will work. Thanks for all your work!
I attempted to flash Alliance ROM 7.1 from the International Forums.
My Steps:
1. Downgrade to NCE
2. Root
3. SuperSU
4. Install FlashFire
5. Set up FlashFire in the following order;
- Wipe
- Flash Partitions and Bootloader
- Flash Alliance ROM
Everything looked to be working perfectly, but it was getting stuck on the second boot screen. Going to try it again, but after I finish installing Stock Rooted 5.0 again. Maybe it will work then. Only one way to figure out.
Great thread. I'll have a deodexed build up in the next few days then start adding mods and working on other things
Nyxerosoir said:
I attempted to flash Alliance ROM 7.1 from the International Forums.
My Steps:
1. Downgrade to NCE
2. Root
3. SuperSU
4. Install FlashFire
5. Set up FlashFire in the following order;
- Wipe
- Flash Partitions and Bootloader
- Flash Alliance ROM
Everything looked to be working perfectly, but it was getting stuck on the second boot screen. Going to try it again, but after I finish installing Stock Rooted 5.0 again. Maybe it will work then. Only one way to figure out.
Click to expand...
Click to collapse
I'm downloading Alliance as well. Let me know how your flash goes. If love to get a Rom going on lollipop.
dirtydodge said:
I'm downloading Alliance as well. Let me know how your flash goes. If love to get a Rom going on lollipop.
Click to expand...
Click to collapse
Should I try flashing the ROM as a Firmware package this time or a Zip/OTA?
Nyxerosoir said:
Should I try flashing the ROM as a Firmware package this time or a Zip/OTA?
Click to expand...
Click to collapse
Not sure. I'd think as a zip. I'm trying to learn FF.
dirtydodge said:
Not sure. I'd think as a zip. I'm trying to learn FF.
Click to expand...
Click to collapse
Going to try as a firmware package
When I tried to flash as a zip in FlashFire all it did was wipe my device then once it tried to insall the ROM it stopped then rebooted.
Nyxerosoir said:
Going to try as a firmware package
When I tried to flash as a zip in FlashFire all it did was wipe my device then once it tried to insall the ROM it stopped then rebooted.
Click to expand...
Click to collapse
I'm sounds good. I'm backing up with Kies right now.
dirtydodge said:
I'm sounds good. I'm backing up with Kies right now.
Click to expand...
Click to collapse
Just updated the 2nd post. It should provide some guidance.
muniz_ri said:
Just updated the 2nd post. It should provide some guidance.
Click to expand...
Click to collapse
Tried to flash Allience in zip/ota and after it wipes it says that it is installing the .zip file for a second then it stops and reboots. Could this be a bug from FlashFire or the ROM not compatible?
Maybe try a dirty flash of the ROM?
I grab a stock ROM directly from G900F, make G900A boot.img and system.img.ext4 into tar.md5. Flash as package in FireFlash along with G900A_OC4_Stock_Partitions_wOA1_BL.zip. Works out pretty well. Just need to disable KNOX with Titanium Backup (for some reason SuperSU doesn't detect KNOX being present) and use Root Explorer to get csc through.
However haven't figured out how to enable VoLTE yet.
Nyxerosoir said:
Tried to flash Allience in zip/ota and after it wipes it says that it is installing the .zip file for a second then it stops and reboots. Could this be a bug from FlashFire or the ROM not compatible?
Maybe try a dirty flash of the ROM?
Click to expand...
Click to collapse
I tried the dirty flash. Just stuck at black screen. I let it sit for 25 min then did a battery pull. Rom did not install. I'll leave it alone tonight before i have to stay up all night fixing a soft brick. Haha.
82801BA said:
I grab a stock ROM directly from G900F, make G900A boot.img and system.img.ext4 into tar.md5. Flash as package in FireFlash along with G900A_OC4_Stock_Partitions_wOA1_BL.zip. Works out pretty well. Just need to disable KNOX with Titanium Backup (for some reason SuperSU doesn't detect KNOX being present) and use Root Explorer to get csc through.
However haven't figured out how to enable VoLTE yet.
Click to expand...
Click to collapse
That is some very useful information. Can't wait to give it a go tomorrow! Time for some rest.
Do you have SQLite Editor? Maybe VoLTE can be implemented though it.
Nyxerosoir said:
That is some very useful information. Can't wait to give it a go tomorrow! Time for some rest.
Do you have SQLite Editor? Maybe VoLTE can be implemented though it.
Click to expand...
Click to collapse
@Nyxerosoir It's not that the option that is not there. It is just I am not able to enable it (grayed out) or it says "VoLTE is not supported by your current software version. Contact customer service for more details." if I try to enable it on quick settings.
Nyxerosoir said:
Tried to flash Allience in zip/ota and after it wipes it says that it is installing the .zip file for a second then it stops and reboots. Could this be a bug from FlashFire or the ROM not compatible?
Maybe try a dirty flash of the ROM?
Click to expand...
Click to collapse
A general principle to keep in mind is when flashing ROM's at the very least the kernel needs to match the system, i.e. 5.0 system requires the G900A Stock 5.0 kernel, 4.x system requires the G900A Stock 4.x kernel. The matching G900A Stock non-hlos will likely also be required in order for the ROM to work correctly.
I finally managed to get the font package by @nitol to work. The first time I ended up with a bootloop, but then I tried wiping dalvik and cache and flashing. Worked like a charm! Updated it in the OP for the index.
Can i upgrade from custom 4.4.2 to stock 5.0 via flashfire without needing a pc odin to flash bootloader and modem ? (I have G900F so unlocked bootloader)
waleed794 said:
Can i upgrade from custom 4.4.2 to stock 5.0 via flashfire without needing a pc odin to flash bootloader and modem ? (I have G900F so unlocked bootloader)
Click to expand...
Click to collapse
Yes, follow @muniz_ri's guide and you can successfully upgrade from 4.4.2 to 5.0 without a PC.
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803