Database Develop

cyanogenmod 4.1.99 support line for installation issues

ok due to the massive number of people clogging the offical thread im starting this thread just to help some of our newer members get working. anyone with a proper working install can help as well. let the issues begin.

i have no data connection at all i have installed 1.6 from htc and then 4.1.99. I even went back and wiped and reinstalled both rebooted and still no connection (3g or 2g).
any ideas

when you signed into google did it work or say cant connect?

Ok here's a question. I was running 4.1.11 which was running fine. I downloaded the recovery image & flashed it thru the recovery console (home + power) and then tried to flash 4.1.99 & now when i try going into the recovery console, I get the Exclamation point with the phone on its side. If i let it power thru it loads up, but like its stock.
I even tried terminal emulation & can't even get the SU command to work.
Any suggestions besides, re-rooting?

This is what I did
Okay, let me start off by saying I have had none of the lag a lot of the people are reporting. So I figured I would post how I installed step by step just incase it helps someone.
Step 1: Download the HTC rom and Cyanogen rom.
Step 2: Reboot into recovery.
Step 3: Flash the HTC update from recovery and let it finish ( it will do the radio as well) the phone will reboot back into recovery by itself.
Step 4: Wipe.
Step 5: Flash the Cyanogen update.
Step 6: Enjoy.
Don't think it would make any diff but just incase, I came from JACxHEROSkiv2.2 and cm 1.4 recovery.
Hope this helps in any way.

yes the same thing happened to me. its very simple too. just fastboot cyanogens recovery.img
http://forum.xda-developers.com/showthread.php?p=3915123
heres fastboot stuff
http://forum.xda-developers.com/showthread.php?t=502010
then flash newest cyanogens like normal and wipe afterwards.

Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition

Every time I try updating to 4.1.99 It stays on the g1 screen.

persiansown said:
Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition
Click to expand...
Click to collapse
try wiping your ext3 however please note alot is going on first boot. i didnt have any issues with slow but i wiped my ext3 and data(wipe in recovery) slow downs are caused mostly by missing or incompatible issues. thats why wiping is recommended. try wiping ext3 and start from scratch. its worth it.

10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2

jeremycool said:
Every time I try updating to 4.1.99 It stays on the g1 screen.
Click to expand...
Click to collapse
did you flash the adp image first?

mormo said:
10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2
Click to expand...
Click to collapse
check your md5s on both and start from scratch.

Here's what I did:
1. Wipe.
2. Delete all your EXT partition stuff.
3. Reboot into recovery.
4. Flashed the HTC update from recovery. I did NOT reboot after this finished.
5. Flashed the Cyanogen update.
6. Rebooted and waited for the post flashing process to finish.
I had one single FC at the beginning but now it's all good.
If you are not clearing out your dalvik cache and all your other EXT stuff AND wiping, then it's only not working because you didn't do those things.

yes both ways work. however if you have issues try letting the radio install. ONLY if you have issues.

here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!

the reason some people have to let the radio flash is due to either a bad flash. corrupted install or some other reason. every new version come with a new radio and it will sometimes delete your recovery. this is because certain older setup are different and not very consistant. however things happen and some stuff gets messed up. every dream is the same and this software is the same. but you are the different part.

damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
wipe is to fix an issue with google apps. as well as if you had something before causing issues.

damngood98 said:
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Click to expand...
Click to collapse
Not sure if it is your only option, but it might help. And no you will not need to flash anything afterwards.

jokersax11 said:
wipe is to fix an issue with google apps. as well as if you had something before causing issues.
Click to expand...
Click to collapse
damn! gonna go bed and maybe pout for a bit tomorrow before i do another wipe. I hate wiping!
thanks for help joker!

damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
Look at it this way...
You moved into a new place and the last tenant was evicted. He left all his crap lying around (mostly trash and dirty laundry.)
Do you sweep the rooms and take out the trash and call it a day? Or do you clean the whole house first? Technically, taking the trash should be enough (laundry included) but you never know what else is hiding in the house (maybe he had a pet tarrantula and it's walking around unbeknown to you. Eventually, you'll run into it and force close yourself in shock.

[Q] SafeStrap not flashing roms correctly

So I've followed all the tutorials I could find. I've rooted, installed busybox (to make sure it really existed), installed safestrap (the official one from the blog) and can get into recovery just fine. I made sure I have the right phone version and I've never done any kind of bootstrap stuff on this phone before this.
However, when I switch to safe mode to try out some roms, it simply will not work. I've tried all three versions of Eclipse and one CM9 version, but once supposedly done flashing and told to reboot, it gets a blackscreen for a few seconds and restarts back to the dual-core pre-recovery screen. I've wiped, wiped, super wiped everything just like the various instructions tell me to, but nothing ever changes the blackscreen.
Switching it back to non-safe and rebooting works just fine, but I cannot get any custom safe-mode roms to boot up. Is there something else I should be doing that I missed?

I occasionally have issues with Safestrap when you choose to reboot, so I just power off and then power on - that always works. Initial boots do take some time, though more than a few minutes without animation is probably too much.
And, just to clarify, this is the Safestrap that I use: http://blog.hash-of-codes.com/downloads/safestrap/

But it's not that it takes time, it reboots the phone itself. It's not locking up like I've seen others say and requiring a battery pull. It just refuses to go on, instead more like a boot loop? But nothing appears to be going wrong and I can easily switch back to the base no-problem.
And yeah, that's the same one I'm using. Droid 3 v1.08 exactly from that site.
It's making me sad that I can't get this going
Edit: I went ahead and tried just powering it off, leaving it for a moment, and turning it back on. Still did the reboot thing

are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..

ovelayer said:
are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..
Click to expand...
Click to collapse
Yeah, tried both ways. Wipe data/factory and cache numerous times, install, nothing. Install then wipe, nothing. Wipe, install, wipe, nothing.
Is there an easy way to know for sure if it is even installing anything at all, like navigating to it using a root explorer?

Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: http://forum.xda-developers.com/showthread.php?t=1554916

doogald said:
Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: "no linkies for me"
Click to expand...
Click to collapse
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?

shinseitom said:
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?
Click to expand...
Click to collapse
wait a sec..
you unzipped them?
the zip files are not ment to be unzipped..
download the zip to your phone
go into safestrap and choose install zip then choose the zip
oh wait...duh you were just checking to see if they worked lol
use root explorer and navigate to system folder open the build.prop and see if there is a mention of the rom your trying to install..ie..version=mavrick or eclipse

I'm not finding any references to other roms anywhere in it. I did a search by eye, then a search for "version", "cm", and "mav" and didn't come up with anything relevant. Is that bad?

There are two other things that you can try, though I am not sure that they will help:
1. From non-safe, stock, run Safestrap and uninstall recovery. Restart to see that it does not intercept before the boot screen, then go back in and reinstall recovery from safestrap. Restart the phone to see if it is working. Then restart to Safestrap and try toggling safe mode and see if your flashes work.
2. One other thing to try (not sure if this will help, but...) is to (prior to flashing a ROM) go into the Mounts menu and format /system. Maybe the old system isn't being cleared out by the ROMs you are trying to flash? Then go install the zip, do a wipe data/factory reset and see if that works.

Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?

Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"

Droidlyen said:
Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?
Click to expand...
Click to collapse
Safestrap is supposed to allow you to install a rom onto a safe "partition" of sorts, though that's not really what's going on. Anyway, it doesn't touch your stock rom so if something fails (like my flashing attempts) you're not in trouble.
SteveHebe said:
Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"
Click to expand...
Click to collapse
Nah, I switch it every time. I'm not quite messing up that bad
Anyway, I might have to resort to bootstrap to see if that works. If not, well, I guess I'll be stuck on stock. Nothing so far mentioned in the thread has worked for me. Kinda sucks, since I have an Infuse that loves being flashed with anything I want to put on it without problems, unlike a friend's Infuse. Maybe its phone karma.

[Q] Problems with custom rom HTC one

I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?

There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.

iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...

Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.

iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.

Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?

Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.

bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.

[Q] Crash on "setting permissions"

Well guys... I'm afraid that I'm in big trouble at the moment.
Hopefully this might sound familiar and some smart guys can help me out.
This afternoon I flashed the latest version of the Galaxy Project ROM for the i9305. I came from v16.10, and some older version of Philz Recovery. Flashed everything with the Aroma installer, without any troubles, and it worked. During the installation process, I've selected to install the newest v6.48.4 of Philz.
After a few hours, I wanted to re-flash the rom again, because I didn't like the transparent theme. But.. whenever I flash it now, the process stops at "Setting permissions". Then the phone shuts down, and reboots into recovery. Tried with both Philz and CWM recovery, latest versions and slightly older. Don't know that the issue is, recovery problem?
With the new versions of these recoveries, there is no more " fix permissions" option, that would be my first idea.
I cannot restore my older back-up, which sucks. And I really don't want to perform a "clean install" with losing all my files, as I just came back from half a year in South Africa and all my photos are still on my internal SD
Hopefully someone can help me out
Regards
EDIT: Turns out that I got this issue also if I try to flash other roms.
If I flash a stock version of Android 4.3 via Odin, do I keep all my photos? Can anyone confirm this?

Odin shouldn't touch internal storage, unless you explicitly tell it to.

My 3T factory reset after flash super su

Hello !
At first I apologize for my English, I am French.
So i used the custom ROM Validus and this problem appears for every ROM. Like you know, when you root, you can't use snapchat and u need to login before you root your phone. So i installed Validus, i install all apps i need and login (included snapchat) but after that when i flash super su, my phone reset and i have a error message which flashes. In the message i have ".com.android" something and i'm obliged to shutdown the phone, reset the phone and re-install the ROM.
And this appears with all ROM (Tesla, Tuga etc...) and i don't know how can i use snapchat acutally.
I tried to disable super user in the app, doesnt work
I saw we can use xposed app but for 7.1.1, it's not possible actually
Any ideas ?
Thanks,

Snapchat discorvers root as it denies working on it. After flashing install snapchat and login. Then return to recovery and install SU afterwards. Possibly you have to use tools like RootCloak.

Inciter said:
Snapchat discorvers root as it denies working on it. After flashing install snapchat and login. Then return to recovery and install SU afterwards. Possibly you have to use tools like RootCloak.
Click to expand...
Click to collapse
It's what i tried to do (without RootCloak) and when i do that, i lost all my data (like i wipe all data when i try to install SU...) but RootCloak works for 7.1.1 ? Because i already tried to flash Xposed, doesnt work (error 1)

Try SUHide. Though the data wipe seems odd.

Inciter said:
Try SUHide. Though the data wipe seems odd.
Click to expand...
Click to collapse
I tried to flash suhide after flash ROM, doesnt work, the ROM don't charge (the loading of the ROM don't stop)
PS : I tried with Validus ROM and others, same things

