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!
Excuse the long thread title lol..
I've been gently lowering myself into all this tampering with my phone as I've always been a bit of a tinkerer with everything i've ever owned.
So back in march my phone, an unbranded handset on o2 uk was on 2.2.1. My first foray into modifying my handset was to flash the jvk gb firmware. I then rooted it using cf root. All very simple. I then flashed it using cwm with Simply honey 3.2 and then the latest 3.5. No issue.
So this afternoon, I flashed it with the "unspoken ones" kernel just cos I could lol. Something didnt seem right though. There was a bit of lag and I got one or two forced closures so I decided to restore one of the cwm backups I had. Thing is, it hung upon reboot at the i9000 screen, for about 10 minutes so I pulled the battery. Now I couldnt get it restarted. Panic set in. This was my first proper issue and I just wished I was back in march on 2.2.1 again.
As said, couldnt get it started so went hunting some advice. Install a base stock rom with 3 files and a 512 pit. I struggled. Could I find 3 files ? Nope. Not on samfirmware. Every file I downloaded was one file. JP1 JPU JPY. All 1 file. So. As JPY was the firmware I was on originally, I chose the 1 file version, put the phone in download mode and flashed it via odin. It worked !!! And then I plugged it into kies and up popped the box, I have an firmware update ! JPO GB! So i installed that. I'm quite surprised that I got the update because you always see lots of threads regarding people being unable to update by kies once they have modified their phones. Why did mine work? Because the handset in unbranded perhaps ?
Anyway, I wanted to get back to the Simply Honey rom because it ran really well and the battery life is fantastic but Simone hasnt done a version based on JVO yet as far as I could tell so I thought, I know, I'll root with cf root, again and try that backup again using cwm. And it worked, and here I am back where I was earlier today ! Ace ! lol
Sorry about the essay but I'm sure that there are some questions in there worth answering.. ?...and also to serve as a bit of help to those that find themselves in a dodgy situation. Just calm down, search for the advice, it is out there and do as it says and everything will be cool
Posted from my restored and working handset...
the files you download from samfirmware are rar files (have a .rar extention). This means you need to decompress them into a folder and the "three files" will be in there. You need a rar extractor app. You can use 7-zip which is free.
You need odin (or ezodin or heimdal) to flash the stock rom but I am sure you know that already. There are a few guides around for all tools.
There is a lot of information here, especially in the "sticky" posts. If you feel like learning what you are doing rather than copy instructions (as I think you do), it may be a good idea to go through them.
Anyway you got your phone working in the end so that's good!
simple solution when an install hangs is only to reflash the kernel in odin: that restarts the phone.
cwm is not invincible and the restored rom is there but the phone hangs on the boot because of the kernel hiccup. Reflashing the kernel to the one you now want will allow the phone to boot and access the rom that matches -- you do have to ensure the recovery version rom and the kernel you are flashing are in sync.
Persist. You only really panic the first time this happens -- after that you know it is a possibility and how to fix it.
Worst case scenario: pull the battery, reinsert, go to download mode and reflash the kernel and base rom of your choice. At least now you have a clean phone!
Two things are important to remember: (1) always do a backup before installing a new rom or kernel and (2) use titanium backup for all applications -- easy to restore everything.
Also I find it easier to use google calender and my internet email as bases for dates, appointments and contacts -- that way if I loose everything on the phone I can quickly reload my data by sync with online accounts once I have the phone "rebuilt".
Just thought I'd put this out there if anyone had the problems I did and found the answer by putting together info in about 5 threads to get my fix.
Rooted, was running CM7 and then a few different mods Hydra, Asop, and others.
Upgraded my phone to the iPhone 4s, daughter wants my Hero instead of her LG optimus S.
Went to authorized reseller, got my new iPhone up and going, however the hero would not release the old info or take the new info in any updates. Sprint put the info up in the data stream, the reseller, (who has his EVO rooted) sent me home to restore my nandroid backup (which I did have - thanks to the 4 million posts telling me to save one)
Got home, copied the nandroid over to my SD card, and couldn't get it to load in recovery. hmmmmm
oh yea now I remember I got a new phone - insurance replacement a few months back and never did a new nandroid. uh oh
so did some search the forum and came up with this fix:
do a new backup in recovery
load the SD card up in the PC and open the folder - clockworkmod/backup/*year-date-time*
delete the contents in it
copy the .img files from the old nandroid file into the *year-date-time* folder
SD card back in phone - reboot to recovery
choose backup and recovery - recovery - *year-date-time*
reboot
everything restored to my pre-root settings
updated profile, prl, software, firmware, - privacy-restore factory settings,
reboot and new number pops up - everything is great - reboot to recovery (had to Vol down/pwr to get to hboot, then to recovery) new backup (deleted old)
Still very much a noob, thought Id share incase someone has the problem I did and cant find the answer.
Big thanks to all the developers and contributors on this site! keep it up
Sorry for my bad English...
I have a Ideos X5. It is rooted, and i have MIUI on it. I also have a backup of stock (2.2.1 B136) rom made with clockworkmod.
I want to put aurora ics on it, but the battery is always 0% and it doesn't connect to network. I have read about that problem and the solution was to get 2.3.5 official rom on it. I have tried many ways to do that but my phone just doesn't want to get into update mode, and I don't know how to update it any other way.
Hope you will be able to help me.
If I remember correctly this issue (0% battery) comes along with another problem - nulled imei. Check if you have this problem. Solution may be found at some threads. One I know is this but you must have a backup http://forum.xda-developers.com/showthread.php?t=1325036&highlight=imei
Regarding the update process try to go to CWM and make a restart from there using a sd card with the dload folder.
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