Related
When trying to switch to a different rom, even after factory reseting and clearing all the cache. Parts of the old ROM consist such as the notification tray colors on the pull down. I dont understand because ive cleared it all
You might have to wipe and start again. I had that problem yesterday.
Sent from my ADR6400L using XDA App
David522d said:
When trying to switch to a different rom, even after factory reseting and clearing all the cache. Parts of the old ROM consist such as the notification tray colors on the pull down. I dont understand because ive cleared it all
Click to expand...
Click to collapse
If all you are clearing is the cache, and not wiping data/cache/davlik, that is your problem right there...
Ive cleared them all 3 times now and still getting the same problem.
David522d said:
Ive cleared them all 3 times now and still getting the same problem.
Click to expand...
Click to collapse
You've gotta be doing something wrong then. Never had this problem before.
What could I be doing wrong. This is getting frustrating
Sent from my ADR6400L using XDA App
You may have to do a full factory reset
FishyChips said:
You may have to do a full factory reset
Click to expand...
Click to collapse
HOW?
Can someone please help
I just tried factory reseting from the phone menu itself no luck. I feel like this ROM is glued to my phone regardless how many times i try to kill it.
WHATS THE DEALLLLLLLLLLLLLLL
David522d said:
I just tried factory reseting from the phone menu itself no luck. I feel like this ROM is glued to my phone regardless how many times i try to kill it.
WHATS THE DEALLLLLLLLLLLLLLL
Click to expand...
Click to collapse
When all else fails, follow unroot steps to return to stock and restart the process. Something you're doing doesn't seem to be adding up.
nerozehl said:
When all else fails, follow unroot steps to return to stock and restart the process. Something you're doing doesn't seem to be adding up.
Click to expand...
Click to collapse
I feel losing root wont gain anything more then re rooting.
Its 1 thing the notification colors in the pull down.
What ROM are you trying to flash, and what recovery are you using? The most reliable is arguably the Clockworkmod version...
Sent from my HTC Desire using XDA App
techtechnique said:
What ROM are you trying to flash, and what recovery are you using? The most reliable is arguably the Clockworkmod version...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
David522d said:
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
Click to expand...
Click to collapse
Returning to stock is a good way to resolve this issue.
So guess what, you can change the color inside the rom settings
Oh thanks for the help
Are you using ROM manager to flash roms or doing it manually? if your not you should try rom manager it has an option that lets you wipe all data before flashing the new rom. i use it and ive never had any problems
David522d said:
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
Click to expand...
Click to collapse
If you search this forum or Google 'unrevoked', you'll easily find a complete guide and walkthrough on how to root your phone, which'll (as part of the process) load clockworkmod boot recovery.
The next time you reboot, hold the volume down key, which takes you into your boot screen, and use the vol up and down keys to select 'recovery', and press the power button.
From there, wiping your cache partitions and doing a full factory wipe is very straightforward.
That's the easiest way to fully flatten your phone before installing a new ROM.
Edit - the process might differ a bit for your model phone, but the principle will be the same...
Sent from my HTC Desire using XDA App
It's not clear to me why some people had a successful webOS 3.0.5 update with Android installed, others didn't. And some people even had stock Touchpads which have problems now after the update? Wow!
If I'm on 3.0.4 with XRON 2.9 installed; what is it I have to do in order to successfully update without having to wipe everything and start anew?
I've read this thread two or three times, plus this other thread, which seems to be ONLY for people who had a failed update, and I'm not entirely sure.
Can someone help with a 1,2,3 kind of scenario?
Thanks!
Well, it seems so far(that I have noticed) that the update will fail if you are using moboot 0.3.3 or 0.3.4. Follow this, and all should be good.
1.) Make a nandroid backup of your android in CWM
2.) Make a backup of webOS(Launcher>Settings>Backup
3.) Make sure you have moboot 0.3.5
4.) Click System Updates in webOS and let it download.
5.) Once finished, try to install.
6.A) Based on my observations, it should install fine.
6.B) If for some reason it doesn't work, that's ok, because you have backed up everything. Follow standard procedure for removing android, and getting webOS back to stock, and install everything(moboot, cwm, android). Then once everything is back, restore your backups.
Sent from my Legendary 2.2 infused device.
FWIW, I did the update yesterday without any major issues.
Prior to the update I had CM7 A3.5 installed and WebOS 3.04. My moboot was still on 0.3.3 as I had never updated it since my initial Android install.
I did the update in WebOS and let it do its thing for a while. When I rebooted the only difference was the bootloader was gone and it would just boot straight into WebOS 3.0.5.
I reinstalled Moboot (0.3.5 this time) and then booted back up into Android and all was fine. I hadn't backed anything up and I hadn't lost anything.
Of course, as always, YMMV.
I was on moboot 0.33 and webos 3.02 and the ota update locked into a boot loop.
Just had to doctor and re-acme CWM, CM7.1 and moboot before restoring my nandroid backup.
Sent from my HTC G2
Thanks guys; I just rebooted to see the menu, and indeed I have the lastest MoBoot (0.3.5). So I am going to back everything up and do this tomorrow.
Thanks for taking the confusion away. I love XDA, but let's be honest, there is so much information, so many threads with thousands of posts, that the whole thing becomes impossible to digest.
Too much information is sometimes worse than having not enough information!
Xaltotun said:
Thanks guys; I just rebooted to see the menu, and indeed I have the lastest MoBoot (0.3.5). So I am going to back everything up and do this tomorrow.
Thanks for taking the confusion away. I love XDA, but let's be honest, there is so much information, so many threads with thousands of posts, that the whole thing becomes impossible to digest.
Too much information is sometimes worse than having not enough information!
Click to expand...
Click to collapse
Good luck bud. Just be sure to back up both as I stated just in case the install doesn't work.
Sent from my Legendary 2.2 infused device.
not to add more confusion to this, but I upgraded without any trouble and I later found out I'm on moboot 3.3. once the upgrade was done I shut off the tp and when I restarted it went straight into moboot. So I'm not sure the moboot version is the critical factor here.
As long as you backup both webos and android I think you should be fine. Although I might ask if you still use webos enough to bother. I didn't see a whole lot new but I didn't spent much time on it.
I failed twice updating, restored palm kernels removed all preware patches and success. Moboot 3.0.4, xron 2.9 were untouched.
Will we be able to run tablet compatible apps in ics?
Sent from my Touchpad using xda premium
sLiKK said:
Will we be able to run tablet compatible apps in ics?
Sent from my Touchpad using xda premium
Click to expand...
Click to collapse
Yes.
Sent from my Legendary 2.2 infused device.
I'm on 0.3.5 and its failed everytime. I unistalled kernels, etc.
zanderman112 said:
Yes.
Sent from my Legendary 2.2 infused device.
Click to expand...
Click to collapse
Can't wait .....
Sent from my SGH-T959 using xda premium
sLiKK said:
Can't wait .....
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I cant wait for CM9.
Sent from something with a Ｋモ尺れモㄥ.
Well I backed-up everything and did the update. It seems to have worked.
I did get a couple of random reboots, but I got those before. Not sure if the reboots are due to the update or not.
Thanks to all who have contributed to this thread.
I'm new to the world of Android and rooting...I have an HTC Thunderbolt with all of the updates and completed the root process using a one-click program found on a different XDA thread. This program allows rooting without any file loss or software downgrades (hope I'm correct??)
With that said...First: how do I verify that my Thunderbolt is rooted? Does the 'SuperUser' app verify the process was successful or do I have to check somewhere else?
From here, what apps would I use to increase phone performance (slow screen refresh, etc.?) and what other enhancements can I change (tired of waiting for ICS)??
Thanks for any help and guidance that can be provided,
ghdroiduser
There's an app called root checker in the market that you could use. As far as enhancements go there aren't very many apps you can get to better performance. You could get a root uninstaller to remove useless apps that you otherwise couldn't get rid of. Best way to get a better phone going is to flash a custom Rom. There are a few roms that have been developed that are ICS but don't have a working camcorder. Although, flashing these roms will cause you to lose your user data...
Sent from my Thunderbolt using xda app-developers app
Will this Work...?
I read about an app called V6 supercharger, is this designed for HTC phones? If not, is there another app like it?
Where can I find out more about how rooting my phone let's me change the configuration? Do I have to uninstall and re-install my apps for the superuser function to take over?
Any help or guidance is appreciated...
Thank you,
ghdroiduser
ghdroiduser said:
I read about an app called V6 supercharger, is this designed for HTC phones? If not, is there another app like it?
Where can I find out more about how rooting my phone let's me change the configuration? Do I have to uninstall and re-install my apps for the superuser function to take over?
Any help or guidance is appreciated...
Thank you,
ghdroiduser
Click to expand...
Click to collapse
Hmm... never heard of that app. You don't have to uninstall apps for superuser to take affect although superuser doesn't do anything to typical apps that you would have had before you rooted. I'm really not sure of what you can do on a stock Rom. If I remember, the only time I had a rooted phone with a stock Rom I didn't do anything to it. The best option to better your performance is to install a custom Rom. Make a backup of your stock Rom in recovery in case you need to get back to it. Also, don't take any OTA updates while you are rooted because that will brick your phone and its quite the process to unbrick.
Sent from my Thunderbolt using xda app-developers app
What next...Two
My inquiry from the other day was incorrect...v6 supercharger is a script for improving a rooted phone's memory performance, not an app...that would explain why some people were unfamiliar with the question. When I complete the rooting process, will my my have 'S-root' and what is 'S-root'?
Is this script better than 'smurf' once my device has been rooted?
Additionally, I would like to maximize the Thunderbolt's performance...what would be the next step??
I would like ICS on my phone, however, it seems that Verizon will never get this done...I see there are several roms available for ICS...are there are any roms that do not loose any of the phone's current functionality?? Can I install more than one rom like multiple booting a computer with more than one operating system??
I used a 'one-click' root program from a different xda forum.
HTC Thunderbolt w/ GB 2.3.4, Go Launcher EX
Thanks for any help or instructions that will assist me,
ghdroiduser
V6 supercharger does help with performance. The liquid ics roms are great and the only functionality you will lose is camcorder. Once you have it installed you can over clock the CPU if you want more performance although it really isn't necessary.
Sent from my Thunderbolt using Tapatalk 2
What next...Two
disconnecktie said:
V6 supercharger does help with performance. The liquid ics roms are great and the only functionality you will lose is camcorder. Once you have it installed you can over clock the CPU if you want more performance although it really isn't necessary.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your answer...Since I do not use the camcorder function, no great loss...
Are all of the Liquid ICS roms the same or is one source better than another?? What will happen to my phone once Verizon finally release the ICS update or any other update for that matter??
Is 'S-root' something that I have to install or configure? Or does it install/configure during the rooting process?
Again thanks for the help,
ghdroiduser
You must be talking about s off. S off is something that should be done during the rooting process to allow for the installation of aftermarket kernels and for changing radios. In the dev section there is a tool called the allinone thunderbolt tool that will do all of that. You really should get it and run that. There are two versions of liquid ics. One is the stock version and the other is jmod which is the one that sounds more up to speed for you. It comes with the supercharger script already in place so you don't have to do that yourself. Once you flash it you won't have to worry about the official release affecting you at all.
Sent from my Thunderbolt using Tapatalk 2
What next...Three
disconnecktie said:
You must be talking about s off. S off is something that should be done during the rooting process to allow for the installation of aftermarket kernels and for changing radios. In the dev section there is a tool called the allinone thunderbolt tool that will do all of that. You really should get it and run that. There are two versions of liquid ics. One is the stock version and the other is jmod which is the one that sounds more up to speed for you. It comes with the supercharger script already in place so you don't have to do that yourself. Once you flash it you won't have to worry about the official release affecting you at all.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
I appreciate all of your help...I found this link for the ICS flash 'Liquid ICS *MR2V7'...Is this the most current rom you mentioned above??
If so, once I complete the download what do I need to set this up...meaning the instructions to install the rom....
Thank again for your help...
Before you flash anything reboot into your boot loader by powering the phone down and then holding volume down and power. The screen will come up with some info in the top left corner of the boot loader. Tell me what that is showing.
Sent from my Thunderbolt using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
The rom version you looked at is the one I was referring to.
Sent from my Thunderbolt using Tapatalk 2
What next...Three
disconnecktie said:
Before you flash anything reboot into your boot loader by powering the phone down and then holding volume down and power. The screen will come up with some info in the top left corner of the boot loader. Tell me what that is showing.
Sent from my Thunderbolt using Tapatalk 2
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
The rom version you looked at is the one I was referring to.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
This is what I see:
-Revolutionary-
MECHA XD SHIP S-OFF
HBOOT-6.04.1002
MICROP-/
RADIO-4.49.00.0406w_1
eMMC-boot
Feb 23 201,20:42:55
I hope this is the correct information...What is this telling you??
ghdroiduser
Alright you're good to go. You do have s off which I wasn't sure of. What you need to do is download the rom OK. To get ready for flashing reboot into recovery by going into the boot loader the way I told you. Once there, press volume down so that it will let you choose something in that menu. Select bootloader. After that it will run a check to see if you have a radio update on your SD card. Once it finishes press volume down to highlight recovery. Press power. Once in recovery you need to wipe data cache and dalvik cache before flashing the rom. This is important. If you don't then it will either not boot or it will bootloop. I don't remember all of the menus in cwm because I haven't used it in so long. Go to the menu that let's you select the file for flashing. If you downloaded it from the phone then it will be in the download folder. Find the file and select it. It should prompt you if you want to flash it. Select yes and there you go. You're off into your first ics rom.
Sent from my Thunderbolt using Tapatalk 2
disconnecktie said:
Alright you're good to go. You do have s off which I wasn't sure of. What you need to do is download the rom OK. To get ready for flashing reboot into recovery by going into the boot loader the way I told you. Once there, press volume down so that it will let you choose something in that menu. Select bootloader. After that it will run a check to see if you have a radio update on your SD card. Once it finishes press volume down to highlight recovery. Press power. Once in recovery you need to wipe data cache and dalvik cache before flashing the rom. This is important. If you don't then it will either not boot or it will bootloop. I don't remember all of the menus in cwm because I haven't used it in so long. Go to the menu that let's you select the file for flashing. If you downloaded it from the phone then it will be in the download folder. Find the file and select it. It should prompt you if you want to flash it. Select yes and there you go. You're off into your first ics rom.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
Just to add dont get scared if it takes awhile to boot up once its done flashing and you reboot. Some roms can take a few min to fully boot. So when its on the splashscreen just let it be and let it load all the file you just flashed. Welcome to the world of rooting.
What next...Three
Dark Jedi said:
Just to add dont get scared if it takes awhile to boot up once its done flashing and you reboot. Some roms can take a few min to fully boot. So when its on the splashscreen just let it be and let it load all the file you just flashed. Welcome to the world of rooting.
Click to expand...
Click to collapse
When I download the ROM, will I do this to my phone or on my p/c with a usb cable??
Are there any other precautions I should be aware of??
Also, I saw another post about using 4ext vs revolutionary...any thoughts??
Thank you for all of your help...
ghdroiduser said:
When I download the ROM, will I do this to my phone or on my p/c with a usb cable??
Are there any other precautions I should be aware of??
Also, I saw another post about using 4ext vs revolutionary...any thoughts??
Thank you for all of your help...
Click to expand...
Click to collapse
I would suggest using 4ext. Its easier to navigate since the recovery is touch enabled and the menus are organized better. Flashing the rom should be done from the phone although it is possible to do it from the PC I wouldn't recommend you trying that just yet. The main thing to remember when flashing a rom is always do a nandroid backup first. I did forget to tell you that. Also just remember to wipe data,cache and dalvik cache before you flash a rom unless the developer makes it clear that it is OK to flash over the current build.
Sent from my Thunderbolt using Tapatalk 2
ghdroiduser said:
When I download the ROM, will I do this to my phone or on my p/c with a usb cable??
Are there any other precautions I should be aware of??
Also, I saw another post about using 4ext vs revolutionary...any thoughts??
Thank you for all of your help...
Click to expand...
Click to collapse
Not really as long as you wipe your caches and data you should be good to go. You can download the rom on to your phone or you can download on to your PC. Once on your PC you will have to transfer the file to your phone via the usb cable.
4ext is a nice touch screen recovery. So you dont have to wear out your vol rockers and power button. Its easy to install just need to download the app.
Heres the thread about 4ext http://forum.xda-developers.com/showthread.php?t=1890323
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
when i install RLS 6 hyperdrive my phone starts fine but after one minute it restarts and again turns again on works fine for 30 seconds and again restart help!!!!
When posting something like this its good to know the beforehand so people know what led up to this. Did you wipe? What recovery you using? Did you follow the install instructions word for word?
SCH-I545 using Tapatalk 2
A couple of possibilities:
Make sure you wipe per the dev's recommendations prior to flashing.
Try installing with minimal mods and see if you can get it to boot. Once you flash, you can always dirty flash the same installer and pick a couple additional mods and see what's causing the issue. Some people noted they were having problems with the Walkman mod causing bootloops.
Check the MD5 of your download against what is in the OP. If you downloaded to PC then copied to SD card, check that the MD5 on the card matches that on the PC and what's online (some people had problems where the file was corrupted during transfer to phone).
Also making sure you have one of the most recent recoveries is a good thing to check. I believe I used TWRP 2.6.0.0 and it worked fine for me.
Finally, try using the stock kernel instead of stock optimized or a third party kernel. I can use stock or stock optimized, for example, but when I flash faux it bootloops about 80% of the time on my phone.
There is a good bit of info about the bootlooping issue on RLS6 in the original Hyperdrive thread. Start on page 472 and read on from there.
http://forum.xda-developers.com/showthread.php?t=2301724&highlight=bootlooping&page=472
hexitnow said:
When posting something like this its good to know the beforehand so people know what led up to this. Did you wipe? What recovery you using? Did you follow the install instructions word for word?
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
yes i did man i swear !!!!
thanks
wontongo said:
There is a good bit of info about the bootlooping issue on RLS6 in the original Hyperdrive thread. Start on page 472 and read on from there.
http://forum.xda-developers.com/showthread.php?t=2301724&highlight=bootlooping&page=472
Click to expand...
Click to collapse
thanks but i dont think that my problem sir thanks !!! more help please?
Did you flash with twrp or cwm. Theres been a few people reporting bootloops when wiping/flashing with twrp. If so you might want to try cwm. Have been using cwm since the DX was the "it" phone. Got it on 4 devices now and have never had a single problem with it.
SCH-I545 using Tapatalk 2
i found the solution
hexitnow said:
Did you flash with twrp or cwm. Theres been a few people reporting bootloops when wiping/flashing with twrp. If so you might want to try cwm. Have been using cwm since the DX was the "it" phone. Got it on 4 devices now and have never had a single problem with it.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
the solution was not to install any audio mods and any players like the walkman just the samsung one thanks man !!
TWRP = bad news with HD6
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
dvdrsmth said:
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
Click to expand...
Click to collapse
I've installed HD6 twice on my phone using TWRP 2502. I followed Dev's installation instructions to the T and have had zero issues.
Includes inissac
reebz said:
I've installed HD6 twice on my phone using TWRP 2502. I followed Dev's installation instructions to the T and have had zero issues.
Click to expand...
Click to collapse
Good to know. I believe that I followed the dev instructions as well.
One time my uncle was over and I was telling him about a marital concern. He told me that I should probably not do what I had been doing and that there was probably a better way. I listened to him and life has been better. Life is full of choices.
dvdrsmth said:
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
Click to expand...
Click to collapse
I agree, like I said have been using it on multiple devices, for close to 3 years now and have never had a single problem. Tried out twrp a few weeks ago and didnt like it to much. To each his own though :thumbup:
SCH-I545 using Tapatalk 2
I have also been having difficulty with both bootloops and the phone freezing on the Samsung image and not booting past this point.
I did a full wipe including data with Twrp. After multiple attempts I'm considering switching to CWM. My question is how to I install CWM on a device without a functioning rom?
Does this require flashing back to stock with odin or is there an easier way?
Sent from my SPH-L900 using Tapatalk 2
rickt1152 said:
I have also been having difficulty with both bootloops and the phone freezing on the Samsung image and not booting past this point.
I did a full wipe including data with Twrp. After multiple attempts I'm considering switching to CWM. My question is how to I install CWM on a device without a functioning rom?
Does this require flashing back to stock with odin or is there an easier way?
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
You can flash CWM from within TWRP, just use ADB to copy the zip file onto your phone then flash, or alternatively you can use fastboot to flash a new recovery directly to the phone. Neither method needs a working ROM to accomplish.