Here's a workaround for Nexus 6. Maybe it's working on 3T as well. Something else I found here.
Nevertheless, the auto data wipe is strange. Did you clean or dirty flash?

Inciter said:
Here's a workaround for Nexus 6. Maybe it's working on 3T as well. Something else I found here.
Nevertheless, the auto data wipe is strange. Did you clean or dirty flash?
Click to expand...
Click to collapse
I don't know what is dirty flash ? What i know is i alway wipe all data before install any custom ROM
But I found a solution. I installed Root Swich, it's a simple app which allows to deactivate the root and activate it as you want.
So i disabled root and install snapchat and login successfully.
But i want to understand why when i want to flash super su for any custom ROM i have a auto data wipe :/

Since your device is beyond my reach I can't help investigating the problem. Maybe the data is not really deleted but r/w permissions have just been modified and cannot be accessed any more. But anyway, I'm glad your found a workaround.

Inciter said:
Since your device is beyond my reach I can't help investigating the problem. Maybe the data is not really deleted but r/w permissions have just been modified and cannot be accessed any more. But anyway, I'm glad your found a workaround.
Click to expand...
Click to collapse
Thanks for your help anyway !
Now I just need someone who knows how can i fix the problem of data. Cause if one day i will need to flash something, it's gonna wipe the data of my phone
Maybe if i do a clean factory reset or something ? Cause i used my 3T a lot cause of this to find a solution so maybe something happenned when i tried so many things. (Test of ROM etc ...)

I have more information, when I install any custom ROM and after that I want to flash super su, wipe cache etc ... I boot on the ROM normally but i see my phone haved a factory reset and i have this ".com.android.phone has stopped" Impossible to remove the message and I am forced to wipe again data and reinstalll the ROM.
Conclusion : I can install ROM but after that, i can not do anything, if i do anything, BOUM, reset factory. And i don't understand why ....
I tried the last (Unofficial) TWRP but when i tried to boot on the ROM after flashing it, my phone didn't boot on the ROM but always on TWRP.
Maybe I brick my phone but i can use it, i don't have storage problem or others so ...
I'm lost ... Any ideas ?

up ?

Balashe said:
up ?
Click to expand...
Click to collapse
Do you have this issue with only flashing super su or try to boot into recovery don't do anything and reboot check if it still reset everything.
Which recovery you are using?
The version

nitinvaid said:
Do you have this issue with only flashing super su or try to boot into recovery don't do anything and reboot check if it still reset everything.
Which recovery you are using?
The version
Click to expand...
Click to collapse
I have this issue only flashing super su, when i try to boot into recovery and then reboot into the ROM, nothing happened.
I use 3.0.3.1, when i tried 3.0.4.0 and flash a ROM, the phone only boot on recovery and not into the ROM

I'm actually having a similar issue. One day my phone was acting weird and I had to force reboot. I noticed after that I lost root. I've tried flashing SuperSU again, and it flashes fine but I still don't get root. This morning I upgraded to 4.0.3, and tried flashing root, and same thing no root.
The weirdest part is I can flash a custom kernel with TWRP 3.0.3.1 and the kernel flashes fine and I have the custom kernel, if I try flashing SuperSU, it flashes fine but I get no root AND it removes the custom kernel!!! Everything I'm using is the most updated too. What gives? I want root back....