DEFY running on CM7 in Boot Loop - Defy General

Hi All,
I am noob. I recently flashed my stock froyo and rooted the phone and loaded CM7. It had bee working good till today. I think I messed with perfomance under Cyanogenmod settings.
When I got my phone rebooted, its stuck in the boot loop. First google with Motorola logo appears.Then CM7 skater board logo appears.Then phone vibrates.Again CM7 skaterboard logo appears.It goes on.I dont know what to do.Please help me out.

yep you definitely screwed up something! LOL
Im assuming you still have access to bootmenu, I would enter custom recovery (not stock recovery) and wipe the phone. If you are concerned about losing your data try wiping just the cache and dalvik cache. If that doesn't work then wipe data. If that doesn't work you will have to wipe data and reflash cm7. If that doesn't work you will have to start from scratch by wiping in stock recovery and using RSD to flash a froyo sbf.

@zyxwvut:Thanks buddy.
I didnt have access to the custom recovery. I flashed the froyo sbf.Now my defy boots into the stock froyo. I need to get back the cm7.
I rooted it. downloaded 2nd init.
But now when I am installing 2nd init recovery, the app is giving ('downloading files...will install after downloading) and it starts downloading(over wifi) but later the app is not responding and i have to close it again.
What should I do.I am not confident enough to use adb shell

I have a couple thoughts on this... One is that you should be sure usb debugging is enabled in order for this to install properly, I'm wondering if it is downloading but when it gets to the install it is failing because usb debugging is not enabled.
If all else fails you can install the old school tenfar's recovery, I believe this will work just fine. If it doesn't then I guess the worst that would happen is that you would need to start from scratch again.
Tenfar's recovery can be found here http://www.multiupload.com/8T81G1Q8MY
Like I said I'm pretty sure it will work to install cm7 however there a couple things you must know.
1. Usb debugging must be ENABLED to install this custom recovery
2. Once it is installed you MUST DISABLE usb debugging or it will not boot to recovery
3. You must open the app and select boot to recovery to enter custom recovery
4. 2nd init is included in the cm7 zip file so it will be automatically installed
5. You must cross your fingers and keep one eye closed during this process.... j/k

Thank you..
I had kept USB debugging on. After pressing 'wait' on not responding window.I got a command 'no root detected, is superuser installed?'. I had rooted and kept superuser to 'allow' command.but still i have the same no root message coming.Should I root the phone again?
If everything fails, I will try TenfARS RECOVERY. Can you please tell me whether it would create any problem if I do update sdcard .zip from stock recovery instead of custom recovery?

Now wait a second! It's not granting root permissions? Did you reboot the phone after rooting it? You MUST reboot after rooting or SU will not work properly.
Since the bootloader and stock recovery are locked down, the custom update.zip will not properly pass signature checks in stock recovery. ie: not signed my MOTO
Just a hunch but I think you need to reboot your phone and try installing 2nd init again and SU should work properly. Thats what is going on, I'm almost sure of it

Thanks zyxwvut
I rebooted the phone. Still there was some problem.I cleaned the data in su.The it told my su binary is outdated.So I downloaded the new binary.
I uninstalled the 2nd init I downloaded.And again downloaded it. Then installed the recovery and this time too it failed.
I browsed net for possible answers and in one forum I found a thread that when superuser is set to 'always allow' it brings some problem.Then I set the super user to 'prompt' and that worked.I could install custom recovery and install CM7.My defy is now running on CM7.
Thanks to you and this forum

Interesting.... I never would have thought of that. Of course in every situation that I've rooted SU is ALWAYS set as default to 'prompt' for access. That's probably why I have never seen this problem, but it is definitely good to know. Anyway I'm glad you got it figured out, CM7 is by far superior in terms of performance and I'm sure you will love it on your Defy. FYI you can play around with cpu frequencies and voltages in bootmenu to achieve ultimate performance and battery life. I wouldn't recommend going above 1300 Mhz (1000 Mhz is default) and keep vsel3 no lower than 56 (thats just my opinion though) you will know the vsel is too low if the phone reboots randomly or simply doesn't boot. Every cpu is different so the default settings are "safe" settings but can definitely be adjusted. I keep the clock settings default but I run vsel1=22 vsel2=38 vsel3=56. Be sure to 'save' settings after adjustment. These settings work great for me (after months of playing around) with no problems but your mileage may vary.
Cheers!

Thanx buddy
Can you tell me what is meant by VM heap size?

Related

[ROM][11/15/10] EZ-DZ ROM Update 01: Embedded Root+S-OFF+Overclocking |Obsolete...

EZ-DZ "PURE" ROM Update 01​
OBSOLETE
THERE'S A NEW VERSION, NOW WITH AUTOMATIC OVERCLOCKING
GO HERE:
http://forum.xda-developers.com/showthread.php?t=847724
INFO FOR USERS
(info for developers at post 3)
WHAT'S THIS ??
- This is my first relesae for the Desire Z so it is quite simple but very clever: this is a standard Update.zip flashable ROM.
- Flashing this ROM Update zip will NOT erase your personal info and configurations; it will not wipe your phone.
It will just add a new boot.img with embedded disabled security (root and S-OFF), the latest Superuser and Busybox tools, and an overclocking module with great power governors.
- This ROM Update can be flashed and has been tested for the stock EURO and NAM-Bell Desire Z.
WHY SHOULD I FLASH THIS ROM Update.zip ??
1.- This will update your stock ROM to include Root + S-OFF + Superuser + Busybox.
This is useful if you ever need to "reset to factory" defaults, because since everything is embedded, you won't have to root and S-OFF again !!.
2.- This Update is also helpful for people without an ADB console or ADB skills, to get the overclocking module pushed into their phone. Better than "pushed" it is already embedded and will stay after resetting to factory defaults.
Please refer to Post 2 for how to use the embedded overclocking capabilities.
3.- Finally, this is a no-harm practicing / experimenting flashing test.
If you are new to Android flashing, Clockwork, etc. and you want to safely test and figure out how's all this android flashing stuff, then this simple ROM Update.zip can help you to learn and understan the process and how it works.
HOW TO FLASH ??
- Obviously, you need root and S-OFF to flash this or anything.
(I assume you are an experienced user, if not, please refer to the stickied TUTORIAL thread "easy rooting/flashing FAQs for dummies")
TIP: Hey, please remember: it's clever to make a NANDroid backup before flashing anything.
- Downlaod and copy the EZDZupdate-01.zip file to your SD card, and flash it via ClockworkMod:
Open ROM Manager, tap "Install ROM from SD card", scroll to select the EZDZ Update, tap OK. Easy.
TIP: DON'T check "Wipe Data and Cache" unless you wanna delete all your personal info, installed apps and configurations !!
ACKNOWLEDGEMENTS:
Many, MANY THANKS to dsixda, coolbho3000, stridger, rmk40, cyanogen and many others for sharing and showing the way. I admire and appreciate your dedication and innovation.
HOW TO USE THE EMBEDDED OVERCLOCKING CAPABILITIES
- The system is set to 806 MHz by default. You can change your CPU speed using some simple commands:
- To overclock, open a Terminal Emulator (get one free from the Market if you don't have one),
type "su" and press Enter.
For 1017 Mhz type:
insmod /system/lib/modules/oc-dz.ko (this is the pre-defined speed)
For 1208 Mhz type:
insmod /system/lib/modules/oc-dz.ko pll2_l_val=63
For 1420 Mhz type:
insmod /system/lib/modules/oc-dz.ko pll2_l_val=74
You can also experiment with other values: multiply your desired value for 19.2.
(eg. to overclock to 1017 MHz, write "pll2_l_val=53", this will apply 19.2 x 53 = 1017MHz)
TIP: I strongly recommend SetCPU from the market, this smart app will let you check your current CPU speed and fine-tune many settings.
- Please notice your overclocking changes will be lost if you cold-boot (full reboot with "Fast Boot" disabled) and you would have to type the command again; if you'd like your overclocking to stick, go to Settings -> Applications and make sure "Fast Boot" is enabled.
- An advantage of this ROM Update is that the overclocking module is already embedded into the boot image, so it will stay there even after a full factory reset.
INFO FOR DEVELOPERS and SOURCES:
- Desire Z Kernel 2.6.32.21 from European 1.34.405.5.
- Modified ro.secure=0 at default.prop from unpacked boot.img's ramdisk dir, then repacked boot.img.
- Embedded Superuser to system/apps and Busybox to system/xbin
- Embedded overclocking module from coolbho3000 (recompiled by stridger)
- Embedded conservative and powersave power governors from rmk40
- Of course, feel free to unpack-edit-repack-whatever this Update.zip
So am i able to flash this on top of sense, my S-OFF is already done, rooted just flash this for the overclock thing, will it stick if i restart my phone?
Sorry, reposting further down (3rd page was already existing yet somehow I managed to post at (4:45pm-ish my time and end up posting at 8:49am!?).
shaunm1989 said:
So am i able to flash this on top of sense, my S-OFF is already done, rooted just flash this for the overclock thing, will it stick if i restart my phone?
Click to expand...
Click to collapse
1.-Yes you can flash this "on top" of Sense because it doesn't include a systrem.img, just the boot.img portion of the ROM (kernel + initial config).
2.-As stated in the post, Overclock will stick if you reboot with the Settings -> Applications -> Fast boot option enabled, but if you remove the battery (cold reboot) you will have to run the "insmod" command again (the overclocking module sticks but has to be invoked from the command).
Again, as stated, this is not a full ROM, just a kernel/boot update with those changes embedded.
Check post 2, I'm updating it
So even with SetCPU, this will not stick between cold reboots?
sonofabit said:
So even with SetCPU, this will not stick between cold reboots?
Click to expand...
Click to collapse
No, not yet, HTC has not relesaed our kernel source,
so yes you have to run the command after a cold reboot.
For now, this is quite nice.
~1380 MHz (val=72) is noticeably better than the stock 806. Thank you very much.
Thanks so much! Works perfectly. Quadrant scores of over 2200.
It seems to have broken my wi-fi...
Not sure if thats just me, considering I seem to have a lot of issues using the insmod command. Half the files on this forum give me (exec format error)
eXase said:
It seems to have broken my wi-fi...
Not sure if thats just me, considering I seem to have a lot of issues using the insmod command. Half the files on this forum give me (exec format error)
Click to expand...
Click to collapse
My wifi, fm radio, everything works fine after this update.
sonofabit said:
My wifi, fm radio, everything works fine after this update.
Click to expand...
Click to collapse
I swear my DZ is special, seems to have errors nobody else is having.
When I click Wi-Fi it just says error, ditto for wifi hot spot. I didn't even try FM Radio.
eXase said:
It seems to have broken my wi-fi...
Not sure if thats just me, considering I seem to have a lot of issues using the insmod command. Half the files on this forum give me (exec format error)
Click to expand...
Click to collapse
Why ?? That's impossible because I have NOT changed the kernel. WiFi works a treat.
I bet you have tested many methods before, thus, your phone may be messed up...
Please ellaborate a little, we can work it out.
This is what I would do:
1.- Backup your data with Titanium or Sprite Backup
2.- Enter Bootloader and "reset to factory defaults"
3.- Then, with a clean stock install, do root and S-Off
4.- Download ROM Manager form the Market an flash ClockworkMod
5.- Now come back and flash this ROM Update
It works a treat, you will be 100% happy
And if you EVER have to wipe everything again, your "stock" ROM will be already rooted from the very first boot
gtrab said:
Why ?? That's impossible because I have NOT changed the kernel. WiFi works a treat.
I bet you have tested many methods before, thus, your phone may be messed up...
Please ellaborate a little, we can work it out.
This is what I would do:
1.- Backup your data with Titanium or Sprite Backup
2.- Enter Bootloader and "reset to factory defaults"
3.- Then, with a clean stock install, do root and S-Off
4.- Download ROM Manager form the Market an flash ClockworkMod
5.- Now come back and flash this ROM Update
It works a treat, you will be 100% happy
And if you EVER have to wipe everything again, your "stock" ROM will be already rooted from the very first boot
Click to expand...
Click to collapse
thats particularly why I'm so confused. Because I literately JUST bought the phone and I followed your guide, and performed root but not S-OFF due to
"exec format error"
then somehow the wpthis-Z.ko from modaco's permaroot worked instead, and I managed to get S-OFF. But haven't managed to OC until this, and when I flashed this it broke Wi-fi.
But I'll try a factory reset and report back
gtrab, are the wifi modules included in the image? maybe his rom version is different than 1.34.405.5 and the modules are for another like the NAM version, for example.
I mean because I have a HD2 and everytime I update the kernel I have to copy the modules for this one I update.
I'm waiting for my DZ to arrive Once I have it, later this week, I will first debrand it and then apply this update.
eXase said:
thats particularly why I'm so confused. Because I literately JUST bought the phone and I followed your guide, and performed root but not S-OFF due to
"exec format error"
then somehow the wpthis-Z.ko from modaco's permaroot worked instead, and I managed to get S-OFF. But haven't managed to OC, and when I flashed this I broke Wi-fi.
But I'll try a factory reset
Click to expand...
Click to collapse
Do you have a NAM D-Z with the Bell ROM?
I'm not actually sure what it is,
because its bought from a Hong Kong store [ yes its legit and not dodgy replacement ] when I asked an employee he said the company imports them from Taiwan, which explains why there are extra asian keys on the F,G< H, V and B keys.
Other than that:
Baseband: 12.28b.60.140eU_26.03.02.18_M3
Kernel: 2.6.32.21-gbfa36d9 [email protected] #1
if that helps.
I'd tell you my SPL but I already S-OFF'd
Ook, I think you have this ROM installed: PC10IMG_VisionHTC_Asia_WWE_1.34.707.3_Radio_12.28 b.60.140e_26.03.02.18_M3_release_15 so this one is different from the european version (RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M).
I think the problem is with the wifi module. The same happens if I use a module for another kernel in my HD2, if I try to turn on wifi it says error.
You could try debranding it/flashing the european version to match this kernel. I can't test this because I don't have my D-Z yet. I think I will have it at the end of this week :/
Ok so I just TRIED to factory reset in HBOOT, 0 success as it just reboots itself into recovery mode. So I thought I'd try the factory reset button that Mr. Koush supplies us with which successfully restored my phone to default.
However when I installed Visionary+, it told me I was already rooted, and it wouldn't let me unroot. So I just nandroided it back to what I was on before I went through all this.
I think I'm just gonna give up trying to go too extreme with this phone until theres a bit more people using the Asian DZ.

Help...Defy stuck in bootloop

I have a stock 2.1 defy with the 2.51 rom (i think). all the mod i did was root the phone using super one click, the phone ran fine for a few months until i experimented with titanium backup and deleted google talk etc. i found out that (too late)doing this would cause the android market to stop downloading and updating my apps. To remedy my situation i tried installing google talk service.apk back to system apps. first by copying the file to my sd card and pushing it to the system file using terminal emulator. after rebooting my phone is now bootlooping. i tried removing the battery and just after i insert it it would go immediately into the bootloop phase. tried using recovery (volume down+power) and wipe cache and reset, still no go. last resort i tried is after wiping i tried installing cm7 but the installation was immediately aborted. please help, right now im close to tears, i didn't know that it was this hard to mod a defy. my previous phone was a wildfire and modding it was pretty easy.
What happens when you turn the phone on? Does it start in the bootloader? Is it stuck in Motorola Logo?
Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
Sent from my Life Proof Defy on CM7
juanplopes said:
What happens when you turn the phone on? Does it start in the bootloader? Is it stuck in Motorola Logo?
Click to expand...
Click to collapse
the phone turns itslef on automatically when i insert the battery, white moto logo first then bootloops in motoblur animation.i can go into bootloader mode by pressing up and power before inserting the battery. i just wished i hadn't played around with titanium backup. i already downloaded the necessary files to flash a new firmware. hope i learn to do it properly.
javi422 said:
Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
Sent from my Life Proof Defy on CM7
Click to expand...
Click to collapse
i tried wiping the cache/data numerous times under recovery mode to no avail. now im crossing my fingers that my battery isn't that drained for me to flash a new firmware.
Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
You can also do the battery hack/trick
Sent from my Life Proof Defy on CM7
Click to expand...
Click to collapse
i tried wiping the cache/data numerous times under recovery mode to no avail. now im crossing my fingers that my battery isn't that drained for me to flash a new firmware.
Click to expand...
Click to collapse
Sent from my Life Proof Defy on CM7
Hi I have the same problem,I just tried to flash the Barebone 1.5 ROM.
My Defy was stock,I just root it and made a backup with clockmod before I did as discribed here:
Installing (Rom wipes data/cache partitions)
1. Copy Barbones to sdcard: Barebones_15-signed.zip.
2. Boot into recovery (make a backup ?) and restore nandroid: 3.4.2_177-Nand.NORDIC_DEBLUR.zip.
3. Still in recovery, select install zip from sdcard -> choose zip from sdcard -> Barebones_15-signed.zip.
4. Reboot system, first boot will take time as it builds the dalvik cache; wait for the background to load, and enjoy Barebones.
- Use Easy Installer to install any apk's you feel are missing.
- Removed.Stock.Apps.zip
-- Removed Apps Must Be Copied To /system/app Manually - Remember To Set Permissions & Reboot
To downgrade back to Eclair; just flash the Eclair sbf you where using beforehand; thats it.
Click to expand...
Click to collapse
after Reboot it just shows Motorola,I can access Recovery Menu stock one and custom,tried wipe restore factory settings and wipe cache but nothing helped!
What version where you coming from ? Eclair or Froyo ?
Btw factory reset and wiping the cache doesnt do anything in these situations.
Did you restore the Nandroid provided ?
Also cant lie only thing I did not test was coming straight from an Eclair build.
I used the Korean Froyo sbf as a starting point; but I'm testing it now.
Got it alive again with this steps.
No wonder why u're stuck on motorola logo.
Let me break it down for you.
Make sure you have motodrivers installed or install them here.
And install the RSD Lite too Here
Turn off your phone, hit the power+volume up together.
Wait till u're in the bootloader.
Open the RSD Lite, u phone should be detected so u click on "..." select the .sbf u downloaded from here
And flash it.
Wait till is over, and your phone should be good again.
Click to expand...
Click to collapse
I used this .sbf
But I still don't know what went wrong,I did exactly as discribed in the TUT I postetd above!?
Well if you flashed that sbf you wont be able to downgrade back to Eclair anymore.
However; yes doing that will fix it.
Is it not good that I flashed this .sbf? I got the phone just 2 days ago I think it already had the newest firmware etc.!?
EDIT: But something is wrong with my Wlan connection it is very slow and always loses connection
I doubt it came with Froyo seeing as they are all leaked builds.
http://forum.xda-developers.com/showthread.php?t=966537 <- Read up
Just means you cant go back to Eclair.
Ok so you wifi is slow ? Are you even using my rom now; because you flashed 3.4.2_155-Stock.CEE_DEBLUR.sbf.
I cant see your phone so you have to tell me what your using.
Yes I just flashed the sbf nothing else,and before I just did what I read in the instructions from the Barebone 1.5 Thread.
1. Copy Barbones to sdcard: Barebones_15-signed.zip.
2. Boot into recovery (make a backup ?) and restore nandroid: 3.4.2_177-Nand.NORDIC_DEBLUR.zip.
3. Still in recovery, select install zip from sdcard -> choose zip from sdcard -> Barebones_15-signed.zip.
4. Reboot system, first boot will take time as it builds the dalvik cache; wait for the background to load, and enjoy Barebones.
- Use Easy Installer to install any apk's you feel are missing.
- Removed.Stock.Apps.zip
-- Removed Apps Must Be Copied To /system/app Manually - Remember To Set Permissions & Reboot
Click to expand...
Click to collapse
I tried this sbf before 3.4.3_11-Stock.UKTmobile_BLUR but it always failed thats why I tried the other one
So your not using my rom now - the sbf overwrites everything.
Ok sorry Im a noob^^ I just wanted to have all this blur stuff removed etc and your rom seems just perfect for me.
I have problems now with the phone and I really wished I would never had tried this.
I cant boot into recovery mode anymore with clockworkmod, I rooted my phone again installed clockwork but the screen stays black after the Motorola Screen came up when I try to make a recovery boot with clockwork.
cause I wanted to restore the backup I did with clockworkmod before I messed it all up,would that make my phone like it was before or not!?
I doubt you will be able to get back to your backup simply cause I dont think its Froyo.
So do this:
1. Boot into bootloader (power + volume up).
2. Flash 3.4.2_155-Stock.CEE_DEBLUR.sbf again.
3. While its rebooting after flashing hold volume down to goto stock recovery.
4. Do a factory reset.
5. Root your device using superoneclick http://forum.xda-developers.com/showthread.php?t=913709
6. Reboot.
7. Install 2nd Init Recovery http://forum.xda-developers.com/showthread.php?t=1032212
8. Reboot twice (to finish installing recovery).
9. Reboot into recovery - wait for blue led then hit volume down.
10. At this point you can try to restore your backup or flash a rom of your choice.
If you try your backup and it does not work you will need to start this process over.
Ok thank you so much fritolays for your help! I will try this tomorrow and post back if I had success or not!
greetz!
EDIT: Couldn't wait to try it and it worked! I took the risk and tried to install your rom again (restoring my backup didn't worked anyways 'cause clockworkmod didn't find the backup but it was still in the same folder it got stored before) works like charm as far as I could test it. But now I really have to go to sleep!
Big thanks again fritolays without your quick help I would still try to get my Defy to work without any success! and THANKS! for this great rom!!!
EDIT2: I don't know why but I have problems with the phone since yesterday when I first flashed another ROM,I always have Network Connection Problems now! I can't download anything from the market if I get to the market! 'cause normally it says no network connection! It worked fine for like 20minutes after I got it to work with ur method u told me above then it suddenly took very very long to download an app. Never had these Problems before,I also have very bad Phone Signal and most of the Time I can just make Emergency Calls and I turned Internet Connection OFF for mobile network (like I did before when it was stock) but sometimes I still can go online with Wlan turned off so this is really ****ed up 'cause I have no internet plan with my mobile phone!
But with your ROM the phone is really flying,I did a Benchmark Test before and got 1100 Score and by just putting your ROM on my Defy without any overclocking or something like that I got 1275 Score!
EDIT3 I found the direction it was clockworkmod/backup/ now
I did a wipe factory reset and a cache wipe and now restoring it I really hope everything is like it was before all this!
Ok this got me to the Bootloop Problem again so I did again all the steps u told me and instead of restoring ur ROM I restored my backup wich was now in the right direction,but it is also ended up in Bootloop!
EDIT4 If I try all this with ur ROM it works,is it because of the Froyo .sbf I flashed that I can't get my backup working!?
I get this Error Message after my phone booted with ur ROM maybe that is one of the Problems I have? "Sorry,the process android.process.media got suddenly closed try it again" I had to translate it so maybe the message is a bit different in english but thats what it says generally.
So everything worked great again,I go into Market to download TitaniumBackup (like I always did) then as always I apply the new Busybox Install TitaniumBackup suggests everytime I start it and the Wifi gets slow already by downloading Busybox. Then I tried to go to the Market again and Network Error, I get the feeling it has something to do with this app or the Busybox installation TitaniumBackup is doing!?
I don't know what it is but it alwys messes something in my phone up and I get Wifi Probs!??
EDIT5 I tried another ROM now "xd1 ** new ** ver 1.2" and everything worked fine! I downloaded Quadrant and a Antivirus App just to test it and everything was alright so I tried TitaniumBackup again (the Free Version as always) and guess what the download got fast till 42% then stuck and now I can't download anything again from Market it is very slow and then the downloads got canceled! wtf is wrong with this app!? I need it for all my Apps 'cause I did a backup with this app but since I flash custom ROMS it always does this bull**** when I download it from market!?
update..got my defy unbricked by following Higgsy's step by step method. installed a 2.51 SEA sbf in the process. love the phone without blur. now im thinking of upgrading to a froyo rom, which do you guys think is the best? based from reading the posts here i'm more confused than ever. sbf's here and 2nd init that??? not to mention a fixed sbf?? i really can't understand these terms and the more i read the more i got confused. Could you guys help me in laymans terms the proper process for upgrading to froyo and which rom is you think is best??

[Q] Stupid Root Question

Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?
BuffaloChips said:
Sorry if it has been answered elsewhere, but I have a migraine and am going for now. I just wanted to post really fast. I rooted my phone recently and have CM 7.2 on my Dinc. Now it suddenly seems that programs seem to think it isn't. Programs such as Titanium Backup won't work saying there is no root. Same with BusyBox and so on. Anyone had any issues like this? Any ideas as to what is next? I am somewhat new to this and would appreciate the help.
Tried to just reroot, but can't seem to get DooMLord's thing to work. Can't get the ADB drivers since, for some reason the Android SDK thingy WILL NOT download the Google USB driver packages. Tried about 6 different times and it just will not download and install them. HELP?
Click to expand...
Click to collapse
Open the superuser app and hit menu and select preferences. Scroll to the bottom and tap check for updates. If it says you have the latest update then hit the update anyways button. Also make sure you have the latest version of busybox installed. Then see if apps can get root. If not post back with your info.
S-off / s-on (can be found at the top of the hboot screen)
Android version (menu settings about phone software information)
Hboot version (found on hboot screen)
Radio (baseband) version. (also on hboot screen)
Also you can get the adb files and drivers here http://dinc.does-it.net/ADB
Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.
BuffaloChips said:
Tried that and it said d'ling manifest ... okay, parsing manifest ... okay, checking installed version = 3.0.3.2 . I clicked update anyway and got ,,, d'ling custom busybox ... okay, checking md5sum... FAIL! Tried the update fixer and it doesn't work either.Says no problems detected. In the little window it says checking signatures...ok! I click force and fix and get, extracting tiny busybox...fail! It says something about trying to download update.zip from somewhere but I cant see the rest.
My phone is s-off
Android version says 2.3.7
hboot 0.92.0000
radio 2.15.00.07.28
Now all I need are some good drugs so I can sleep. Migraines suck! It won't even let me do that.
Click to expand...
Click to collapse
Try flashing these thru recovery.
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip, and http://dinc.does-it.net/BusyBox/Busybox_1.19.4_Flashable.zip, then boot and see if your apps can get root.
Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.
BuffaloChips said:
Flashed them but no good. Still says no root with programs requiring it.
Was going to go nuts and shoot for flashing Condemned CM7.2 to see if I brick my phone or not, but after d'ling the ROM, I'm not sure what I'm supposed to do next.
Click to expand...
Click to collapse
If you want to flash a new rom, download the roms zip to your sdcard. Go to recovery and go to advanced and wipe dalvik-cache. Go to mounts and storage and format everything in there except sdcard and emmc. Then go to install zip from sdcard, internal sdcard, and choose the rom zip you downloaded, and select yes to flash it.
Are you sure that you have superuser app set to allow, and not deny these root apps. Try opening superuser app ad removing the root apps from the list. Then try using the root apps and see if it propmpts for and allows root.
I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)
BuffaloChips said:
I have super user set to prompt me every time and I click on allow. And yes, I have deleted and retried them so many times I want to rip out what is left of my hair.
OK, after flashing Condemnedsoul's cm7.2 (post says v12 but in about phone I get v10, go figure) nothing had changed. I got the ROM manager updated and clicked fix permissions and it went through a bunch of stuff. Now, before it wouldn't do anything through the ROM manager and recovery would do nothing either. Guess I found the culprit here. This is the bad thing about not being able to remove and reinstall these little items. Makes you really crazy at times as you are not necessarily sure that it is really the issue and if it is.... it requires a bit of extra work to fix. Live and learn.
Thanks for trying hard to help me though. It is greatly appreciated.
Oh, thanks for reminding me I am an idiot for not realizing one CAN flash ROM's straight from a .zip through recovery. LMAO! (this is meant as self-deprecating and not as an insult to you)
Click to expand...
Click to collapse
Yeah it is recomended not to use rom manager for flashing things, but to go straight to recovery to do it. The only thing i use rom manager for is so that i get notified about new versions of cwm recovery.
If flashing new roms dosent fix the issue there are always ruu's which will put your phone back to complete stock except for still having s-off, making it easy to root again.
Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.
BuffaloChips said:
Great! Wi-Fi doesn't want to work now! Crap! Gets as far as trying to obtain an IP address from my router and then says out of range while I am about ten feet from the router and the strength meter is showing full...! It just gets better and better some days.
Click to expand...
Click to collapse
Sounds like you need to just ruu and start over fresh. Seems something is seriously buggy with your setup. Are you using a custom kernel, or one that came with the rom?
Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.
BuffaloChips said:
Well, Wi-Fi was working with the original CM7.2. Just seems that it isn't with Condemned's. And I am using the kernel that came with the ROM.
To be honest, I haven't a clue about doing an RUU install.
Click to expand...
Click to collapse
Ruus are pretty simple. Make positive you are s-off before doing this, or rerooting will be a lot harder.
Download the ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip
Do not rename it just stick it on the root (in no folders) of your sdcard.
Boot into recovery (if entering recovery thru hboot select no when prompted to update) wipe dalvik-cache in the advanced menu, and format everything in mounts and storage except emmc and sdcard.
Power off the phone and boot to hboot. (hold vol down plus power till a white screen pops up) Hboot will find the ruu automaticly and prompt you to press vol up to update. Do so and let it do its thing, note it will reboot once durring the ruu, be patient and do not interupt it. When done press vol up to reboot. You are now stock.
Do the setup on the phone and then go to menu - settings - applications, and uncheck fastboot. Use a file explorer or pc to remove the PB31IMG.zip from your sdcard.
Power off the phone and boot to hboot again. From the hboot menu select factory reset. This will ensure all corrupt data is gone. After it finishes the phone should boot again. Once again do the setup and uncheck fastboot again.
Download these two files:
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
Do not rename them and place them on the root of your sdcard.
Power off the phone and boot to hboot. It will find the PB31IMG.zip file (cwm recovery) and prompt to press vol up to update. Do so. When asked to reboot press vol down no.
Select recovery from the hboot menu. Once in recovery select install zip from sdcard - internal sdcard- and select the Superuser_3.0.7.zip. Select yes when prompted.
Reboot thr phone and go to the market and download the busybox app. Open busybox and install it. Go to your sdcard and delete or rename the clockwork PB31IMG.zip.
Thats it you should be stock rooted. From here you can stick with stock, or flash a rom of your choosing.
I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......
BuffaloChips said:
I have a PB31IMG.zip file that is 176,626kb with 8 "files" in it. It has andriod-info.txt, hboot_8x50_0.92.0000_100723nb0, radio.img, boot.img, recovery.img system.img splash1.nb0 and nv_MFG_VZW_1.70_0825_PRL58006.img in it. Any idea what the hell this is for? I thought about trying to use it, but I can't even remember what the hell it is. Sad, I know. I should have renamed it so I would know.
Live and learn ......
Click to expand...
Click to collapse
That is an ruu. Not sure which version, but definitley an ruu.
PB31IMG.zip files can be ruu's, radios, splash screens, recoveries, hboots, or a combination of them.

[Q] Boot loop after installing busy-boxon HTC One

Hi, I installed busy-box to my HTC with stock ROM and kernel, and now Im having problems keeping my phone from not rebooting. My phone reboots like normal and I can use it normally for about a minute until it reboots. Prior to this it was working fine.I now know there are problems installing busy box to stock ROMs.. At this point I'm willing to do just about anything to get my phone back to its previous state. Preferably still rooted and with my data still intact.
When I installed busy-box I installed to the /system/xbin directory. A install notifier came up saying that busy box was already installed and doing this may not be required then it rebooted. Im not sure if Ialso did the smart install because it did not say smart install was finished or was ready to be finished. I can still access the TWRP recovery screen.
I would like to inform I am a cheeky scrub when it comes to dealing with situations like this so preferable please insruct me with simple and easy instructions.
Thank you so much in advance!
tried doing wipe cache/ wipe davilk?

Xposed Framework Is Not Installed - Installation Help

Hey guys,
I have a HTC M9
I am trying to install the Xposed Framework on my Rooted M9 with stock ROM but inside the Xposed app it tells me that it's not installed.
I have TWRP installed.
I rooted my phone with SuperSU v2.65 (After trying a couple of versions that would result in boot loop)
I checked my phones CPU (ARM64) and downloaded "xposed-v86-sdk23-arm64" as well as "XposedInstaller_3.0_alpha4.apk".
I booted into TWRP and Installed the xposed-v86-sdk23-arm64 Framework, it gets to Placing Files and then my phone reboots (I don't know if this is normal or not).
My phone reboots and I open XposedInstaller, under Framework it says "The latest version of Xposed is currently not active, Did you install the Framework and reboot?"
Inside the Framework menu it says "The Xposed Framework is not installed. Please download the latest ZIP file from XDA and flash it manually via reocvery."
The options Install/Update, Uninstall, Recovery (Flash zip automatically) are grayed out.
When I press the Soft Reboot button the phone does restart but no change.
When I try to press the Reboot option I get this error:
Code:
sush: <stdin>[8]: /data/user/0/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed please use the device's normal reboot function.
I have restarted the phone normally a couple of times with no change.
I'm new to rooting but I don't find this stuff too difficult to understand, I had a lot of problems trying to get my phone to root in the beginning, I had to try a few SuperSU versions before I could get my phone past boot looping. When I run Root Check it tells me that my phone is Rooted.
I'm not sure what other information I can post to help yous help me but if there's anything you need to know just ask and I'll reply asap.
Cheers guys
I basically want access to Xposed so I can use the FakeGPS and the Hide Mock Location modules.
EDIT (29/07 2:00PM)
I re-downloaded xposed-v86-sdk23-arm64 and tried flashing it again, I read somewhere someone mentioning to clear the caches after the install has finished but when I start the install and it reaches "Placing Files" the phone automatically reboots itself, so I held Volume down and Power to go straight back into Download Mode > Boot Mode > Recovery Mode and cleared the caches, let the phone boot up and still have the exact same problem as the above post.
Seeing as though I haven't gotten any advice yet I am going to try an older version of the Installer app, I have 2 seperate backups of my device so if anything goes wrong I can restore, wish me luck!
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Wolf_vx said:
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Click to expand...
Click to collapse
You have described my situation perfectly.
I have a back up I can restore through TWRP if I soft brick it, which at this moment I just did.
I tried flashing the same superSU version again seeing as though it was the only one I could get to work (didn't try your version though) and then installed the latest Framework version right after without rebooting, cleared the two caches and rebooted, I get past the first boot screen, I see my mobile providers boot screen, I then get to the screen with One in big letters and it stops there, I'll try a few more reboots before I restore.
Xposed isn't stable on the m9 and is why I have avoided installing it. Some people get it running first time, no issues. Some people brick their phones. It really is a roll of the dice.
I'd stay away from it if i were you. Htc's can't be easily recovered.
Beamed in by telepathy.
it doesn't brick the phone, but there are a few tutorials with other methods of flashing xposed, should be inside software development of android forum. please try those solutions and please stop creating two threads, with nearly same problem. both things can be asked in one thread, thanks
stock rom has often problems. you need to install busybox to have it working properly

Categories

Resources