Hello XDA, i have samsung galaxy note 2
ive used android revolution HD 4.0 before, and now im flashing android revolution HD 4.1 (updated 14th november)
the problem is , it doesnt show any progress while installing busybox, stucking at 0,00%, but the loading bar is running,
the process is about 20 minutes till now,
i already buckup my system data and wiping
somebody please help me ?
weby91 said:
Hello XDA, i have samsung galaxy note 2
ive used android revolution HD 4.0 before, and now im flashing android revolution HD 4.1 (updated 14th november)
the problem is , it doesnt show any progress while installing busybox, stucking at 0,00%, but the loading bar is running,
the process is about 20 minutes till now,
i already buckup my system data and wiping
somebody please help me ?
Click to expand...
Click to collapse
-- SOLVED --
I took off the battery and put it on again, so i redo the flashing step, and now its working
i dont know what is wrong
weby91 said:
Hello XDA, i have samsung galaxy note 2
ive used android revolution HD 4.0 before, and now im flashing android revolution HD 4.1 (updated 14th november)
the problem is , it doesnt show any progress while installing busybox, stucking at 0,00%, but the loading bar is running,
the process is about 20 minutes till now,
i already buckup my system data and wiping
somebody please help me ?
Click to expand...
Click to collapse
Don't be scared,just press volume up,power and home button at the same time to go to clockworkmod and wipe cache and dalvik cache then flash rom again, it happen to me 1 time with wanamlite 1.5.
Related
I flashed RCMix HD v5.1 Last night and everything was ok. Today I saw that RCMix HD v5.2 came out and I tried to flash this Rom, However everytime I got to boot, I get to the Screen Lock which I scroll down and it stays on the "HTC Logo". Any ideas what I can do to fix this?
Fixed, I just installed RCmix DH again. However all my contacts are screwed and it bugs out when trying to click on them and asks me to force close? Any Ideas how to fix this?
Yes wipe all and install again.
Go to the ROM thread and check the advices of the dev when upgrading from 5.1 to 5.2 (maybe he asked to do a full wipe first)
Hi
2 days ago i upgraded my htc desire to cyanogenmod 7.0.2.1 using the Rom manager
every thing was ok except the market which started rebooted it is one and twice then worked fine just for browsing and i can't download ,upgrade & even delete my apps .
i decided to downgrade the device again to cyanogenmod 7.0.0 but it's still there .
i did a full wipe and repartition the sd card and flash a new rom ( Oxygen v2.0.3 )
but it's still there !
update : i tried to downland an app over the 3g and it works !
what is wrong with the WiFi
any help
A.M.S said:
Hi
2 days ago i upgraded my htc desire to cyanogenmod 7.0.2.1 using the Rom manager
every thing was ok except the market which started rebooted it is one and twice then worked fine just for browsing and i can't download ,upgrade & even delete my apps .
i decided to downgrade the device again to cyanogenmod 7.0.0 but it's still there .
i did a full wipe and repartition the sd card and flash a new rom ( Oxygen v2.0.3 )
but it's still there !
update : i tried to downland an app over the 3g and it works !
what is wrong with the WiFi
any help
Click to expand...
Click to collapse
try upgrading radio or at least loading ril which is for your current radio.
where can i find a good one ?
what about this 32.56.00.32U_5.17.05.08
update : i just flashed this ( http://forum.xda-developers.com/showthread.php?t=971904 )and still getting the same issue ( market doesn't work ) and the 3g is not working as well
pleaaaaaaaaaaaaaaaaaaaase help me
Hi there,
I have a Samsung Galaxy Nexus (GSM) with Jelly bean from here, and franco.Kernal nightly r240, with 384Mhz GPU. I auto-flashed it, and it got stuck on "Android is upgrading - starting apps". I've cleaned the cache and fixed permissions and it boots once but the next time I try to start it, it gets stuck again on "Android is upgrading - starting apps". I've tried installing it with CWM Recovery but it makes no difference. So do I have to clean the cache everytime I want to boot, or how do I resolve this problem? Reflashing the ROM would be my last resort.
Any help would be much appreciated.
I've re-installed my ROM without wipeing data - everything is fine with stock. Then when I flash franco.Kernal through ClockWorkMod Recovery it boots! ... but not the second time. I cleaned my cache and fixed permissions and now I'm back to step one. I'll stick with stock kernal or an old version.
Yharooer said:
I've re-installed my ROM without wipeing data - everything is fine with stock. Then when I flash franco.Kernal through ClockWorkMod Recovery it boots! ... but not the second time. I cleaned my cache and fixed permissions and now I'm back to step one. I'll stick with stock kernal or an old version.
Click to expand...
Click to collapse
hi, i am having issue also with this. have Kernal nightly r240, with 384Mhz GPU in Xenon HD v8 JB. upon reboot I get stuck. my fix is to remove battery and reboot again without any problems. I have not encountered this with other kernels. Will try to flash the rom again and wipe everything and see if the problem persist.
update; just downloaded newly realeased r241 franco kernel. No more stuck at "upgrading android".
mrm43 said:
update; just downloaded newly realeased r241 franco kernel. No more stuck at "upgrading android".
Click to expand...
Click to collapse
Same here. Thanks for the fix Franco.
For it worked the opposite
I installed r240 when it became available and had no problems with being stuck on "starting apps...", but today I installed r241 and discovered that audio jack for headphones is not functioning - if I plug in headphones or car aux it continue using built in speaker. Restarted the phone to recovery, cleaned cache and dalvik cache and upon restart I was stuck in "starting apps..." screen. Removed battery and phone booted ok, but audio jack still didn't work, so I returned back to r240 and now I can use headphones
Stuck at Android is updating starting apps .
Hi there ! How to solve this problem my phone stuck at android is upgrading starting apps after i select recovery from Rom Manager anyone can help me with this issue ? Thank You in advance
:crying::crying::crying::crying:
My phone is HTC One M9 Sprint. Today i download Android Revolution HD 14 (http://forum.xda-developers.com/devdb/project/?id=8972#reviews) to flash.
Before flash my phone on android 5.1 (1.32.651.30) (http://forum.xda-developers.com/devdb/project/?id=8972#reviews)
After flash to Android Revolution HD 14, i got problem. My Phone keeps rebooting and optimizing apps, it will say Android is Starting... Optimizing app # of #
One month ago, i tried to update to 2.11.651.19 but still got the same problem:crying::crying:
NOTE: Before flash, i wiped :silly:
Pls help me. Sorry for bad english
Anyone there
i still can not use my phone. I have a new method is flash the previous ROM but i wanna use this ROm
Hi, I am a noob in flashing ROMs and stuff...
I recently got a Galaxy S9(used) by a family member. It had One UI 2.5, android 10 on it but I missed a couple of Android 11 features that I had on my Galaxy A50
So I decided to get Lineage OS 18.1. I flashed it successfully. When I launched Samsung Wearable app, it said that I had modified the software in "Unauthorized way". So I searched and found that Noble ROM is based on One UI 3.1 so I tried to flash it. I got stuck in a bootloop at first but then flashed again and after some time it booted up in setup screen like select language, etc. then at the data transfer part, the phone screen went black except the status bar, then it lighted up the set up screen went black again, it kept on happening. I rebooted it, tried safemode and also tried factory reset in TWRP. Then the issue still occurs from time to time.
I am ready to go back to stock ROM or should I try flashing newer Noble ROM or something else, please suggest.
Please help me!
I used Odin3_v3.14.4 , twrp-3.5.0_9-1-starlte.img.tar and NOBLEROM1.1_N9_S9_S9P with CAMERAFIX_G960
I didn't install kernel fix as I followed this video .