Database Users

having issues after bootloader unloack, and root

this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...

Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App

i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol

can you boot into fastboot or Android Recovery?

yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?

PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?

i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick

i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?

Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?

it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...

PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...

rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...

PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.

you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!

Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.

just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!

Urgent help PLEASE!

I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.

Rizy7 said:
I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.
Click to expand...
Click to collapse
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.

simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?

Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.

Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.

username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
I used adb to push a file but I cant see it

thank god it worked

simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
gee2012 said:
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.
Click to expand...
Click to collapse
username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
Thanks for your help guys

[SOS] after flash new rom, bootscreen stop at Google

Please help me,
My Nexus 4
after flashing PURITY ROM
reboot, the screen stop at GOOGLE forever there
Please give me you help to get away with this screen
Thank you very much,
Regards,
PS:
*don't have any other rom available on the internal disk
*cant connect to PC via bootloader

nguoidungnq said:
Please help me,
My Nexus 4
after flashing PURITY ROM
reboot, the screen stop at GOOGLE forever there
Please give me you help to get away with this screen
Thank you very much,
Regards,
PS:
*don't have any other rom available on the internal disk
*cant connect to PC via bootloader
Click to expand...
Click to collapse
Did you do a factory data reset before flashing the ROM?

Yes, I did.
I did a very clean flash (wipe & reset factory data too)
abaaaabbbb63 said:
Did you do a factory data reset before flashing the ROM?
Click to expand...
Click to collapse

nguoidungnq said:
Yes, I did.
I did a very clean flash (wipe & reset factory data too)
Click to expand...
Click to collapse
Boot in recovery, then connect your phone to your PC.
Use "adb push" to push a ROM to your phone, and then flash it with recovery.
Or
Use the "adb sideload" option from recovery.

Thank you very much for your replying,
because "USB Debugging is enabled": NOT ENABLE because of the new rom
will it work with my phone?
abaaaabbbb63 said:
Boot in recovery, then connect your phone to your PC.
Use "adb push" to push a ROM to your phone, and then flash it with recovery.
Or
Use the "adb sideload" option from recovery.
Click to expand...
Click to collapse

nguoidungnq said:
Thank you very much for your replying,
because "USB Debugging is enabled": NOT ENABLE because of the new rom
will it work with my phone?
Click to expand...
Click to collapse
No you dont need usb debugging enabled. Adb should work by default when your phone is booted into a custom recovery.

Thank you, it connects & works.
May I know where this file (new updated) is stored?
Chromium_ said:
No you dont need usb debugging enabled. Adb should work by default when your phone is booted into a custom recovery.
Click to expand...
Click to collapse

nguoidungnq said:
Thank you, it connects & works.
May I know where this file (new updated) is stored?
Click to expand...
Click to collapse
You mean the rom you just flashed? It depends on what remote path you used in the adb command.
(adb push rom.zip /path/on/phone/)

oh sorry,
I meant, when this new rom (for exemple: purity.zip) is pushed to my phone via SIDELOAD,
after 100% loaded, where this "purity.zip" will be in my phone,
so that I can flash this rom to the phone
Thank you.
Chromium_ said:
You mean the rom you just flashed? It depends on what remote path you used in the adb command.
(adb push rom.zip /path/on/phone/)
Click to expand...
Click to collapse

nguoidungnq said:
oh sorry,
I meant, when this new rom (for exemple: purity.zip) is pushed to my phone via SIDELOAD,
after 100% loaded, where this "purity.zip" will be in my phone,
so that I can flash this rom to the phone
Thank you.
Click to expand...
Click to collapse
If you use adb sideload you wont have to look for it to flash...it gets flashed automatically. (adb sideload = adb push + flash via recovery)
Nonetheless the file will be pushed to the root of your sdcard and it will be renamed to sideload.zip. (/sdcard/sideload.zip)
If you use adb push then you specify where you want to push it to.

Frist of all, Thank you Chromium for your help, it works.
Now, I can push the file to my phone.
However, it seems that there something wrong because of my flash rom from xenoHD (Android v4.2.2) to Purity (Android v4.3)?
I dont know, but after I flash "back" the OLD xenoHD, my phone is still stuck at the GOOGLE screen...
Please give me your advice.
Thank you & Regards,
Chromium_ said:
If you use adb sideload you wont have to look for it to flash...it gets flashed automatically. (adb sideload = adb push + flash via recovery)
Nonetheless the file will be pushed to the root of your sdcard and it will be renamed to sideload.zip. (/sdcard/sideload.zip)
If you use adb push then you specify where you want to push it to.
Click to expand...
Click to collapse

nguoidungnq said:
Frist of all, Thank you Chromium for your help, it works.
Now, I can push the file to my phone.
However, it seems that there something wrong because of my flash rom from xenoHD (Android v4.2.2) to Purity (Android v4.3)?
I dont know, but after I flash "back" the OLD xenoHD, my phone is still stuck at the GOOGLE screen...
Please give me your advice.
Thank you & Regards,
Click to expand...
Click to collapse
So Purity 4.3 works but xenon 4.2 doesnt work?
Are you wiping in between?

