Database Develop

I screwed something up.

I was rooted and running CM6. I tried getting back to a stock 2.2 by flashing the stock image from Rom Manager. I downloaded the 2.2 update from google and it wouldn't update. In the system menu or bootloader I got a little format happy with boot/system and so on. Anyway, doing a nandroid now. Is there anyway to get this phone back to the kernel it shipped with?

You have to flash it with the stock recovery.

I've been using that Universal androot.http://www.androidappjudge.com/2010/08/one-click-root-application-universal_10.html I tried flashing stock 2.2 and I didn't read the two options, I just clicked them and kept going not realizing that I flashed the rooted, superuser version. Does this mean that I'm now rooted forever? When I try flashing stock 2.2 with rom manager It stops @ the android and /!\ symbol. Now it's even doing this with CM.
I'm now wondering how to get rid of whatever crap might be floating around on my phone and why it may not be flashing anymore?

there is nothing wrong, rooting allows you the ability to have super administrative rights. Since all you have done is grant yourself admin rights, the recovery should be the same.

Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.

glwinkler said:
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
Click to expand...
Click to collapse
Did you wipe? I used 1-click root and I hadn't flashed anything in over a year so I forgot to wipe and I boot looped until I pulled the battery, booted into recovery and wiped. Simple solution but it could be worth mentioning...

So you are saying that, you have the stock recovery now? Triangle with little android? If so, Just download a PASSIMG.zip and flash through bootloader. This will take you to stock.
I have an N1 with locked bootloader and when I wanted to go back to stock(Forgot to get a nandroid of unroot rom). I had to flash a stock recovery. then downloaded the PASSIMG.zip from here http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91+downgrade
This takes me back to ERE76. Then I download an OTA of FRF85B.

I think fix permissions fixed everything. Thanks for the tips!
THIS HELPED TOO:
http://forum.xda-developers.com/showthread.php?t=619153

Issues with Safestrap - How to get phone booting properly?

So I just got this phone, and I've been trying to get it up to ICS. I've gone through and was able to complete the ICS update the first time completely, installed Safestrap, etc. Now this is where the issues came in. I did a backup, and then I started restoring some apps from titanium, from an old phone. This is where I started getting constant force closes. Tried fix permissions, went through again, same issue. So I wiped the phone, and went to restore with safestrap - it failed. Now on bootup, it refuses to even boot into safestrap anymore. All I can get is either a blank screen, or motorola recovery menu. By the fact that I can get into the motorola recovery menu, I presume it's not fully bricked, but I know there can be issues with installing on top of Safestrap.
Long story short, my question: In this condition, will flashing the same file I did during the ICS leak installation through Moto Recovery allow the phone to boot? Or will that cause a brick like downgrading from ICS does?

So, just to be sure, you installed one of the ICS leaks correct? Then you installed safestrap 2.0?
Sent from my Droid 4

Yes, that's exactly what I did. Was able to boot up into Safestrap (2.0) and restore through Safestrap, but after wiping /data I got errors with restoring a backup, and after rebooting to attempt it again, Safestrap splash screen no longer appears for me. It has the initial splash, and where the Safestrap splash should be, it just stays blank screen.

Not sure what would have caused this. I don't think you'll be able to flash the zip again since it looks for a .219 system build. Might be worth a shot though. You could also try booting into recovery and doing a factory reset. If neither of those work, try following the instructions for upgrading from one leak build to another.
Sent from my Droid 4

Tried Factory reset already, and attempted just flashing the update anyways - got an error saying build.prop file was invalid/missing?
Now I'm going through the tool steps to swap between ICS builds. At least I'll hopefully get something working.
Though I did do a step I forgot to mention, if that explains why it happened. After the Safestrap restore failed, I tried to do a partial restore of /system and /data. /system restored fine, when I went to do /data it said it was restoring /system in the log - could that have been an issue? A possible mistake in safestrap that overwrote the wrong folder? Or just an issue with the menu?

Doing the ICS switch got it working for me. Now to attempt round 2 and see if I can get into CM9, and Safestrap works right.
More research, root cause : Forgot to install busy box when doing the initial root.

Glad you got it working!
Sent from my Droid 4

[Recovery] Unofficial TWRP 2.6.3.0 for XT901 / XT907

UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff

Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.

CM 10.2 Build removed due to errors.

jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.

@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4

I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4

netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.

Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload

Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.

scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.

Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.

motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.

RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x

motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal

Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.

When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2

Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.

I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.

It works with the xt902 too. Thanks!

What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!

After installing stock firmware, problem still persists...

