Database Develop

Trying to load a custom rom, wth am i doing wrong?

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.

Trying to restore Steak 7 Wifi to stock, need help quick!

I need to return it to stock before returning it, and I've got less than a week to do so. I've tried so many different methods and files, and the closest I've gotten is a stock/factory reset (with the original setup screen) with a root with Clockwork Recovery (CWR) installed.
I can't use the method in this thread, since this is for the T-Mobile version, and removing the T-Mobile apps and bootscreen would require my rooting it, which would put me back at square one:
http://forum.xda-developers.com/showpost.php?p=12590019&postcount=1
I did find a Wifi version of it in this post, but after flashing it multiple times (once after botching a recovery flash and being unable to boot into it), I think I found out that it's already rooted with CWR installed:
http://forum.xda-developers.com/showpost.php?p=14303822&postcount=3
And then I tried using this method (along with simply using fastboot to flash the stock recovery from the first link), and every time either CWR still came up, or no recovery came up and it simply booted into the OS when I tried to do the update or full factory reset option:
http://forum.xda-developers.com/showpost.php?p=12355315&postcount=1
EDIT: I also found this method looking through the boards, but sadly the files are also for the T-Mobile version:
http://forum.xda-developers.com/showpost.php?p=12453284&postcount=1
(I can't even access the flash_image file needed because the link is invalid)
Any help? I'd rather not return the Streak in its rooted state, even if it looks stock. If all else fails...I'll just use the method in link 2 to restore it, since at least it looks stock when it first boots up...

use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.

shadowswithin said:
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
Click to expand...
Click to collapse
I'll try that now, I'll post how it turns out. I tried using Gingerbreak to unroot earlier, but didn't think it would work since it just rebooted with no changes.
EDIT: Seems to work so far, I need to recharge before I can use the update or full reset options in the recovery and see if CWR is truly gone, but in any case, thank you so much, finally got it stock and unrooted.

Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.

magus57 said:
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
Click to expand...
Click to collapse
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.

I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.

jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.

jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried the files from that thread, but they are for the t-Mobile version, not the wifi only version. Does anybody know where we can find a stock wifi only recovery image?

bimbot said:
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
Click to expand...
Click to collapse
Yeah, I wouldn't bother, doubt it'd work for you if it didn't work for me the however many times I tried it.
And if you've ever done anything in adb with the Android SDK, fastboot is similar - basically, you hold volume (-) and power, wait to get into fastboot, plug it into the computer, and use:
fastboot flash recovery recovery.img
to flash to the recovery. That also works for boot and system.
Bigirish said:
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
Click to expand...
Click to collapse
Try doing the NVFlash method in APX mode, it's pretty much guaranteed to work. It's the method in the first link in my original post, and the files for the Wifi version are in the second post (extraded, the .rar file is like 14GB's, you only need the images p2 though p14 to flash). You'll still have root and CWR, but at least you'll be out of the boot loop and you'll still be able to at least remove root with Gingerbreak.

[Q] Problems with custom rom HTC one

I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?

There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.

iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...

Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.

iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.

Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?

Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.

bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.

[Q] Troublehooting with bricked Galaxy Note needed

Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?

Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?

grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.

User_99 said:
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
Click to expand...
Click to collapse
I have the Stock Samsung Android 4.1.2 installed. I'll try it again with an older kernel. Thanks for your help.

nokiamodeln91 said:
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
Click to expand...
Click to collapse
I tried it several times, also after removing the battery. no success. Is is necessary to use ODIN? I use Heimdall as I mentioned, because I am running Mac OS.
I'll try it with a different kernel and report back here about my results. Thanks a lot.

Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.

What
grosserzampano said:
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
Click to expand...
Click to collapse
Install terminal emulator and try the command
su
reboot recovery.

Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.

grosserzampano said:
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
Click to expand...
Click to collapse
May be the recovery partition is messed up due to the usage of rom manager earlier. Try to flash a stock rom.

grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
go to download mode and flash stock rom of note 1 via odin then after successful installation u can go to recovery mode and install this zip ur phone will be rooted and phliz touch will be installed
for any help u can PM me

Can't enter recovery, everything else works (sort of)

Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?

samcool55 said:
Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
Click to expand...
Click to collapse
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.

rog_star said:
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
Click to expand...
Click to collapse
Tried that, but UKF says device unsupported, don't know why... I have used it before and it worked then.
Any other options?

I got it fixed. But tbh i still don't understand how. I flashed JB stock with odin and when it rebooted, i got automaticly into CWM weirdly enough... Wasn't going to waste my maybe only chance so i flashed the custom rom, wiped everything again, reboot, went again automaticly into CWM. anyway i was third time lucky and it booted as it should. Everything is working now! Anyway thanks for trying to help.