1. I was using ok with XENO HD (4.2)
2. Today, I tried PURITY 4.3
3. Stucked at GOOGLE SCREEN
4. After learn the new technique, I was able to copy the old rom XENO HD 4.2 BACK & FLASH ( I DO WIPE, FACTORY RESET..before FLASHING)
5. It still STUCKED AT THE GOOGLE SCREEN
....
Do you guess any reason why, or you have any suggestion what I should do, to get back the NORMAL PHONE
Thank you & Regards,
Chromium_ said:
So Purity 4.3 works but xenon 4.2 doesnt work?
Are you wiping in between?
Click to expand...
Click to collapse

nguoidungnq said:
1. I was using ok with XENO HD (4.2)
2. Today, I tried PURITY 4.3
3. Stucked at GOOGLE SCREEN
4. After learn the new technique, I was able to copy the old rom XENO HD 4.2 BACK & FLASH ( I DO WIPE, FACTORY RESET..before FLASHING)
5. It still STUCKED AT THE GOOGLE SCREEN
....
Do you guess any reason why, or you have any suggestion what I should do, to get back the NORMAL PHONE
Thank you & Regards,
Click to expand...
Click to collapse
Oh, i see. It seems that you're doing everything correctly. If you just want the phone back in a working condition you can flash the factory images. That should get the phone up and running again, but it'll remove your custom recovery, so you will have to reflash one after, but lets be honest....not that hard.

Chromium & abaaaabbbb63, Thank you very much!
It runs again
Thank you & Regards,
Chromium_ said:
Oh, i see. It seems that you're doing everything correctly. If you just want the phone back in a working condition you can flash the factory images. That should get the phone up and running again, but it'll remove your custom recovery, so you will have to reflash one after, but lets be honest....not that hard.
Click to expand...
Click to collapse

Factory reset isn't enough, you also need to format the /system partition sometimes. Also you need to flash a compatible 4.3 kernel with your 4.3 rom. Usually the kernel is included in the rom.zip in the form of boot.img, but you can flash your own.
As to move files from your computer to your phone, use: adb push rom.zip /sdcard/
Or you can flash the file directly, by putting the recovery into sideload mode and type: adb sideload rom.zip

[Q] Copy files to the device on twrp?

I installed a rom which had a bad install so i was stuck in a boot loop, And no matter what I try i always get the boot loop, Im able to boot into twrp but going to mount im unable to see it on my windows 7 laptop? I have no idea how to push files to the device with adb as im what you'd call a slow learner lol.
Any ideas would be much apreciated.

I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!

Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?

crazyboy81 said:
I'm in the same boat, I didn't install any custom roms but have twrp and this morning a system update was available and I said yes, it went into twrp and did nothing, I recovered and nothing, it'll only go into twrp and nowhere else. HELP!
Click to expand...
Click to collapse
Thats an easy one compared to me lol. go to advanced, terminal command and type in the following minus the brackets (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota)

metapy said:
Did you guys look here?
[FIX] Installed TWRP and now you're stuck after OTA?
Click to expand...
Click to collapse
My problem isnt anything like the bootloop, Ive done a full wipe and now have nothing on my phone to install, adb sideload isnt working for me for some reason as its coming up as adb is not a recognised command? I feel screwed?
EDIT: I may have solved my problem, currently pushing a rom onto the phone with adb sideload

D801 (Tmobile) Stuck in TWRP - No OS Boot

This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!

brickwall99 said:
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
Click to expand...
Click to collapse
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.

freebee269 said:
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
Click to expand...
Click to collapse
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.

brickwall99 said:
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
Click to expand...
Click to collapse
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.

freebee269 said:
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
Click to expand...
Click to collapse
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...

brickwall99 said:
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
Click to expand...
Click to collapse
that's because you have no adb connection. no connection = no pushing files. that's why i said you need to get adb working first.

I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!

brickwall99 said:
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
Click to expand...
Click to collapse
good news. hope you get up and running now. still update your twrp.

freebee269 said:
good news. hope you get up and running now. still update your twrp.
Click to expand...
Click to collapse
Okay I got the ROM transferred and I have installed it successfully.
Using this one: http://forum.xda-developers.com/showthread.php?t=2598361
But when I reboot it goes straight to recovery.
A factory reset fails. I'm only able to advanced wipe of system/data, also it fails when I wipe cache or dalvik.
So I've tried wiping system/data, then installing the ROM again, and it just reboots straight back to recovery.

I sideloaded TWRP 2.6.3.5 for tmobile. Verified it shows 2.6.3.5 TWRP now. I'll try to sideload/install the ROM again.
Edit: When trying to factory reset it says failed to mount cache.

Okay so I have successfully installed the ROM with TWRP 2.6.3.5 and when I reboot it still goes straight into recovery.
What next?
Thanks
Edit: Is there perhaps something wrong with the bootloader, or what? I'm thinking part of the issue is because I can't mount or wipe cache/dalvik?

I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle

rawb123456 said:
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
Click to expand...
Click to collapse
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.

Any luck? I tried flashing CM11 on TWRP 2.6.3.2 (per XDA instructions) and it failed. Now I am stuck in recovery and can't ADB new recovery
brickwall99 said:
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Click to expand...
Click to collapse