Related
Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.
chaosthebomb said:
Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.
Click to expand...
Click to collapse
From my understanding, as I saw it, I believe that the RUU's are safe, since they're HTC approved images, just that the gold card allows you to revert to a lower version of an HTC rom. Think of it as the RUU's as an official update, but an older official update, and the gold cards make your phone seen as a phone that can accept any update (new or old). So there will not be any harm when you run an official update like this unless your computer crashes midupdate or you pull the battery..or the cable gets unplugged.
Nandroid backups can be produced using the recovery image (i call it a menu since that's all you really see from it), which is covered later in a tutorial if you're reading one. This recovery image is applied after a downgrade (the downgrade gives you the ability to have root access, which is i believe necessary to get the recovery image installed), and thus be able to make these nandroid backups. The nandroid backups then get saved onto the SD card to which you can transfer to your computer for safe keeping. This ensures you can revert to an official rom with previous settings applied in case of an awry custom rom installation. The nandroid backups can also be used for nonofficial roms that you've deemed stable when you tested them, and this can be done as many times as you want.
I'm not sure if I'm entirely right, but I believe I have the gist of it. If anyone can correct me for any errors or can elaborate more, please feel free to share After all, we're all new at one point, hopefully veterans of this will chime in and allow us all to learn!
Also, welcome to the forums! Glad to have you!!
alright, so if I understand correctly, I first need to root my phone to gain root access to perform these nandroid backups?
I'm using this guide" Get started rooting Telus HERO130! (No need for QMAT!)", I'd post a URL but it seems that since I am a new member I'm not allowed to post URL's. I've gotten up to step 6. When I run that RUU file it says its going to erase everything on the phone, so I decided its probably best if I backed up my phone before I try this in the event that I mess everything up horribly.
Is this possible without having root access to use the recovery image with nandroid on it? or am I just having another noob moment?
thanks for the help!
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
kabutar said:
Hello!
So, I've read through the beginner guides (and that is a hilarious video btw!) and just want to double check a few things. I'm on Fido (Canada) with a stock S4 (i337M) that I got a couple days ago.
1. I assume I use the instructions here: http://forum.xda-developers.com/showthread.php?t=2314494 [HOW-TO] and here http://forum.xda-developers.com/showthread.php?t=2298299 [Canadian Root and Recovery].
1a. That tool will allow me to un-root in case I need the warranty, yes?
2. I also want to flash to vanilla Android (aka Pure Google / Google Edition)... which ROM do I use? There are so many I can't tell.
2a. I know the Samsung camera app doesn't work on the Pure Google ROM, but is basic functionality still working, i.e. can I still take a picture / video / etc.? Is there any other basic functionality missing? (I heard something about the volume button?)
3. Which ROM do I use if I want to restore to factory?
4. I also need to backup my SMS, contacts, call log, app data, settings etc. so I can restore them easily after flashing to new ROM, or after restoring to factory ROM. Will Titanium handle all of this?
Thanks
Click to expand...
Click to collapse
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
CommentProvider said:
That guide should be fine. If you want "vanilla Android", right now the closest thing would be CM, you can get it from http://get.cm and select "jfltecan" (the canadian S4 model). Ye,s, Titanium can backup all of those things you mentioned, although I am not certain about system settings - there will be a lot of different settings between TouchWiz and AOSP.
Click to expand...
Click to collapse
awesome thanks. I'm not worried about system settings just apps and their settings.
for the factory ROM would this work?: http://forum.xda-developers.com/showthread.php?t=2261573 (again, I'm on Fido in Canada)
and lastly, I'm still not clear on the difference between Odin/Loki/whatever you use to root and/or flash - would someone be able to clarify?
Also, just to be clear, what is meant by 'recovery'?
Thanks again
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
mymusicathome said:
http://forum.xda-developers.com/showthread.php?p=41989987
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T).
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
Sent from my SGH-I747
Click to expand...
Click to collapse
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
kabutar said:
ok, great, thanks. just to clarify one last time: am I correct in understanding that I don't need to have a custom recovery in order to flash a ROM? or is that what installing clockwork mod/TWRP means? (or is that what rooting means?)
Lastly... is there somewhere with a list of what each custom ROM is, and/or what things don't work in the ROM? I do want vanilla, but I'd also be interested in checking out the other ROMs to see if there's one that will keep some TouchWiz functionality while removing the ridiculous skin.
Also, for vanilla Android, would you recommend waiting till devs release a MOD based off of the S4 GE?
Click to expand...
Click to collapse
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
mymusicathome said:
Check out the link in my first post. A plethora of knowledge that will help you in your Rom journey.
Play around and test the options of roms you have. Each user has different likes/dislikes. MAKE SURE YOU READ THE ORIGINAL POST OF THE ROM YOU ARE PLANNING ON FLASHING. They will contain the basic inductions to flash the Rom and usually any bugs that exist.
Check out this thread for a list of compatible roms -
http://forum.xda-developers.com/showthread.php?p=41834056
[GUIDE][NOOB'S]These non-AT&T ROMs work on AT&T/TMO/Canadian S4 devices. Here's how!
A quick search can be a beautiful thing
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Thanks again for the link! I have actually seen several of those... but am just still very confused. mainly on these points:
- FIDO's rom isn't in those lists, and the variety of options for flashing (e.g. some ROMs say they need to be flashed with ODIN not TWRP) is a bit overwhelming!
- there's a post saying the Canadian ROMs are for odin not recovery flashing?
- I'm still not clear on whether I need to install a custom kernel just to flash a different ROM
- Also not clear on how to restore to factory stock (to take it to store for example)
- In the link you sent, the OP said non-ATT people should use the versions in their own forums... but does this apply to Canadian users too or is this ok for them?
Feel free to tell me if I'm being really dumb, but I really am a little lost lol.
As for buggy ROMs... would it be better to wait for one based off the S4 Google Edition?
Thanks again
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
zild8 said:
Canadian dont need loki dont use loki never use loki
Take time to understand everithing before flashing
rodger is the same as fido exept for the rodger bloatware (my accout,visual voicemail etc)
what i did root with cf auto root
installed goomanager on google play ,this app can installed twrp and it really easy
in recovery i flash mint jelly rom ,after its done i flash faux kernel for canadian
To factory restore you have to installe stock rom thru odin ,(from what i understand) it change the rom and the kernel at the same time
Click to expand...
Click to collapse
ok, so I'm just sorting through all of this. Successfully rooted and flashed CM nightly. However, now I see 'rogers' instead of 'fido' and 4G in the status bar, which I understand means that I'm on LTE according to stock JB icons.
So to sort this out:
a) what do I do about this incorrect network name?
b) if I restore to stock rom through odin, and it installs the 'rogers' rom, how do I get back to the fido apps? will I still have the network access / wrong name problem?
c) if I want to go BACK to stock eventually, I seem to have two options:
http://forum.xda-developers.com/showthread.php?t=2261573 [FACTORY STOCK]
http://forum.xda-developers.com/showthread.php?t=2269304 [12 May Official STOCK firmware collections for Canadian S4]
which do I use?
d) I took a nandroid image, BUT: can I restore from this (after wiping all data) to get back to factory ROM, or MUST I use ODIN? Or, do I need to use ODIN and then nandroid to restore everything about the stock ROM?
Thanks!!
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
zild8 said:
A = I think cm have an option to rename carrier label if not you can install xposed framework and notach xposed and the go in frameword,module then activate nottach .open nottach then chose any option that you want ,over 100...
or i think you can try change your apn to show fido ( not sure)
B= check playstore for fido app
C= ? i dont know i think both of then are good, iwould use the one that say canadian stock firmware
D = if you restore from nandroid i think you flash counter gonna still show that you running cutom rom ,best way should be thru odin
Read a lot before you do anithing,you have to understand ..seem to be easy to brick .did not happen to me since one years ,but i read a lot..
And hit the thanks button when somebody helps you
Click to expand...
Click to collapse
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
kabutar said:
AWESOME, thanks for all that. Successfully flashed, so hopefully that's the end of it all. And thanks for pointing out the thanks button!!
Two LAST quick things:
- if I use the Canadian stock firmware, do I still end up with a wrong carrier name sign? I imagine I may need to ask the dev that, but just in case you happen to know. I actually can't seem to fix it using the methods you suggested, so I'd prefer not to have this happen.
- ok so I can flash with ODIN and then use nandroid to restore a snapshot of the filesystem I assume?
Click to expand...
Click to collapse
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
blyndfyre said:
-If you flash back to your stock carrier specific firmware with ODIN the carrier will be correct. You will be back to just as when you first got it from the dealer (provided they didn't set it up for you first).
-You shouldn't be able to restore the nandroid if you ODIN back to stock because you will no longer have a custom recovery.
Click to expand...
Click to collapse
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
kabutar said:
- Well the problem is that my carrier is Fido, a subsidiary of Rogers, and so CM only has a 'Rogers' release. Similarly there is only a 'Rogers' stock firmware, so I don't want to flash back to that and have the carrier still wrong...
- OK, well I assume I could root, flash nandroid, and then unroot - yes?
Thanks!
Click to expand...
Click to collapse
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
blyndfyre said:
-I see the dilema.
-Well as opposed to even flashing to stock with ODIN in the first place. I would suggest booting to recovery (TWRP or CWM), and restore your Nandroid backup. This should bring you to the point before you flashed any ROM. Keep in mind this won't however remove status showing 'custom'.
If you happened to already ODIN back to stock you would have to root again, install custom recovery and perform the step above.
Click to expand...
Click to collapse
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
kabutar said:
that is what I was thinking... there are ways to unroot as far as I know so hopefully that should be ok!
thankfully I did take a nandroid backup. speaking of which - I have 3 files, does this sound ok?:
- boot/sys/data (these were originally selected so just went with it)
- efs
- other (everything else)
last clarification: I thought nandroid was not recommended if switching between ROMs? like if I had a computer backup (i.e. nandroid) but took the backup in Windows XP (i.e. stock rom) and then tried to restore it over Windows 8 (i.e. CM rom), bad things would happen? or is the nandroid more like an acronis boot image thing where it completely wipes everything?
lastly, if I do that... do I need to wipe factory data, dalvik cache, etc or will nandroid take care of that for me?
many thanks again!
Click to expand...
Click to collapse
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
blyndfyre said:
I think when you go into recovery and restore nandroid everything will restore.
I would just restore the nandroid from your current state via recovery. If you are worried about it or it causes a problem, it isn't to many more steps to flash to stock via ODIN, root and install recovery and proceed with restore.
I think it is always safe practice to wipe first, and not to dirty flash.
Click to expand...
Click to collapse
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
kabutar said:
ok thanks.
However: I may be SAVED! I just realized that Fido is often tagged as FMC, and there's a stock firmware for that one in this thread. Thank the heavens!
Click to expand...
Click to collapse
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
blyndfyre said:
Didn't know that! Never been with Fido. Great news for you, all you have to do is ODIN that firmware
Click to expand...
Click to collapse
Yeah, very relieved, and now just gotta figure out why my phone is showing up as a Rogers phone when the nightly is tagged Rogers + Fido and I'll be good to go. I must say I miss multi-window a little and the handwaving over screen a lot, but by god TouchWiz was ugly.
hey kabutar
Yesterday i flash the 12 may stock firmware thru odin ,to revert backt to stock
Here what i did
-latest odin 3.07
-put your phone in download mode with usb not pluged to computer ...
-closed all kies software
-plug your phone in computer
add firmware on pda button ,dont touch any other option.
reboot i add a lot of crashing app so i went to recovery and errase data
reflash thru odin the stock firmware ,and boom everthing was stock ,no more custom in os or in download mode
Alcatel OT POP C7 (7041x) [BACKUPS/ROOT/CWM/TWRP/TOOLS/DRIVER] [STOCK & MIUI V5 ROMs]
Last Update: Mon. AUG-03-2015
Hello,
I had bricked my "just" 4 hours old C7 a week ago because i was stupid enough to delete the custpacks from root and /system folders without even making a backup.
I had not flashed CWM and only rooted the device with RomasterSu_2.1.4 (aka iROOT, some Chinese one-click root / KingUser app) and i could not revive the phone through MTK Tools, Mobile Upgrade S or adb shell (either device not recognized or it couldn't push files, giving errors).
Today i got a new one, and hell i have not made the same mistake again.
After i unboxed the phone i immediately went into stock recovery and made a backup!
Secondly, i rooted the phone with RomasterSu and installed Uncle MTK Tools and made a IMEI backup (Just incase).
And lastely, i flashed CWM through Uncle and made a Full Backup of the current rom.
For anyone who happens to play with a rooted C7 on stock rom and accidentally bricked it, i will provide my Stock and CWM Backup Recovery's for anyone to use.
note: If you already flashed a custom recovery onto your device (e.g; CWM), the stock backup becomes obsolete! Use CWM instead.
[INFO]
Model: Alcatel One Touch 7041x
Firmware: 4.2.2
Baseband: MOLY.WR8.W1315.MD.WG.MP.V7
Kernel: 3.4.5
Build: 01003
Stock Recovery (Data) Backup (.backup):
- userdata_20100101_000117.backup (.rar / 83MB)
Place Stock Backup (Unpacked) into the root folder of your sdcard.
Reboot phone, Vol+&Power into stock recovery and select "restore user data" (or something alike) and select the .backup file.
New googledrive uploads:
-MIUI V5 (4.8.29) ROM (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
-SP Flash Tools (.rar)
If you're familiar with flashing, i'd guess installing these files and how to use them propertly are self explainatory.
If not, you can ask me how to write a proper guide...
==============================================================================================================
--UPDATE--
I provided a stock rom and a MiUI V5 rom for people who don't want or prefer to use backup's. A custom Recovery is needed and will not work with stock recovery.
This is a vanila stock rom without the custpack games/apps bloatware. IIRC this rom is already rooted, but if not, you can always use iROOT.
Bare in mind that it's based on the first TCT Firmware build 01001 and not the latest Firmware Upgrade 01003.
The MiUI V5 rom is based on miui 4.8.29 (Jellybean 4.2).
Also, the installers are in Spanish and you can only select a handfull system languages for both roms, but atleast you can use these roms in English.
Both roms work absolutely fine, and faster than stock with custpack bloatware.
Stock (01001) ROM:
https://drive.google.com/file/d/0B_pc8K917q22RlJWNllGV2JLOVE/view?pli=1***
MIUI V5 (4.8.29) ROM:
http://www.mediafire.com/download/9l49h7gisxslx2s/Miui+v5+spanish.Alcatel+7041x.zip***
---UPDATE--- [AUG-03-2015]
KitKat 4.4.x Alcatel C7 (7041x):https://translate.googleusercontent...2.html&usg=ALkJrhh-v6soAAT7XuUrpiK_zGh5bODHaA***
*** I have not uploaded these ROMs, nor am i responsible for any damages or errors that might occur during flash, use at own risk and always make a backup first!
Making any custom changes to your device will void your warranty!
Bump Update!
Added files to google drive;
-MIUI V5 ROM (4.8.29) (.zip)
-RootMaster / iRoot & SU (.apk)
-Uncle MTK Tools (.apk)
-CWM & TWRP Recovery (.img)
-Mobile Upgrade S (.exe)
-One Touch Center (.exe)
-USB Drivers (.rar)
-MTK DroidTools (Windows) (.zip)
- SP Flash Tools (.rar)
https://drive.google.com/folderview?id=0B52SB5R_clyUVTNwVHlwMHpCZWM&usp=sharing
S5 7041X Rom
http://www.htcmania.com/showthread.php?t=976259
How to install stock ROM with Mobile Upgrade S,when installed custom CWM?How back to stock CWM?Mobile Upgrade S does not recognize the phone with custom CWM.Phone must be flashed with SP Flash Tool.After this,Mobile Upgrade S,recognizes phone.
_jussyy said:
http://www.htcmania.com/showthread.php?t=976259
Click to expand...
Click to collapse
Nice ROM,but it kills the battery.
mugy said:
Nice ROM,but it kills the battery.
Click to expand...
Click to collapse
Most roms need some time to settle, after 1 or 2 complete charges your battery should behave normally.
You can also use the 'Greenify' (Permit SU access) to blacklist any app that uses wakelocks or running backround processes.
This will save you some battery...
My best bet is going for the MiUiv5, which always ran fine when i used to own the C7. Never had any issues with that ROM other than a occasional 'SystemUi stopped working' when trying to use the Rom's OTA.
I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?
erdemdengel said:
I installed CWM 5.5.0.4 but cannot see internal storage
Do you have any idea?
Click to expand...
Click to collapse
A bit late but that's because I don't own the C7 anymore and hardly pay attention to these threads anymore, I'm sorry...
I have no idea why it would'nt show up in CWM. I always use TWRP on any device that has it's compatibility over CWM, mainly because of it's touch functions and ext partitioning functions. Normally your internal storage is sdcard0 and your SD is sdcard1, select "mount/unmount" to see whether it's listed or not (I guess you already did that obviously but still....) It should be listed, if not, reflash CWM (try latest available for the tct/alcatel, i don't know which build number out top of my head, or TWRP.
I suggest to switch to TWRP and most likely your problem will be solved.
I don't know where you got your recovery files, but the ones I got in my googledrive are guaranteed working since I tried them both before uploading, if you used my CWM try to reflash it with MobileUncle MTK Tools, but than again pick TWRP instead .
Sent from my ACER LIQUID Z500 using XDA Free mobile app
Bump Update
Sent from my HTC One using XDA Free mobile app
I tried to use both the CWM and TWRP recoveries and neither worked. When it tries to boot into them it just glitches out the boot screen and resets. I flashed them with Flashify if that's a problem. My tablets model is a P310A. So this is the right thread for it right?
It does the same thing when I flash with Uncle MTK Tools.
Update: So it seems that you need to use this recovery if you have a P310A. Sorry for the pointless bump.
White sreen when flashed
After I flash my phone I get white screen logo whitescreen logo etc.
I have the alcatel 7041x
Alcatel one touch pop C7 ,Dutch
It functional in 7040e?
Not reading us b
I can't download backup file
@dragonivell
No! 7041x only. If it would, i would've stated it at the "device compatibility list" (which doesn't exist in this topic, for that reason!)
@pricklain
I'm sorry, somehow the file got removed from my gdrive. Since I don't own this particular device anymore, i cannot re-upload the file in question.
Also, i'm unable to edit the OP for some reason, so i understand any complains about the backup file(s).
Note: I am hardly online on xda these days, so forgive me if my response is a bit late...
@jachthond
Heb je wat meer details wat er niet lukt met flashen, en welke files je daarvoor gebruikt hebt? Mischien kan ik je er door heen loodsen.
Nobody has to Alcatel One Touch Fierce 7024w ?
links please
Ebom
Because this thread was the first one I completly read and looked at many time again, I post my results in short here.
Its posible to "flash" or "download" the KitKat rom from Hungary (or whereever the rom came from) onto a stock Alcatel OT POP C7 (7041X). Note the X, I have only that phone so, find another thread or user if you dont have a x (the kitkat rom is from/for a 7041D, so maybe your in luck too if you have the D version)
https://forum.xda-developers.com/alcatel-pop-c7/help/alcatel-one-touch-pop-c7-kitkat-twrp-t3438624 this other thread has the working rom, tools, and scatter file.
I could write a tutorial, but i based my carefull work on that thread and the links he provided. I also watched the youtube video even tho I dont understand a word thats being said.
Basicly NEVER EVER overwrite or format the phone completly or do sh1t with the preloader. mobile_info we leave alone aswell and we dont like to touch NVRAM aswell. They kinda contain imortant stuff
Basicly i made backups of everything I could or wanted (some thread said "Readback" the preloader can break alcatel phones, Ive succesfully read my whole phone back, but NEVER tried "downloading" or flashing preloader, cause i dont want a brick.) so I have everything saved and i could compare my files against any other rom that ppl uploaded.
KitKat rom from that thread I linked you to, get it, just all of it just in case. then if you compare them using CRC/SHA1 or MD5 against your dumps. hopefully like me, MBR, EBR1 and EBR2 are all the same compared to the kitkat one. so i took the liberty of not flashing them.
left us to do the: UBOOT(lk.bin in my backups), BOOTIMG, RECOVERY, SEC_RO, LOGO, CUSTPACK, ANDROID.
I noticed diferences in the logo, recovery and sec_ro, so I followed the tutorial/video on "downloading" those onto my phone... real simple...
I now have KitKat on my 7041x
Phone calls itself a 7041D now and Gyroscope sensor is not working
simple fix for the phone name is in the build.prop file, either google how to edit that (using root, or adb tricks) or do as I tricked, changed the file inside custpack.img using an hexeditor (HxD is my favorite). When you find a 7041D, replace with X. I suggest you use your brain and computer skills to deduce how to "replace" a character instead of inserting seems to start at offset 0x03356000 (http://www-ccpp.tcl-ta.com/files/ALCATEL_ONE_TOUCH_7041X_KK.xml does excist, so it suggest an official rom either was made or support added anyway).
I replaced budhapest with amsterdam and could change the dualsim to false and compensating the file size change by removing some 0x00 after the file.. but felt it was too risky and only tried the D into X wich was succesfull. ill check if I can find the AcceleroMeter/Gyro? module or fix.
If anyone has a question, sure ask me. but the rom is there, make backups before ANYTHING, and never full format or touch the preloader. ive read it might be able to fix using some Jtag method, but I cant remember the thread and this is quite the old phone by now. if ever, ill try a newer rom, but probably have to make it myself. another kitkat rom Ive found wasnt clean but this one was like it was a OTA, the phone migrated the 58 apps, and all my settings where still there, whatsapp worked right away without trouble and I can now play Pokemon GO (the x version has the 1gig ram )
Bedank @JMailuhu for making this thread and pointing and warning people. within 1 week of fixing this free phone Ive updated to kitkat. Now ill try fixing the accelerometer problem and maybe try other roms (ow well, kitkat does work fine) no root or custom recovery sofar
TLDR: Have a cookie, sorry I talk too much. much better than "ROM NOW" comments
Hi guys,
I need your help because I'm a complete newbie in this field. 2 yrs ago I rooted my HTC 816 with CWM and unlocked the bootloader (my current system is 4.4.2, htc sense 6.0, ver. 1.60.401.1, htc sdk api 6.21, cwm-based recovery v6.0.4.7) ). I would like to upgrade my system but cant do it without unrooting the device. Unfortunately I dont know how to, coz the option with fastboot doesnt work. I can only manually get to hboot option. Can you guys plz tell me what to do to get to factory settings and be able to upgrade my software the official way? Thanks in advance for a "for dummies" explanation. Best regards!
luq4 said:
Hi guys,
I need your help because I'm a complete newbie in this field. 2 yrs ago I rooted my HTC 816 with CWM and unlocked the bootloader (my current system is 4.4.2, htc sense 6.0, ver. 1.60.401.1, htc sdk api 6.21, cwm-based recovery v6.0.4.7) ). I would like to upgrade my system but cant do it without unrooting the device. Unfortunately I dont know how to, coz the option with fastboot doesnt work. I can only manually get to hboot option. Can you guys plz tell me what to do to get to factory settings and be able to upgrade my software the official way? Thanks in advance for a "for dummies" explanation. Best regards!
Click to expand...
Click to collapse
If your version is the single sim a5_ul version( verify in your bootloader or in about phone in your settings first) here's a tutorial with links for restoring stock recovery and rom. Obviously your still on your stock rom so just unroot through your SuperSU or Superuser apps settings then flash back your stock recovery over your custom recovery. Relock your bootloader then upgrade your stock rom through OTA . You can't flash a higher rom from this tutorial without your phone having S off. Just unroot then flash back your stock recovery , lock bootloader then do OTA update. Good luck.
http://forum.xda-developers.com/showpost.php?p=65155555
thanks a lot for a quick response, my version is a5_ul with S-ON so i will try the procedure You gave me and inform soon
ADB doesnt see my device <i downloaded sdk manager, updated, also htc sync manager>; i also tried to do it directly from FASTBOOT USB option in my bootloader but also no effect <neither can see it>; should I try the step 3.b then? I'm not sure coz I never had lollipop on my htc
luq4 said:
ADB doesnt see my device <i downloaded sdk manager, updated, also htc sync manager>; i also tried to do it directly from FASTBOOT USB option in my bootloader but also no effect <neither can see it>; should I try the step 3.b then? I'm not sure coz I never had lollipop on my htc
Click to expand...
Click to collapse
Do you have USB debugging ticked on in your phone's developers settings?
Do you have Java on your computer?
Either of these 2 things could be the reason it's not recognizing your phone because it should be able to.
---------- Post added at 08:15 PM ---------- Previous post was at 07:58 PM ----------
luq4 said:
ADB doesnt see my device <i downloaded sdk manager, updated, also htc sync manager>; i also tried to do it directly from FASTBOOT USB option in my bootloader but also no effect <neither can see it>; should I try the step 3.b then? I'm not sure coz I never had lollipop on my htc
Click to expand...
Click to collapse
No don't try step 3b. You'll need to get your device recognized through ADB first but really you should unroot the phone first then get it recognized 2nd then flash back the stock recovery file from that tutorial then relock your bootloader and then you should be able to just update through your stock system or HTC sync manager. If that fails for whatever reason then and only then should you try to flash the stock image from this tutorial. First though you've got to get your device recognized or nothing is going to work so just keep trying on that front.
uffff, I finally managed to do this but it took me many hours Thanks a lot for your help!! It seems <although I aint sure> that the problem was with the java version installed on my notebook. I installed 64-bit and after removing it I installed 32 bit, reinstalled apk and htc drivers, and adb saw my device! I then used supersu to unroot, locked the bootloader and got stuck. But then I copied the zip file into my sd card <another problem was that - I dont know why - but I couldnt copy the 1.2 gb zip file into my sd card so I changed the extension to .txt, copied and changed back to .zip; another another problem was that the file downloaded from the above mentioned tutorial was corrupted. I tried 2 times but it didn't work so I googled another file with the same name and it worked>. All in all, now I have a stock android 6.0 and Im very glad. Thank you very much for your help once again, best regards!
luq4 said:
uffff, I finally managed to do this but it took me many hours Thanks a lot for your help!! It seems <although I aint sure> that the problem was with the java version installed on my notebook. I installed 64-bit and after removing it I installed 32 bit, reinstalled apk and htc drivers, and adb saw my device! I then used supersu to unroot, locked the bootloader and got stuck. But then I copied the zip file into my sd card <another problem was that - I dont know why - but I couldnt copy the 1.2 gb zip file into my sd card so I changed the extension to .txt, copied and changed back to .zip; another another problem was that the file downloaded from the above mentioned tutorial was corrupted. I tried 2 times but it didn't work so I googled another file with the same name and it worked>. All in all, now I have a stock android 6.0 and Im very glad. Thank you very much for your help once again, best regards!
Click to expand...
Click to collapse
Hi !
I'm needing to do the same ...
Can you please give me the link where you have downloaded the file ?
thx, and have a good day
Asardex
Not sure if anyone encountered this issue, but a few years ago, I bought the developer version of the Desire 626s directly from HTC (aka with a CID: BS_US001).
Something happened to the phone recently when I let my friend borrow it for development purposes, and he flashed the "Sprint debloated Marshmallow" rom that seems to be floating around. It turns out there wasn't a way to return it to the stock unbranded because all RUUs that are publicly available from HTC are for the branded version. (e.g., T-Mobile, MetroPCS, Sprint/Boost, etc.)
Just wanted to let the community know that if you do want the stock HTC firmware that is factory unbranded, or to use as a base for development, go ahead and google:
0PM9IMG_A32E_UL_L51_DESIRE_SENSE70_NA_Gen_Unlock_1.11.617.1_Radio_01.01_U113251011_32.04.50622G_2_release_446244_signed
It's a zip file (1,283,787 KB / 1.22GB) you can download. You can then rename it to 0PM9IMG.zip, place onto the root of your SD card, boot the Desire 626s into download mode (press and hold volume down when powering up), and flash directly within download mode (Vol up to initiate flash when in download mode)
I should note, this stock firmware is only available if you have CID: BS_US001, or if you have S-Off/SuperCID: 11111111 already. If there is any interest, I may consider just performing a TWRP backup of this image on my phone, and releasing it as a flash-able zip through TWRP Recovery. However, I'm pretty sure since this is such an old phone, there's really no need. Anyone that really wanted to do this probably is more technical and would have already just followed directions I noted above.
i would be greatly interested and apreciative if you could.I have four 626. one for each teenager.
Unable to flash
12 RU ZIP ERROR.
HTC_a32eul pvt s-off
Cid-111111111
mid-0PM912000
Primalmudcat said:
i would be greatly interested and apreciative if you could.I have four 626. one for each teenager.
Click to expand...
Click to collapse
https://super-firmware.com/index.php?a=browse&b=file&id=12649
See if that works for you.