The problem I'm having originally started when I attempted to install a marshmallow global port rom on my g4. For some reason even after doing a clean install the rom was buggy, screen would become unresponsive, and apps would consistently crash. I attempted every possible option from recovery. Wipe, install several different roms, restored nandroid backup (unresponsive screen issues still persisted). Finally, I decided to restore stock firmware with a complete wipe of the phone via kdz. However somehow the system instability persists. An error will pop up saying "Process system isn't responding. Do you want to close it?" So now I have no custom recovery and have a hard time even getting to the settings menu to enable usb debugging. I'm stumped and what I should do....

motojdm said:
The problem I'm having originally started when I attempted to install a marshmallow global port rom on my g4. For some reason even after doing a clean install the rom was buggy, screen would become unresponsive, and apps would consistently crash. I attempted every possible option from recovery. Wipe, install several different roms, restored nandroid backup (unresponsive screen issues still persisted). Finally, I decided to restore stock firmware with a complete wipe of the phone via kdz. However somehow the system instability persists. An error will pop up saying "Process system isn't responding. Do you want to close it?" So now I have no custom recovery and have a hard time even getting to the settings menu to enable usb debugging. I'm stumped and what I should do....
Click to expand...
Click to collapse
Can you get to Download mode? If so you can flash this rooted, stockk 81110N img and once it is in, you can use Flashify to flash twrp.
http://forum.xda-developers.com/tmobile-g4/development/h81110n-stock-rooted-image-t3191038

Barsky said:
Can you get to Download mode? If so you can flash this rooted, stockk 81110N img and once it is in, you can use Flashify to flash twrp.
http://forum.xda-developers.com/tmobile-g4/development/h81110n-stock-rooted-image-t3191038
Click to expand...
Click to collapse
I managed to reinstall twrp and root. However, installing different roms whether it be stock or otherwise does not resolve the issue. I'm absolutely boggled how this issue can persist across flashes. I'm hesitant to call it a hardware problem because the phone is mint and there was no physical damage/shock done to the phone right prior to the issues occuring.

xposed modules resulted in a bootloop - cant restore my nandroid either

hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get

chaitra26 said:
hi all, i made an xda account because i really cant understand whats going on with my phone
HTC One M8 running Android 6.0 (rooted)
so after rooting my phone, i proceeded to install xposed.
i flashed the zip - no problem
i installed the apk, and after choosing 4/5 modules that i wanted, i went ahead and enabled them all and rebooted to activate them.
this is where the problems started. my phone booted, however it kept on flashing a screen with the deafult One M8 wallpaper at me. after a few seconds, it came up with an error "com.android.systemui has stopped"
not sure what was going on, i went to twrp and directly restored my nandroid backup, but after waiting for 15 mins, i realised my phone was in bootloop, so i went back to twrp and did a factory reset and restored my nandroid. but again, it went into bootloop. i tried factory resetting and restoring 3 times before giving up.
my phone isnt connecting to my laptop anymore either, but if i need to flash anything i can do it with my sd card.
im not a complete noob but im still learning and ive never not been able to restore my nandroid.
thanks in advance for any help i can get
Click to expand...
Click to collapse
*. Flash xposed uninstaller zip and try booting your device. Link here - http://dl-xda.xposed.info/framework/uninstaller/
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system etc.. Then restore your nand. Then you're good to go.

thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again

chaitra26 said:
thanks a ton for your reply
i already tried flashing the uninstaller - didnt work
but ill try your second method. thanks once again
Click to expand...
Click to collapse
Hey, the 1st one won't works, Cuz you'd already did a factory data reset, so that's gonna be won't work. And you'd tried restoring nandroid over that, so that's failed.
I hope second one will works.

sachin n said:
*. Flash xposed uninstaller zip and try booting your device.
-->> use this» make a full wipe from recovery, then restore nandroid backup.
*.While restoring nand. from recovery, make a full wipe like wipe system / data etc.. Then restore your nand. Then you're good to go.
Click to expand...
Click to collapse
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
oh my god my phone doesnt have an os anymore... what have i done wrong?????

chaitra26 said:
Um i think i seriously screwed up - i deleted everything including system and data and stuff - but now my nandroid is gone
what can i do now i dont even have a nandroid!
Click to expand...
Click to collapse
Deym!!
So, look at the One m8 forums, you'll get the workarounds.
I've found one here - https://forum.xda-developers.com/ht...k-twrp-t3086860?_e_pi_=7,PAGE_ID10,5801529172
@chaitra26, either DL any custom ROMs and flash it via custom recovery [Twrp].
Look here for custom ROMs - https://forum.xda-developers.com/htc-one-m8/development?
Regarding that '' no OS installed'' error, that's common when you try to reboot your device from twrp without installing any system images /ROMs.
FYI - when you full wipe your device and tries to power up you'll get the same warning.