Related
I have flashed my Hero with many ROMS, mostly the Cyanogen nightly's. I have seen recently a huge lag no matter which build I use. I think there may be a corrupt file left behind that is causing the problems.
How can I erase everything and start completely from scratch? I have already done a wipse and re-imaged from there and it doesn't seem to help.
Run the officail RUU, then re-root again. that is all you need to do.
Sent from my HERO200 using XDA App
fowen said:
I have already done a wipse and re-imaged from there and it doesn't seem to help.
Click to expand...
Click to collapse
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
ranger61878 said:
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
Click to expand...
Click to collapse
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
If you are using the Amon Recovery v1.5.2, it does actually wipe everything even thought it gives you that 'run via adb' nonsense. It's just a small error/bug in that version of recovery that doesn't output the correct string of text, but the wiping part does work correctly and it does actually wipe Dalvik, data, ext, etc. even though the output tells you something else.
As said above, you need to wipe ALL of those (except battery) every time you flash a new ROM, or else it can lead to some corruption like you are experiencing. If still unsatisfied or if you still can't get things to work, then rerun the official RUU as also suggested above to start fresh. But I will tell you that I've never had to rerun the RUU before in the entire 6 months I've been rooted, so I think your problem is maybe just incorrect procedure between wiping and flashing ROMs. All phones are different though. Good luck, and please keep posting so we can continue to help you out.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
What recovery are you using? Anyways, the RUU wipes everything, no need to wipe beforehand, see this to RUU
I haven't flashed many types of ROM's, only a few. I have been sticking with Cyanogen Mod I would say 90% of the time. I cleared out everything and it didn't seem to help much.
Most of the time it lags when I am dealing with email, or a email comes in. Last week I got tired of it and OC'd it up to 768 and I saw a huge difference but my battery died after 6 hours. Even with the CPU clocked to 768 I can notice a huge difference when I have a email coming in.
I just flashed to Cyanogen's newest nightly to see if there are any differences. If not, I will try to un-root and flash directly to Cyanogen's rom. Will I need to clear everything before going to a new rom from stock?
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
fowen said:
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
Click to expand...
Click to collapse
Assuming you mean going back to pre-root, right out of the box state...you need to run the official RUU from your computer, not via recovery.
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
fowen said:
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
Click to expand...
Click to collapse
You are using HTC Sync and have the USB drivers installed?
----------
Sent from the XDA App on my FroYoed Sprint Hero...so forgive my inevitable typos
Sounds like a driver issue. Also make sure you have USB debugging on, otherwise adb will not recognize your device.
I've run across issues with loose fragments of data being left after a wipe via recovery. My favorite was the home key ceasing to work. A full wipe via fastboot always seems to do the trick. Just make sure you have a copy of your recovery image to reflash when done. You'll need the ENG SPL as well.
You'll do this all via adb.
In bootloader:
fastboot erase system -w
fastboot erase boot
fastboot boot your_recovery_image.img
adb shell mount /sdcard
adb push your_recovery_image.img /sdcard/your_recovery_image.img
adb shell flash_image recovery /sdcard/your_recovery_image.img
adb shell reboot
Just make sure your recovery image is on the root of your sdcard. Full wipe in minutes without that long ruu process! I've been doing this every time I flash a new ROM lately, never an issue.
Please read this post in its entirety before downloading and flashing.
THIS IS FOR I9020T ONLY! IF YOU DECIDE TO GET BRAVE AND TRY THIS ON AN I9020A, I9023 OR D720, MAY THE FORCE BE WITH YOU. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO ANY PHONE BY USING THIS ROM.
YOU MUST FLASH THIS ROM USING CLOCKWORKMOD RECOVERY. THIS WILL NOT FLASH USING THE STOCK ANDROID 3E RECOVERY AS THE ZIP FILE IS NOT SIGNED. I HAVE NOT TESTED IT ON OTHER RECOVERIES.
This is probably more for posterity now than anything else, however I have created a CWM-flashable full on ROM for the Nexus S Gingerbread firmware, version 2.3.2, build GRH78C. This is built exactly the same way that the full OTA ROM packages for 2.3.3 and 2.3.4 were built.
Some notes:
1. Flashing this ZIP will remove ClockworkMod Recovery on first boot. Android 2.3.2 contains a script that automatically overwrites alternate recoveries with the stock Android 3e recovery each time you reboot your phone. The script is located in /system/etc/install-recovery.sh. If you root the ROM, you can rename this file to avoid flashing the stock recovery on each reboot.
2. Flashing this ZIP will overwrite your bootloader and radio, restoring them to I9020XXJK1 and I9020XXJK8 respectively. These are the versions that came stock with GRH78C.
3. GRH78C is receiving OTA updates. As of this writing, the latest version of Android is 2.3.4, and Google is pushing an OTA update for 2.3.2 to 2.3.4.
4. This ZIP will NOT clear your user data or cache. For users running a stock ROM, I would highly suggest clearing your data and cache manually as sometimes downgrading without clearing data and cache can cause problems. If you are coming from a non-stock ROM, you are required to clear your data and cache or the ROM will not boot.
5. Since writing NFC tags wasn't introduced until GRI40/2.3.3, the Tags app is read-only.
6. There is no video chatting through Google Talk. This feature was not introduced until GRJ22/2.3.4.
Instructions:
1. Download the Stock GRH78C ROM package here.
2. Copy it to the root of your USB storage.
3. Reboot into ClockworkMod Recovery (or flash it).
4. Select "Install ZIP From SD Card"
5. Select "Choose ZIP"
6. Find the ZIP file and select it.
7. Wait for it to finish.
8. Wipe data and cache (optional but HIGHLY recommended for stock ROM users and REQUIRED for non-stock ROM users)
9. Reboot and have fun.
Reserved...just in case.
Thank You will post results if needed,i doubt it,again thank you very much,ping33tx
I can access the bootloader, I can access the clockwordrecovery, odin recognizes the device, but I can not access the intern sd.
I can only try to restore by odin
I'm looking rom to use the odin.
My nexus s is bricked, anyone help-me
I'm Brazilian and I used google translate, sorry.
i was googling for stock roms and found this
i had no idea if i have the i9020t or not
now my phone wont even turn on, no life
any ideas?
*EDITED: not sure which version i do have actually
SS2006 said:
this rom was bad...i was googling for stock roms and found this
i have the i9020t
now my phone wont even turn on, no life
any ideas?
Click to expand...
Click to collapse
Wanted to flash this ROM, just wanted you to confirm that yours is an i9020A, not i9020T, therefore that's the reason why it won't turn on now.
Sorry for your phone by the way.
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Can you boot it to bootloader?
From off position, try Vol UP + Power.
If you can see the Android logo and 4 menu options, you got yourself a great deal.
SS2006 said:
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Click to expand...
Click to collapse
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
al_madd said:
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
Click to expand...
Click to collapse
He doesn't need to. If he can get to the bootloader, he can flash and boot a recovery via fastboot.
No guys, seems i got myself in a mess. It is indeed a i9020a (the info under battery was erased so i didnt know0 and i flashed the i9020t rom in this thread (different radios)
so this thing is HARD bricked, screen won't turn on, no bootloader, nothing, tried to get it into download mode (even without screen turning on) assuming it was working, but odin doesn't realize its there
so i think my only solution is jtag. I can buy a usb jig but I think that usb jigs dont do anything for hard bricked phones, am i right
Much thanks for your help.
Hey Guys,
Before i start let me explain that i use to cook roms for my magic, so i know what im doing with this stuff.
Anywho i have been having a weird issue where whenever i flash a rom, it will not boot to either the rom or back into the recovery. my only option is to relock the bootloader and flash back to the stock ruu, and reinstall recovery.. right now im stuck on the stock rom and i hate it!
btw the device is s-off and unlocked bootloader, so wth, if anyone has any advice please let me know!
Did you try reflashing the recovery? Or a different recovery ? had a problem once with my pc antivirus blocking certain files and was causing the zip to be corrupted , just some thoughts
shael said:
Hey Guys,
whenever i flash a rom, it will not boot to either the rom or back into the recovery.
Click to expand...
Click to collapse
All you get is the white HTC screen when you reboot?
What about when you boot into HBOOT, then choose recovery manually?
As you mentioned, you're used to this stuff, so this part probably isnt helpful - do you do the 4 wipes when flashing? (data/cache/dalvik/system?)
I wonder if (even though you are S-OFF), the kernel portion of the rom isnt flashing? This can cause your phone not to boot and just sit there... i.e. your phone hasn't experienced a stockish/insecure kernel flash first, so recovery is having trouble flashing the custom recovery that comes with the rom.
See this thread for more info (it helped another user):
http://forum.xda-developers.com/showthread.php?p=30658376#post30658376
Also - to what Bigtjmc is saying - in the link above, I mention the recovery I use (which has not let me down at all!) Maybe you want to try it (if you're not using it already?)
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
Try Wildchild's Recovery (by far MY most favorite)
And if it's not passing verificiation, like the other user said check your anti-virus and check the MD5 Checksum to make sure you have a complete good download, wipe all data cache and blah blah blah then with fastboot "fastboot flash boot <Insert kernel file name here>.img
hmm, well in the past ive always flashed kernel with fastboot... its almost like my chip timed out and wont let me flash the kernel anymore :s
If recovery is crashing you might need to relock the bl and run the stock ics ruu to get you back up and running then try n start over , I used the tool kit just this morning for the same troubles and got back where I wanted to be in just a few minutes .
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
This happened to me as well... can't remember what script it was that was running but there is a script that is associated with a rom (vague I know) that is messing up the cache partition. If I remember correctly I also might be associated to the recovery you are using... but I can't remember. Anyway, If you do a fastboot erase cache command from the bootloader and re-flash the recovery of your choice you should be back to normal.
Awesome, thanks for you help guys, unfortunatley i dont have easy access to a pc, so i gotta wait a bit before i can try this... thanks again though
OMG!!!!! you guys are simply amazing, thank you everyone for your help! wiping the cache from fastboot, then flashing stockish kernel, then flashing cwm recovery, then wiping cache, and factory reset, then flashing my rom worked!!! <3
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
[email protected] said:
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
Click to expand...
Click to collapse
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
kessaras said:
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
Click to expand...
Click to collapse
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
[email protected] said:
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
Click to expand...
Click to collapse
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
kessaras said:
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
Click to expand...
Click to collapse
I did wipe the data and cache after installing the custom ROM. But the result is the same; No WiFi response.
However, I always copy my custom ROMs by mounting my phone through USB to my Win8 laptop, and then copy the ROM file through windows explorer. And then install the ROM from the CWN recovery. Thus do not use ADB for copying files, or installing custom ROM as mentioned above. If this is the main issue reason, then advice.
Also I haven't tried TWRP till yet. Will do now. Till then, what else I can do.
Thanks for the quick replies.
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
format system also, when installing a new rom, not just data, cache & dalvik
kessaras said:
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
Click to expand...
Click to collapse
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
[email protected] said:
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
Click to expand...
Click to collapse
Now, I have repeated using CWM 6.0.4.5 and TWRP, and no breakthrough .... Starting to lose hope ... Help !!!
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
kessaras said:
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
Click to expand...
Click to collapse
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
[email protected] said:
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
Click to expand...
Click to collapse
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
kessaras said:
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
Click to expand...
Click to collapse
YES. When I flashed stock V20A, I never had issues with Wifi. Its when I install custom ROM, and any custom ROM.
So I suppose, either there is something wrong in my installing method, or in my stock ROM that won't allow WiFi to work on any custom ROM. But how much influential will be the stock ROM if it is being replaced by a custom ROM?
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums. But I will do that now, and let you know the results shortly.
Thanks again for the replies.
[email protected] said:
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums.
Click to expand...
Click to collapse
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
kessaras said:
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
Click to expand...
Click to collapse
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
you dont need to copy it . u can open adb sideload from recovery and on pc use command : adb sideload [path/filename of rom.zip]
SimonTS said:
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
Click to expand...
Click to collapse
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
[email protected] said:
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
Click to expand...
Click to collapse
AT LAST .... FIXED ...
I did two things, V20B, and format /system, /data before installing new ROM. So my steps were:
1) Flush V20B instead of V20A
2) After rooting, and installed CWM 6044 touch, copy custom ROM MIUI to external SDCARD
3) Reboot into recovery, and format /system, /data, and /cache partitions
4) Install custom ROM from external SDCARD
5) Wipe data and cache
6) Reboot into the new world
:good: formatting did the work sorry i didnt think of it earlier.
So, I've just unlocked the bootloader on my Z1. Followed the instructions on the Sony website and it went off without a hitch. I then followed the instructions on the Cyanogenmod website to install the boot.img from the ROM file. This also seemed to to proceed without issue and I was able to boot the phone into recovery mode.
Unfortunately it all went wrong from here as whenever I install a ROM, I can't seem to get the phone to boot up, it hangs at the boot animation. I've tried various different ROMs and they all do the same thing. I've tried installing various stock ROMs and flashing the FTF file but that doesn't work either. I've even tried restoring it using the PC Companion software but it won't do anything because it says the software is modified and won't update it.
I don't suppose anyone would have any ideas? Perhaps someone with a more technical knowledge of such things?
What program are you using to flash the FTF files?
Are you using the ones for your model?
Did you buy your phone used or was it new?
Try this to get CM on the Z1
There is no official stable build on the CM website.
Also, if you flash other ROMS whilst you have a CM kernel, you will get a bootloop unless the Roms are based on that kernel.
Follow the links in the thread I gave you to download a CM11 build (Android 4.4) and then you can just flash the update.zip in recovery.
Job done.
Seems odd, that even flashing FTF files didn't help... Weird stuff.
Try flashing Cyanogenmod again, but performing full data wipe.
Does the cm boot animation hang and like not move or just spin forever and is actually moving?
Poesini said:
What program are you using to flash the FTF files?
Are you using the ones for your model?
Did you buy your phone used or was it new?
Click to expand...
Click to collapse
I bought it brand new, was using Flashtool. I was using the correct ones for my model (C6903).
gregbradley said:
Try this to get CM on the Z1
There is no official stable build on the CM website.
Also, if you flash other ROMS whilst you have a CM kernel, you will get a bootloop unless the Roms are based on that kernel.
Follow the links in the thread I gave you to download a CM11 build (Android 4.4) and then you can just flash the update.zip in recovery.
Job done.
Click to expand...
Click to collapse
Think I've already tried that, but I'll give it another try.
SquiffyGrain6 said:
Seems odd, that even flashing FTF files didn't help... Weird stuff.
Try flashing Cyanogenmod again, but performing full data wipe.
Does the cm boot animation hang and like not move or just spin forever and is actually moving?
Click to expand...
Click to collapse
CM and some other ROMs don't hang, it just carries on animating indefinitely.
I have noticed that recovery seems to have some issues though. When I do a wipe on CWM, it says "error mounting \data" and something else as well.
You can try manually flashing /data
Do you know how to install TWRP recovery?
I remember writing a guide of formatting the partitions manually (adb shell) via mkfs.f2fs (in that case, f2fs), but it can be done the same way with mkfs.ext4
If you have problems with /data partition you definitely should wipe it. As suggested above, the manual method might work the best for you, and it is as follows:
Boot into recovery and make sure you have adb working and your computer recognizes your device. Then use this commands, pressing enter at the end of each line. I remember using them myself, so this should work:
adb shell
recovery --wipe_data
Notice double - in the second line. Write precisely as above and after that reboot. With a little bit of luck your phone will boot into Cyanogen.
If that method doesn't work (I really don't know, but I'm sure this would work better), try this one:
http://forum.xda-developers.com/showpost.php?p=51517202&postcount=542
And change every part that says f2fs to ext4, so it gets like this:
Go to recovery (TWRP) and then go to command input:
cd /dev/block/platform/msm_sdcc.1/by-name/
mkfs.ext4 -l cache cache
mkfs.ext4 -l data userdata
mkfs.ext4 -l system system
Now set in advanced settings to "rm -rf instead of wipe" and then wipe data and internal storage