Related
i was on Calkulin's_EViO_2_ROM_v1.8 and i rebooted to recovery to restore back to cm7 rc4 but it gives me error error while flashing image. so i try to wipe and reinstall another rom and works but it still stuck in htc logo.
Are you performing a full wipe, factory/data, cache, and dalvik?
yes i performing full wipe and everything im uisng clockworkmod recovery 3.0.0.5. did those and install a rom but still stuck in logo screen and i cant restore i made few backup and none them work!?
Have you tried going into the bootloader, select clear storage [factory reset], then flash the rom? Also are you flashing a kernel?
im just flashing regular rom on using clockworkmod. ived done this flashing roms many times and never happen like this before.
Well at this point, it seems like your old backup may be corrupted. Make a new backup, and then try to restore it.
how i do backup when i already delet wipe already so i jsut need to install another rom and do backup and restore it?
culua said:
how i do backup when i already delet wipe already so i jsut need to install another rom and do backup and restore it?
Click to expand...
Click to collapse
Correct, make a backup of your current, flash a new rom, then try and restore.
ok i install Calkulin's_EViO_2_ROM_v1.8 agian backup and try restore but it gives me boot image error same thing.
i had a similar issue. my phone wouldnt even boot past the splash screen but i was able to correct that by flashing the stock evo ruu in hboot from my sd card then reflashing a custom rom over that. im not sure if you have to re-root but in my case i had to run unrevoked again. i had to reflash at least 4 times before my issue resolved but havent had any issues since
can you show me the steps and what i need?
1. Go into recovery, select backup, backup current rom
2. Wipe factory/data, cache, dalvik cache under advanced
3. Flash a new rom, let it boot up, go back to recovery, backup that rom
4. Restore previous backup just made
You can install the official RUU upddate from sprint then download the newest HTC SYNC to your computer then plug in the phone thru the usb and run the RUU file as if you are running an app. Remember this will delete everything includidn your root but you can easily re-root with unrevoked. Hope that helps? I had that problem on my incredible and I did this and it fixed it.
Sent from my ADR6300 using XDA Premium App
teh roxxorz said:
1. Go into recovery, select backup, backup current rom
2. Wipe factory/data, cache, dalvik cache under advanced
3. Flash a new rom, let it boot up, go back to recovery, backup that rom
4. Restore previous backup just made
Click to expand...
Click to collapse
when i try wipe this thing showed up saying E: unknown volume for path [sd-ext]
culua said:
when i try wipe this thing showed up saying E: unknown volume for path [sd-ext]
Click to expand...
Click to collapse
That's a separate partition, that is okay, since you don't have it, no ened to worry about it.
teh roxxorz said:
That's a separate partition, that is okay, since you don't have it, no ened to worry about it.
Click to expand...
Click to collapse
i did follow you steps and did restore i keep getting the error image.
pena020563 said:
You can install the official RUU upddate from sprint then download the newest HTC SYNC to your computer then plug in the phone thru the usb and run the RUU file as if you are running an app. Remember this will delete everything includidn your root but you can easily re-root with unrevoked. Hope that helps? I had that problem on my incredible and I did this and it fixed it.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
to unroot do i need 2.2 version to unroot?
If you're on hboot 2.10, you'll need a 3.70 ruu.
im sorry please show me how to unroot my phone since i cant boot up im on bootloader.
Use Sprint Lovers ROM the PC36IMG.zip version put on root of sdcard go into bootloader, update, reboot there you go. No re-root needed. I ALWAYS keep this on my sdcard root just in case. Trust me it saved my EVO more than once. You will lose everything but better lost info than lost phone. Try RA Recovery...better than any IMHO
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
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot
LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky
I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using Tapatalk 2
I recently tried installing probam rom v4.4.9 from xda threads and followed all the instructions. everything worked fine up until the thread said to reboot the phone once more, anyway long story short i rebooted it and it was stuck at the galaxy note 2 logo (white letters black background) it was stuck like this for around 5-10mins at which point i pulled the battery and decided to go back to using rootbox rom.
Is their anyway i can install probam rom without this happening again?
I've also tried downloading and installing probam version 4.5.0 from their own website following the instructions given on xda, but once its booted from twrp it'll work until i have to reset, at which point i am back to square one, being stuck at the galaxy note 2 logo.
I have also tried installing pacman rom because i would like to use a 4.3 rom but the same thing happens, the rom will work fine until i have to reboot or it randomly reboots and gets stuck at the note 2 logo.
the only roms i am able to use without this happening are moon rom v10, rootbox rom and carbon rom, only thing is i would like to use different roms and check out their features, but i am somewhat limited to what i can use due to the above problem. Does anyone else have this issue? If so how did you get past it?
Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app
Machiel187 said:
Haven't had the problem myself. Did you also format the system partition and not just wipe it? Wipe the data partition?
Perhaps you can try installing a stock firmware through Odin, reinstall your recovery. That might clean some thing up that keep you from booting in probam rom.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
through twrp i went to wipe, format data typed yes, after this i swiped to factory reset then advanced wiped clicking cache, dalvik cache and system, if i've done this wrong could you please tell me how to do it the right way as i'm not really sure how to, thanks in advance :highfive:
i did what you told me to and flashed a stock rom through odin, went through the whole rooting process and flashed probam 4.5.0 again and this time it worked!! But no signal at all
Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!
acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk
It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D
wipe Dalvik and Cache before trying the rom again. If