Related
Hello this will be my first post, although I have been a forum lurker, I have been doing it for awhile. Now my problem is that I want to switch ROM's but i have had problems in the past, I successfully rooted and unlocked the Bootloader with Xfactor exploit. My first time flashing a rom on the hox, I did something wrong and found out that when I did my nandroid backup it failed (Yes I know i'm ashamed I made such a nooby mistake). Luckily I had a friend who knew his way around phones a little better, and flashed it to Nocturnal ROM, It's nice and all but I have had my eyes on Paranoid Android. This time I know for sure I have a nandroid backup and I have a copy on my computer, but I want to make sure there is nothing else wrong if I try. Can I get a line of steps to sort of follow? I did flash ROM's on my HTC Inspire, but it just isn't the same case her obviously. I know you have to seperate the boot.img from the ROM files but that is where my last ROM flash screwed me over.
Try using viperxl Rom , its awesome. If you use twrp there is no need to flash img as twrp does it auto for ya
Sent from my HTC One XL using xda premium
---------- Post added at 12:53 AM ---------- Previous post was at 12:50 AM ----------
http://forum.xda-developers.com/showthread.php?t=1671237
Here is a good link to always keep handy
Sent from my HTC One XL using xda premium
DESERT.TECH said:
Try using viperxl Rom , its awesome. If you use twrp there is no need to flash img as twrp does it auto for ya
Sent from my HTC One XL using xda premium
---------- Post added at 12:53 AM ---------- Previous post was at 12:50 AM ----------
http://forum.xda-developers.com/showthread.php?t=1671237
Here is a good link to always keep handy
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Which HBoot are you? If you are on 1.14 you need to flash the boot image either via command prompt of flashgui.
Fastboot is easier in my opinion.. Download PA on your phone.. Plug it in and COPY rom to your computer. Extract rom, drag and drop boot.Img inside your adb/fastboot folder. Enter Fastboot on phone. If on windows 7, right click on adb folder and choose "open command prompt here"
Command is fastboot flash boot boot.Img
Success. In bootloader, choose recovery. Flash entire PA zip, flash gapps.
Profit!
Sent from my One X using Tapatalk 2
cpttrippa said:
Which HBoot are you? If you are on 1.14 you need to flash the boot image either via command prompt of flashgui.
Click to expand...
Click to collapse
Not with viper. It flashes it for you
Sent from my HTC One XL using xda app-developers app
Alright I feel a little more ready to switch, but there is no way this could fail right? Having a backup on my phone and computer? I'm just being over protective haha
Edit: and yes I am above 1.14
InflatedTitan said:
Fastboot is easier in my opinion.. Download PA on your phone.. Plug it in and COPY rom to your computer. Extract rom, drag and drop boot.Img inside your adb/fastboot folder. Enter Fastboot on phone. If on windows 7, right click on adb folder and choose "open command prompt here"
Command is fastboot flash boot boot.Img
Success. In bootloader, choose recovery. Flash entire PA zip, flash gapps.
Profit!
Fast boot is also more reliable. A few times I flashed kernel thru flash GUI and it didn't take. Had to fast boot it.
Sent from my HTC One XL rocking Jelly Bean.
Click to expand...
Click to collapse
area51avenger said:
Not with viper. It flashes it for you
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
It's good info.... But he wants to try paranoid android... Not viper
Sent from my One X using Tapatalk 2
How does viper get around fastbooting kernel?
Sent from my HTC One XL rocking Jelly Bean.
If Viper has made it so you don't have to flash a boot.IMG they have made a pretty big breakthrough and I'm sure that would of been news, just saying. Anyways on topic, is there any other precautions I should take before trying to flash it?
Sent from my HTC One XL using xda app-developers app
Alphacall2 said:
If Viper has made it so you don't have to flash a boot.IMG they have made a pretty big breakthrough and I'm sure that would of been news, just saying. Anyways on topic, is there any other precautions I should take before trying to flash it?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
?? It's true, no need to flash boot.img separate with Viper or CleanRom. Just go into twrp, wipe everything and do a factory reset INSIDE twrp and then flash. Follow Aroma Installer and choose your options.
Those are the only "precautions" I'd say. Obviously ensure you have a backup on your phone to go boot from in case there's an issue. That would be the best precaution to take.
ATT HOX Premium App--Stock is fine but modded is Creative
I think you guys are mistaken a little with hboot 1.14 it just doesn't change your kernel when you fkasha new Rom so of course if your going from the non jb viper to clean Rom you won't have a problem since its still a sense kernel but going from aosp to sense is a different story if you were to go from aosp to viper either viper you would have to flash the boot img and same with viper jb to a non jb sense Rom....do you see how that works?it just doesnr change your kernel and if your going to a similar Rom you won't have a problem with it it'll just stay on that kernel since it works with that Rom
Ics version of Viperxl will flash the kernel for you automatically.. 2.4.0
Jellybean version 3.0.0 does NOT flash it for you, it has to be done via fastboot or flashgui app. It is an alpha version, turge will include this is further builds but he's working on ironing out the wrinkles...
A few tips for 1.14 hboots.........
If you UPGRADE a rom, you usually won't have to flash boot.Img separate as it will most likely use the same kernel as the previous build, but it's always best to ask before flashing just in case they modify the kernel
If you switch from aosp to sense, or vice versa you WILL have to flash it separate. No matter what.
Or you can boot into Linux and downgrade your hboot but that's not for the faint of heart
Personally, I'd flash kernels through fastboot as you can pretty much guarantee it will stick and be good to go
Sent from my One X using Tapatalk 2
InflatedTitan said:
Ics version of Viperxl will flash the kernel for you automatically.. 2.4.0
Jellybean version 3.0.0 does NOT flash it for you, it has to be done via fastboot or flashgui app. It is an alpha version, turge will include this is further builds but he's working on ironing out the wrinkles...
A few tips for 1.14 hboots.........
If you UPGRADE a rom, you usually won't have to flash boot.Img separate as it will most likely use the same kernel as the previous build, but it's always best to ask before flashing just in case they modify the kernel
If you switch from aosp to sense, or vice versa you WILL have to flash it separate. No matter what.
Or you can boot into Linux and downgrade your hboot but that's not for the faint of heart
Personally, I'd flash kernels through fastboot as you can pretty much guarantee it will stick and be good to go
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I have a question, so I'm pretty new to android scene with kernals and roms but I have a basic sense on how everything goes now. I tried the new CM10.1 nightly with JB4.2 and it was great but still unstable for a daily driver. I switched to cleanrom and everythings fine so far but I had some problems with my SD becoming unmountable but I ended up just reformatting it which I don't know if it was a smart idea or not. Luckily, nothing bad happened yet and everything seems to be working fine. I have CleanRom 5.1 and Element 3.2, underclocked and undervolted. Realized that I didn't need this much battery so I'm planning on checking out Viper. (13 hrs and I still have 75% haha)
Problem is, since I switched from an aosp back to a sense based rom I want to ensure everythings fine. I want to flash boot since I don't remember doing it once just to make sure viper installs nice and clean. How would I go about doing this? I pretty much know how to flash it in cmd etc, I just need to know where to get the actual boot.img file and which folder should I place it in. Thanks. Better safe than sorry.
As a side note, between switching roms I did a complete wipe. Just didn't flash boot.img. Oh and I have hboot 1.09 and am using TWRP 2.3 Recovery.
thanks again
crisjed said:
I have a question, so I'm pretty new to android scene with kernals and roms but I have a basic sense on how everything goes now. I tried the new CM10.1 nightly with JB4.2 and it was great but still unstable for a daily driver. I switched to cleanrom and everythings fine so far but I had some problems with my SD becoming unmountable but I ended up just reformatting it which I don't know if it was a smart idea or not. Luckily, nothing bad happened yet and everything seems to be working fine. I have CleanRom 5.1 and Element 3.2, underclocked and undervolted. Realized that I didn't need this much battery so I'm planning on checking out Viper. (13 hrs and I still have 75% haha)
Problem is, since I switched from an aosp back to a sense based rom I want to ensure everythings fine. I want to flash boot since I don't remember doing it once just to make sure viper installs nice and clean. How would I go about doing this? I pretty much know how to flash it in cmd etc, I just need to know where to get the actual boot.img file and which folder should I place it in. Thanks. Better safe than sorry.
As a side note, between switching roms I did a complete wipe. Just didn't flash boot.img. Oh and I have hboot 1.09 and am using TWRP 2.3 Recovery.
thanks again
Click to expand...
Click to collapse
You good to go bro! Hboot versions 1.09 have no bounds. You can flash roms, kernels, splash screens, radios etc. There is no need for fastboot whatsoever as long as your on 1.09! :thumbup:
Don't worry about formatting your SD.. I do it every Sunday night to keep my phone on a diet LOL.
I always install roms clean, so I wipe everything in twrp and never do a titanium backup or restore to ensure there's no bugs being caused by me.
Hope I helped lol
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
You good to go bro! Hboot versions 1.09 have no bounds. You can flash roms, kernels, splash screens, radios etc. There is no need for fastboot whatsoever as long as your on 1.09! :thumbup:
Don't worry about formatting your SD.. I do it every Sunday night to keep my phone on a diet LOL.
I always install roms clean, so I wipe everything in twrp and never do a titanium backup or restore to ensure there's no bugs being caused by me.
Hope I helped lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Okay cool, thanks! installing viper right now, any other, roms, kernals etc you want to recommend. Im pretty new and I feel like there's a whole lot to experience!
crisjed said:
Okay cool, thanks! installing viper right now, any other, roms, kernals etc you want to recommend. Im pretty new and I feel like there's a whole lot to experience!
Click to expand...
Click to collapse
I'm on Viper 2.4.1 with ElementalX kernel and its awesome, stable and fast. Battery life can be optimized with the built in CPU manager or something like SetCPU. You can get kernel suggestions right inside Venom Hub app on your new Rom.
ATT HOX Premium App--Stock is fine but modded is Creative
Man there's a whooollleee bunch of awesome roms.. just flash one every other day till you find what you like lol.. there's some nice sense roms, but I'm more into aosp roms. They all offer something unique and each dev brings something new to the table
Sent from my HTC One XL using Tapatalk 2
Hey I thought I would stop by to say that i successfully flashed paranoid android, one problem the keyboard keeps crashing. What are the solutions for this? A simple cache clear just isn't doing it.
Edit: Scratch that alot of things are crashing. help?
Super mega edit: I learned that i had the incorrect gapps downloaded I flashed the correct ones and it is still happening so that is out of the question
Sounds like there could be a few problems so were gonna go with the most popular ones lol..
1. Sounds like you didn't wipe everything in twrp before you flashed. Make your you always wipe cache, dalvick, factory reset, and system. Then flash Rom followed by gapps.. then reboot
2. Have you restored from a titanium backup? If so, make sure next time its ONLY user apps.. if you restore system apps and data, think of your system settings from one Rom clashing with the system files from your new Rom. They won't play nice together. Only backup and restore user apps+data
3. If the above steps were taken correctly, I would delete the Rom.zip from phone. Maybe download using a different browser. Chrome browser is notorious for corrupting roms.. you could have had a bad download
Sent from my HTC One XL using Tapatalk 2
So I'm having a problem installing any AOSP ROMS on my one x. I can install any sense 4+ plus ROMS but cyanogenmod, jellybam , etc won't install they just bootloop constantly . I'm on the latest version of viper jellybean . It's a weird case unless i'm missing something which I think. Please help if you can
Sent from my HTC One X using xda app-developers app
marquavious said:
So I'm having a problem installing any AOSP ROMS on my one x. I can install any sense 4+ plus ROMS but cyanogenmod, jellybam , etc won't install they just bootloop constantly . I'm on the latest version of viper jellybean . It's a weird case unless i'm missing something which I think. Please help if you can
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
FLASH. THE. BOOT.IMG. USING. FASTBOOT.
Sent from my One X using Tapatalk 2
I've done that each time too . I had to , to even get on viper.
Sent from my HTC One X using xda app-developers app
Have you taken the stock JB update?
That upgrades something making non sense roms fail I think.
Not too sure exactly, but have read this somewhere and I'm in same position after taking JB 4.1 OTA before finding xda goodness.
Dacra said:
Have you taken the stock JB update?
That upgrades something making non sense roms fail I think.
Not too sure exactly, but have read this somewhere and I'm in same position after taking JB 4.1 OTA before finding xda goodness.
Click to expand...
Click to collapse
Even if you've taken the 4.1 ota it will boot just no working touchscreen. Op is doing something wrong. Verify that you have a onexl and are flashing a ROM for the one xl then make sure to wipe cache, dalvik, system and do a factory reset in twrp. If you wipe system and are flashing a ROM for the wrong phone you will brick so make sure you have the right ROM and phone combo. After flashing the ROM boot to fastboot and fastboot flash your boot.IMG. if you do all that your ROM will boot.
Sent from my One X using xda app-developers app
Wait so you flash a ROM first , then flash the boot.img ?
Sent from my HTC One X using xda app-developers app
Doesnt matter if you flash it before or after ...are you full wiping? Data system caches. .. and you're flashing thorugh Fastboot right Sith Fastboot flash boot boot.img ?
Yes. Well mostly to flash the flash boot img . I was using the flash image gui app , or the flash boot .img batchfile created here on xda. They both have worked in the past .
Sent from my HTC One X using xda app-developers app
Any ideas anyone? I just tried flashing nocturnal and my phone's just sitting at the boot logo. I've flashed the boot.img and yes my phone is a oneXL.
Similar problem
I've been having a similar problem but maybe even worse. After rooting my phone via onexroot.com tutorial I havent been able to install any custom roms. It says that the MD5 file is not found and "completes" the installation very quickly. I have tried the viper rom but i have tried the CM10 and AOKP JB. I have flashed boot.img via fastboot every time to no avail. Help please.I have ATT One X 2.20 hboot 1.14 twrp 2.4.1.0. Thanks.
alemcc said:
I've been having a similar problem but maybe even worse. After rooting my phone via onexroot.com tutorial I havent been able to install any custom roms. It says that the MD5 file is not found and "completes" the installation very quickly. I have tried the viper rom but i have tried the CM10 and AOKP JB. I have flashed boot.img via fastboot every time to no avail. Help please.I have ATT One X 2.20 hboot 1.14 twrp 2.4.1.0. Thanks.
Click to expand...
Click to collapse
I know this may sound silly but are you leaving the boot image in the zip file that you are placing in recovery? Extract the boot image from the zip but leave it in the zip file you are placing in twrp.
AT&T HTC OneX
Android 4.1.1
ViperXL
No silly qurstions at this point
Venomtester said:
I know this may sound silly but are you leaving the boot image in the zip file that you are placing in recovery? Extract the boot image from the zip but leave it in the zip file you are placing in twrp.
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Yep, I just extract and copy the boot image over to user/downloads/onexrootattnew folder. Im starting to think that I did something wrong when rootin. I followed a tutorial online step by step and have twrp working and have superuser access. I'm not sure what else I'm doing wrong.
alemcc said:
Yep, I just extract and copy the boot image over to user/downloads/onexrootattnew folder. Im starting to think that I did something wrong when rootin. I followed a tutorial online step by step and have twrp working and have superuser access. I'm not sure what else I'm doing wrong.
Click to expand...
Click to collapse
Place boot image on phone but not in any folder so that GUI can see it not in one x root. Place full zip file in downloads folder on phone storage. Use GUI to flash image. After flashing it will go into recovery. Use TWRP to install zip. Make sure you wipe system, cache and davlik cache before installing zip.
Hope this helps.
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
Place boot image on phone but not in any folder so that GUI can see it not in one x root. Place full zip file in downloads folder on phone storage. Use GUI to flash image. After flashing it will go into recovery. Use TWRP to install zip. Make sure you wipe system, cache and davlik cache before installing zip.
Hope this helps.
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Yes it's very annoying and I can't get on any AOSP Roms or anything. I'm on viper 3.2.3 hopefully you can get on a sense based Rom that will work
Sent from my HTC One X using xda app-developers app
Sent from my HTC One X using xda app-developers app
marquavious said:
Yes it's very annoying and I can't get on any AOSP Roms or anything. I'm on viper 3.2.3 hopefully you can get on a sense based Rom that will work
Sent from my HTC One X using xda app-developers app
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Try watching a few Zedomax or Nocturnal TV Videos on youtube. Get away from onexroot videos if they are not working for you.
AT&T HTC OneX
Android 4.1.1
ViperXL
Sorry I'm still learning: what do u mean by use GUI to flash image. I've been fastbooting it via cmd on windows.
It's an application you can install on your phone that does the flashboot part for you. Search for " fash image gui apk " on here .
Sent from my HTC One X using xda app-developers app
alemcc said:
Sorry I'm still learning: what do u mean by use GUI to flash image. I've been fastbooting it via cmd on windows.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2155132
AT&T HTC OneX
Android 4.1.1
ViperXL
So I downloaded the flash GUI program and followed the steps via the video (thanks for that, very helpful) but after flashing the kernel (boot IMG) and hitting the recovery reboot option it didn't reboot, it didn't do anything. So I did a manual reboot into recovery and installed the zips and rebooted. I got to the Rom initiating page (this one had a unicorn) and it didn't go any further. The only other info I could offer is that I went the lazy way and emailed the boot image to myself on my comp and downloaded to my phone via the email. Not sure if that makes a difference. Any more ideas, I'm gonna try the ice cold jelly Rom and the viper xl later today.
So I just tried the viper 3.2 Rom and although it seemed to get a little further in the process, result is the same: stuck on viper logo. Only ice cold jelly left. When transferring zip files over to phone do o have to mount via twrp or can I just mount as disk drive via stock rom? At this point, unrooting and waiting for att's official JB update may be my only option. Thanks in advance for any help.
FatToad release thread and build/development discussion
What this is: This is an Unofficial CyanogenMod based image for the Samsung Galaxy S Relay 4G (apexqtmo) by TeamApexQ.
Latest released version: FatToad-5.0.2_0001
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/FatToad-5.0.2_0001-apexqtmo.zip
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/FatToad-5.0.2_0001-apexqtmo.zip.md5sum -- md5
Use the latest officially released CWM recovery -- https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexq_recovery-10.2-347.zip
Compatible gapps - https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
**FLASH THIS ONLY WITH CWM** -- Wifi will NOT WORK if you flash from TWRP.
ignore any warning at the end of the installation about /data already being mounted.
Great! Thanks for your work...testing
As more bugs are discovered, worked on, fixed and what have you, I will endeavor to update the OP, keep an eye on this space.
Would it be helpful for testers to report bugs here?
Flashing with CWM 6.0.1.2 fails with error
set_metadata_recursive: some changes failed (Status 7)
Click to expand...
Click to collapse
After some Googling it looks like I need to update my CWM, gonna try that next. Glad I did a backup.
Edit:
After CWM update it flashes correctly!
wedg11383 said:
Would it be helpful for testers to report bugs here?
Click to expand...
Click to collapse
I suppose it would, especially if not currently on the list in the OP. Although, keep in mind that the team is not yet ready to go into full support mode for these builds yet. This is just a preview of what we are working on.
user032 said:
After some Googling it looks like I need to update my CMW, gonna try that next. Glad I did a backup.
Click to expand...
Click to collapse
Yes. The one currently linked in the CM wiki, http://cmw.cmfs.me/apexqtmo/apexq_recovery-10.2.img works. You were trying it with the old CM 10.1 recovery. This is far too old.
Magamo said:
I suppose it would, especially if not currently on the list in the OP. Although, keep in mind that the team is not yet ready to go into full support mode for these builds yet. This is just a preview of what we are working on.
Yes. The one currently linked in the CM wiki, http://cmw.cmfs.me/apexqtmo/apexq_recovery-10.2.img works. You were trying it with the old CM 10.1 recovery. This is far too old.
Click to expand...
Click to collapse
If I flash from rom manager then I have also the latest recovery, right ?
couldn't restore my backup with recovery (maybe bad sd card issue).
edit: was a bad microsdcard !
robuser007 said:
If I flash from rom manager then I have also the latest recovery, right ?
couldn't restore my backup with recovery (maybe bad sd card issue).
Click to expand...
Click to collapse
Which recovery are you using? I do not know what version of recovery that ROM manager gets you. I've never used that. Please specifically flash a compatible recovery. Some time not long before the release of the recovery I linked, recovery could not access SD cards on the relay. The one linked is certified as compatible. If you're having trouble with your backup restore using that recovery, than it's likely a problem on your card or the backup set.
Magamo said:
Which recovery are you using? I do not know what version of recovery that ROM manager gets you. I've never used that. Please specifically flash a compatible recovery. Some time not long before the release of the recovery I linked, recovery could not access SD cards on the relay. The one linked is certified as compatible. If you're having trouble with your backup restore using that recovery, than it's likely a problem on your card or the backup set.
Click to expand...
Click to collapse
Thanks for the information, could you provide a zip file instead of a img for the recovery ?
robuser007 said:
Thanks for the information, could you provide a zip file instead of a img for the recovery ?
Click to expand...
Click to collapse
Actually, I can link to my personal one.
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexq_recovery-10.2-347.zip
Once you install it, remember to go into advanced, and reboot to recovery so that you're using the newer one rather than your older one.
Also, everyone, it's been pointed out that I'm an idiot. I was using a ParanoidAndroid Gapps package, that was deleting Gallery2, and replacing it with GoogleGallery. When using the correct Gallery app, video recording works fine.
Gapps: http://d-h.st/3k8
Is it worth to install on wife phone, also how stable is the camera,
Sent from my SGH-T989 using Tapatalk
alphaeagle777 said:
Is it worth to install on wife phone, also how stable is the camera,
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
It depends. Do you want to piss her off?
alphaeagle777 said:
Is it worth to install on wife phone, also how stable is the camera,
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I'll point out where I say in the subject of the OP, this is a Pre-Alpha, and later in the thread where I said that the team is not quite ready to be in full support mode for this version, this is a preview release. The camera though is quite stable, so long as you are using the certified gapps linked by Nardholio, and also linked in the OP.
Magamo said:
Actually, I can link to my personal one.
https://googledrive.com/host/0B-v962-Q8Pd9Q3F5Y1Z5Nm42c28/apexq_recovery-10.2-347.zip
Once you install it, remember to go into advanced, and reboot to recovery so that you're using the newer one rather than your older one.
Also, everyone, it's been pointed out that I'm an idiot. I was using a ParanoidAndroid Gapps package, that was deleting Gallery2, and replacing it with GoogleGallery. When using the correct Gallery app, video recording works fine.
Click to expand...
Click to collapse
Can't boot to recovery now, are you sure I can use that recovery while using cm10.2 ?
robuser007 said:
Can't boot to recovery now, are you sure I can use that recovery while using cm10.2 ?
Click to expand...
Click to collapse
The one I linked is a CM 10.2 recovery.
Magamo said:
The one I linked is a CM 10.2 recovery.
Click to expand...
Click to collapse
The recovery.zip doesn't work, tested it twice.
robuser007 said:
The recovery.zip doesn't work, tested it twice.
Click to expand...
Click to collapse
The recovery zip worked just fine for me.
Sent from my SGH-T699 using Tapatalk
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
I would recommend the one from ROM manager should be the same.
Sent from my SGH-T699 using Tapatalk
chris122380 said:
The recovery zip worked just fine for me.
Sent from my SGH-T699 using Tapatalk
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
I would recommend the one from ROM manager should be the same.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
The rommanager's one is 6.0.3.8, but can't mount the sdcard (need external mSD-reader).
Why doesn't it work on my phone ? Strange :s
robuser007 said:
The rommanager's one is 6.0.3.8, but can't mount the sdcard (need external mSD-reader).
Why doesn't it work on my phone ? Strange :s
Click to expand...
Click to collapse
It's been mounting my SD card just fine. Doesn't work 100‰ with ROM manager so I boot into recovery mode to do everything.
Sent from my SGH-T699 using Tapatalk
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Mods feel free to move if this is in the wrong section.
This is an unofficial build of TWRP RECOVERY built from the latest twrp sources
I just compiled this out and it fixes the new fstab layout starting from tonight's Cyanogenmod build
Credit: Mdmower --> https://github.com/mdmower/twrp/tree/twrp-2.7.0.8
Download: http://d-h.st/kgR
Note: If after installing the recovery, it will not pass the screen TWRP:
Restart and boot normally (system), then with any file manager to delete this "/sdcard/TWRP/.twrps
Click to expand...
Click to collapse
Sorry, this thread isn't pretty, but whatever
Mdmower also compiled his...didn't notice lol
feel free to take either one, won't hurt my feelings, as long as it gets the job done
http://mdmower.cmphys.com/download/267/?version=2.7.0.8
How did this recovery pan out? What's diff of this one and 2.7. Just wondering
Sent from my Desire HD using Tapatalk
chrisb906 said:
How did this recovery pan out? What's diff of this one and 2.7. Just wondering
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
CM is having a new fstab layout for a number of devices. One of these changes include a by-name partition support (instead of say mmcblk0p33 called as "system"). you need this recovery to flash CM from today, and probably all 4.4.2 ROMs soon
That's the major change...other than that: adb fixes (big issue for me while trying to pull kmesg logs for Sense 6 building :fingers-crossed, LED fixes, dual core support, fix of backup and restoration of encrypted backups
Is the mounting to pc issue solved?
Sent from my HTC One XL using xda premium
paras33 said:
Is the mounting to pc issue solved?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I haven't tried. I know adb works now though so I can guess that mass storage will too
Sent from my HTC One XL using Tapatalk
Tried flashing, then tried booting both versions directly from fastboot and neither will completely boot for me. All I get is a flashing TWRP splash.
jacobas92 said:
Tried flashing, then tried booting both versions directly from fastboot and neither will completely boot for me. All I get is a flashing TWRP splash.
Click to expand...
Click to collapse
Is anyone else having this issue? because its working for me fine. Maybe an ruu will fix it
Sent from my HTC One XL using Tapatalk
pandasa123 said:
Is anyone else having this issue? because its working for me fine. Maybe an ruu will fix it
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
I guess I could try that. I'm fairly certain I've got the latest firmware and hboot, but its worth a shot
Sent from my Wabbajack using Tapatalk Classic
jacobas92 said:
Tried flashing, then tried booting both versions directly from fastboot and neither will completely boot for me. All I get is a flashing TWRP splash.
Click to expand...
Click to collapse
I did what Jose mentioned in the Pacman Kitkat thread as the fix to this--"Note: If after installing the recovery, it will not pass the screen TWRP
Restart and boot normally (system), then with any file manager to delete this "/sdcard/TWRP/.twrps"
It worked for me, and I had the same flashing TWRP screen issue as you.
Rayvin56 said:
I did what Jose mentioned in the Pacman Kitkat thread as the fix to this--"Note: If after installing the recovery, it will not pass the screen TWRP
Restart and boot normally (system), then with any file manager to delete this "/sdcard/TWRP/.twrps"
It worked for me, and I had the same flashing TWRP screen issue as you.
Click to expand...
Click to collapse
Ahh. Thanks bud, I'll get right on that.
Mounting to PC is not working in this version of TWRP
sathish804 said:
Mounting to PC is not working in this version of TWRP
Click to expand...
Click to collapse
It is for me, you could try uninstalling the currently installed driver on windows and reinstall it.
jacobas92 said:
It is for me, you could try uninstalling the currently installed driver on windows and reinstall it.
Click to expand...
Click to collapse
I tried to uninstall and re-install the drivers but no luck for me to enable USB mounting in TWRP 2.7.0.8
I just flashed this via fastboot and when I go into recovery, it gets stock on the teamwin logo forever?? md5 checks out?
Lunatic00 said:
I just flashed this via fastboot and when I go into recovery, it gets stock on the teamwin logo forever?? md5 checks out?
Click to expand...
Click to collapse
Go back, one page.
I flashed this today and now my internal SD card doesn't mount. I'd be grateful for any assistance.
[email protected] said:
I flashed this today and now my internal SD card doesn't mount. I'd be grateful for any assistance.
Click to expand...
Click to collapse
All you needed to do was read the last few posts in this thread for suggestions on what to do.
Sent from my Evita
I flashed mine with Flash GUI Image. It worked flawlessly and TWRP is super smooth and stable. I couldn't use fastboot because my phone can't be recognized by my PC.
timmaaa said:
All you needed to do was read the last few posts in this thread for suggestions on what to do.
Sent from my Evita
Click to expand...
Click to collapse
I'm sorry timmaaa, I'm not sure what you mean. When I use a file explorer on my phone, it says my internal storage sd card is unmounted.