Hi there, thanks a lot for paying attention to this thread
I have just recently pushed in a partition table 'Bravo CM7 r2' using fastboot and adb.
What i have done so far:
I wiped the cache and wiped data/factory reset after the partition table was done. Then i restored the backup i did before i updated the partition tables.
However, after booting up normally with no problems, the second i unlocked my device, things started to force close (keyboard, android.process and other things)
Desperate, i went back to recovery and i reflashed my ROM (cm7.1), then i wiped the cache and wiped data/factory reset and the same thing happened, i unlocked my device and everything just starts to force close again (refer to previous paragraph for force closed items)
I have no idea how to get this working, it appears it is not as easy as the tutorial says.
I need your assistance, thanks a lot guys!
What exactly did you do when you "unlocked your device"?
Sent from dGB using Transparent XDA App
Hi MatDrOiD, thanks for the prompt reply.
What do you mean by "What exactly did you do when you "unlocked your device"?
Btw, i forgotten to include some information about the device im using. Sorry about that.
Phone Model: HTC Desire (GSM)
ROM: CM7.1
S-OFF
Hi, can't anyone help a noob out?
Can't no one help me? Or am i required to start a new thread?
As far as I can tell, you're doing it wrong. Wipes are to be done before, not after the flash.
fastboot flash hboot cm7r2.img
fastboot reboot-bootloader
fastboot erase cache
Boot to recovery now.
mounts&storage
format system, data, sd-ext and cache (optional as you already wiped it but do so for the piece mind) and do so manually! Not just full wipe.
Now flash your new rom. In case you flashed something else, only one thing is supposed to be flashed per session unless said otherwise in the installation instructions!
If crashes continue, download the rom again.
Sent from my HTC Desire using Tapatalk
Hi, thanks for the reply! Am i supposed to restore my backup after im done flashing my ROM?
UPDATE: I did a restore and the situation looks a lot brighter, less force crashes. The only thing that FCs now is thememanager. Is there anything else i can do? Or should i raise a white flag and restart from scratch?
Why would you flash a new ROM if you can restore your nandroid backup of the previous rom?
But make sure your the /system-partition of the ROM you backed up is smaller than the one of your new hboot.
Hi, let me get a clearer picture of what im supposed to do
1) Push in the img for the partition using fastboot
2) Wipe system, cache, data, sd-ext
3) Restore backup (no need to flash new ROM here?)
In case this helps, i flashed ceberus and gapps for my backup. Would that affect the system partition?
First step: Make nandroid backup!!!
No, there isn't any need to flash rom.
Yes, it will effect it.
Haha! Nandroid Backup has already been made. But it is useless now because i flashed in ceberus isn't it? So the only thing i can do now is to make a backup of all my apps through Titanium backup and start anew?
Also, if i wanted ceberus to be inside, i would have to make a custom partition right?
Excuse me, but what is ceberus??
kassarin said:
I have just recently pushed in a partition table 'Bravo CM7 r2' using fastboot and adb. [...] Then i restored the backup i did before i updated the partition tables.
Click to expand...
Click to collapse
As MatDrOiD said earlier, make sure the ROM you're restoring is made for the CM7R2 partition table. The stock partition table has a 250 MB /system partition while CM7R2 has an 145 MB one. If you're trying to fit your 250 MB /system ROM into an 145 MB /system... there's your problem. So, what ROM were you using before flashing CM7R2?
Related
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.
eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?
teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!
I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.
Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.
SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu
Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk
I just successfully rooted my device w/Odin, then decided I wanted to start fresh. I used CWR to wipe my partitions, including the System partition. I take it that was incredibly stupid? I guess I'm so used to having a full .zip ROM package to flash with my old phones that I didn't stop to think about what I was doing.
Now I'm permanently stuck at the T-Mobile splashscreen. The progress bar fills, but the phone boots no further. Is there any existing way to restore the system partition to stock? I still have access to CWR and can still flash with Odin. I do see that there are .img dumps of the system partition; can I do anything with these? Thank you!
Have u tried to Odin back to stock?
Sent from my SGH-T989 using xda premium
Do you mean by flashing the ~10MB SGH-T989-Stock-UVKID tar file? If so, yes. The file successfully flashes in Odin, but it the phone still doesn't boot.
Is it at all possible that I need to reflash the system partition? I've downloaded a couple >300MB images of System, either as .img or .zip files. Can I do anything with these?
Then I have no idea sorry
Sent from my SGH-T989 using xda premium
sb61g2 said:
I just successfully rooted my device w/Odin, then decided I wanted to start fresh. I used CWR to wipe my partitions, including the System partition. I take it that was incredibly stupid? I guess I'm so used to having a full .zip ROM package to flash with my old phones that I didn't stop to think about what I was doing.
Now I'm permanently stuck at the T-Mobile splashscreen. The progress bar fills, but the phone boots no further. Is there any existing way to restore the system partition to stock? I still have access to CWR and can still flash with Odin. I do see that there are .img dumps of the system partition; can I do anything with these? Thank you!
Click to expand...
Click to collapse
Did you happen to make a NANDROID BACKUP prior to your formatting frenzy?
ALWAYS, ALWAYS, ALWAYS...you get the point yet? If someone else hasn't uploaded one, I'll post one when I get home in about 4 hours...
Well, thank you for trying. To reiterate my problem:
I have ClockworkMod Recovery installed and working. While in it I did the following, thinking this would cause the phone to reboot in a "factory fresh", but rooted state:
-wipe data/factory reset
-format /system
-format /emmc
-format /sdcard
-Wipe Dalvik Cache
I then rebooted, and thus cannot boot the phone. The progress bar fills on the Samsung/T-Mobile splashscreen and then just hangs. Could someone confirm for me that I caused this by formatting /system? If so, is there any way to copy the OS back over to the system partition?
Shamwow, that would be amazing. I did a Nandroid backup, then proceeded to format the microsd card on which it was stored. Chalk it up to pure, unadulterated stupidity.
Anyone willing and able to post their Nandroid backup?
I have installed MildWild CM-2.7 on my Desire but there is now MildWild CM-2.8 and I can't find a guide how to install/update my Desire.
I have got S-OFF and recovery by Revolutionary The guide I followed to S-OFF and ROOT
This is the ROM I using. MildWild CM ROM
Just flash it via recovery like you did with the previous version
Will flashing the new version cause me to loose everything on my current version I.e apps and data etc??
Thanks for the reply though
do back up first, wipe davik+cache and flash it... it should work if not do full wipe and restore back up
just post any result we will move from there
What should I use to hackup TIbackup? Or is there a better one that you reccomend?
Wh000sher
Titanium and recovery. All basic stuff. Have a,read of my rooting faq in my signature. Tells you everything you need to know
Sent from my HTC Desire using Tapatalk
rootSU said:
Titanium and recovery. All basic stuff. Have a,read of my rooting faq in my signature. Tells you everything you need to know
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Do I only restore the Titanium I am guessing, as restoring recovery would revert back to my current ROM? and I have thanks
Yes indeed. With titanium, only restore "missing apps with data".
Theres a guide Angusc wrote here:
http://forum.xda-developers.com/showthread.php?t=1480343
ROM Manager can make updating so much easier - well worth the investment.
JohnHarrisNZ said:
ROM Manager can make updating so much easier - well worth the investment.
Click to expand...
Click to collapse
I can't speak for other devices but for Desire, nope it's not worth the time and money.
kotag82 said:
do back up first, wipe davik+cache and flash it.
Click to expand...
Click to collapse
So I'm only wiping the davik cahce correct?
Not anything else or have I missed something?
Wh000sher said:
So I'm only wiping the davik cahce correct?
Not anything else or have I missed something?
Click to expand...
Click to collapse
Things I've learned with all this flashing that may be helpful for you.
1. Before flashing, always backup your current system up. nandbackup via recovery, titanium for your apps, sd card if really needed for that you need to do.
2. If flashing an updated version of same rom, wipe cache and dalvik only on your recovery (unless explicitly specified by dev to make a full wipe.)
3. If you are having weird issues after upgrading the same rom, do a full wipe and start fresh. If issue is not resolved, report the issue to the Dev's thread.
4. Do a Full Wipe on recovery (System/factory, cache, dalvik if coming from a different rom).
stankyou said:
Things I've learned with all this flashing that may be helpful for you.
1. Before flashing, always backup your current system up. nandbackup via recovery, titanium for your apps, sd card if really needed for that you need to do.
2. If flashing an updated version of same rom, wipe cache and dalvik only on your recovery (unless explicitly specified by dev to make a full wipe.)
3. If you are having weird issues after upgrading the same rom, do a full wipe and start fresh. If issue is not resolved, report the issue to the Dev's thread.
4. Do a Full Wipe on recovery (System/factory, cache, dalvik if coming from a different rom).
Click to expand...
Click to collapse
Thanks for the reply.
In response to 2. I am using ClockworkMod as my Recovery and I am guessing you mean I have to wipe 'cache partition' and 'wike dalvik cache' under advanced?
I am creating a guide to help fellow N00bs how to update a rom and change between ROM's
Wh000sher
Wh000sher said:
Thanks for the reply.
In response to 2. I am using ClockworkMod as my Recovery and I am guessing you mean I have to wipe 'cache partition' and 'wike dalvik cache' under advanced?
I am creating a guide to help fellow N00bs how to update a rom and change between ROM's
Wh000sher
Click to expand...
Click to collapse
Yes if I remember correctly there are the first three lines on that recovery is wipe system, cache partition (like you stated), and wipe dalvik. So if upgrading just wipe cache partition and dalvik cache.
System partition is where the "Android OS" resides. Wiping it is like formatting your computer. Most of the time, incremental updates of the same rom requires you to wipe just the cache partition and dalvik, otherwise if the rom update has a lot of changes, the dev might require you to wipe all three options on the recovery.
Having wiped my cache and dalvik cache. I am now wanting to install the new version. On the main screen I have 2 options which are tempting to click.
One is 'Apply update from SD card' and the other is 'Install zip from SD card'
I am unsure of which to choose but my gut instinct is to go with 'Install zip from SD card', is this correct or am i going to make a terrible mistake?
wh000sher
Install zip from SD
Hi folks,
I flashed the ICS 4.0.4 BCM RC3.2U1 ROM on my phone and I have now been waiting for first boot to complete for well over 90 minutes (animation looping continuously).
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
How long is the first boot supposed to take? Should I remove the battery and try flashing again?
HTC Desire
S-OFF
Radio 5.17.05.23
Stock hboot
Clockwordmod Recovery
Thanks.
thegreendroid said:
Hi folks,
I flashed the ICS 4.0.4 BCM RC3.2U1 ROM on my phone and I have now been waiting for first boot to complete for well over 90 minutes (animation looping continuously).
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
How long is the first boot supposed to take? Should I remove the battery and try flashing again?
HTC Desire
S-OFF
Radio 5.17.05.23
Stock hboot
Clockwordmod Recovery
Thanks.
Click to expand...
Click to collapse
It says about five mins
just be patient
I froze my self few days ago until I've red it in their thread
thegreendroid said:
animation looping continuously
Click to expand...
Click to collapse
this is known as a bootloop. whenever your phone does this for a long time, don't bother waiting for 90mins, it's not going to go anywhere. pull the battery.
thegreendroid said:
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
Click to expand...
Click to collapse
as a bare minimum you need to perform a full wipe before flashing a rom: 'wipe data/factory reset' option within recovery.
i don't think you have done this, therefore you have bits of old and new rom mixing up so it bootloops
eddiehk6 said:
this is known as a bootloop. whenever your phone does this for a long time, don't bother waiting for 90mins, it's not going to go anywhere. pull the battery.
as a bare minimum you need to perform a full wipe before flashing a rom: 'wipe data/factory reset' option within recovery.
i don't think you have done this, therefore you have bits of old and new rom mixing up so it bootloops
Click to expand...
Click to collapse
Aye, correct. Before you flash a new rom format boot, system, data, cache, dalvic and sd-ext (which you need if you want mounts2sd!!)
It also says on the BCM thread that at first it may take a while to boot, and 2nd time it will not boot at all, for which you press volume down, power and trackpad to restart the phone, and it will boot fine.
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
here's same as u!
thegreendroid said:
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
Click to expand...
Click to collapse
its not comin up..its an ics on htc desire, but its not working, i'd performed a factory full wipe, heading for another full wipe..hope it works,
but a question?! should i update the firmware when im coming from gingerbread rom (stock) to ics?
Hi,
can you load your old working rom ?
which one was it ?
thegreendroid said:
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
Click to expand...
Click to collapse
did u change the hboot to alpharevs data ++? The rom needs 180mb on the system partition.
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Try the cache clean up after the nandroid is restored.
Also try to install some other compatible kernel (if it's stock it should be also to find on the forums) after the restore with its modules if the cache clean up doesn't help.
Sent from my HTC One X using Tapatalk 2
Wipe the cache and dalvik cache again.
shadehh said:
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Click to expand...
Click to collapse
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Thanks for the help guys. I mentioned all the suggestions on this thread to him and it he was able to get it running
Sent from my HTC One X using xda app-developers app
bradmax57 said:
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Click to expand...
Click to collapse
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
squirrelbo1 said:
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
Click to expand...
Click to collapse
The file shouldn't be on the phone, but on the PC.
Place it in the folder in which you have your fastboot files.
oh of course. I'm being a moron again.
I cant believe I did that. so very very simple. sorry for being a numpty guys. wasn't thinking strait. Done a few custom rom installs but never flashed a backup. Didnt even think. You even have to type the directory into command prompt.sorry guys I can't believe I didn't think that. (was thinking along the lines of installing from zip way)
to be fair the only reason I'm doing all this is because my screen is playing up and I need to return it so getting everything as close to stock as possible so got other things on my mind
everything is working now. Thanks guys. My god stock rom on HTC one x from orange is ugly.
No worries mate. You're not a moron, just a beginner.
TToivanen said:
No worries mate. You're not a moron, just a beginner.
Click to expand...
Click to collapse
thanks heaps for the thread guys, this has been a great help as I'm doing a similar thing and had the same problem.